Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert PVC storage path to /var/tmp #7865

Closed
wants to merge 2 commits into from

Conversation

jradtilbrook
Copy link

@jradtilbrook jradtilbrook commented Apr 23, 2020

Fixes #7511

This changes the mount volume of the storage provisioner to /var/tmp on the host system.
On modern linux systems this is a normal mount point, as compared to /tmp which is generally a tmpfs which is removed upon reboots so persistant volume claims are not actually persistent.

@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
  • Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Apr 23, 2020
@k8s-ci-robot
Copy link
Contributor

Welcome @jradtilbrook!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Hi @jradtilbrook. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 23, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jradtilbrook
To complete the pull request process, please assign ra489
You can assign the PR to them by writing /assign @ra489 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 23, 2020
@k8s-ci-robot k8s-ci-robot requested review from medyagh and RA489 April 23, 2020 15:31
@codecov-io
Copy link

Codecov Report

Merging #7865 into master will decrease coverage by 1.11%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #7865      +/-   ##
==========================================
- Coverage   36.68%   35.57%   -1.12%     
==========================================
  Files         146      148       +2     
  Lines        8978     9297     +319     
==========================================
+ Hits         3294     3307      +13     
- Misses       5292     5593     +301     
- Partials      392      397       +5     
Impacted Files Coverage Δ
pkg/minikube/perf/start.go 30.00% <0.00%> (-21.36%) ⬇️
pkg/minikube/cruntime/containerd.go 28.65% <0.00%> (-15.10%) ⬇️
pkg/minikube/bootstrapper/images/images.go 87.50% <0.00%> (-12.50%) ⬇️
cmd/minikube/cmd/node_start.go 10.00% <0.00%> (-12.23%) ⬇️
pkg/minikube/out/out.go 46.57% <0.00%> (-12.05%) ⬇️
pkg/minikube/command/ssh_runner.go 0.00% <0.00%> (-10.35%) ⬇️
pkg/minikube/kubeconfig/kubeconfig.go 61.06% <0.00%> (-7.63%) ⬇️
cmd/minikube/cmd/node_stop.go 14.28% <0.00%> (-5.72%) ⬇️
pkg/minikube/proxy/proxy.go 96.96% <0.00%> (-3.04%) ⬇️
cmd/minikube/cmd/delete.go 22.13% <0.00%> (-2.98%) ⬇️
... and 43 more

@minikube-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@jradtilbrook
Copy link
Author

/check-cla

@jradtilbrook
Copy link
Author

The CLA has been signed

@tstromberg
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 23, 2020
@minikube-pr-bot
Copy link

kvm2 Driver
docker Driver

@RA489
Copy link

RA489 commented Apr 28, 2020

/check-cla

@tstromberg
Copy link
Contributor

/ok-to-test

@tstromberg
Copy link
Contributor

need any help with the CLA?

@jradtilbrook
Copy link
Author

need any help with the CLA?

Sorry @tstromberg it wasn't working and I forgot to come back to it. I believe I've done it now

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Apr 30, 2020
@jradtilbrook
Copy link
Author

The logs are so verbose I'm not quite sure what the error is. If you can provide any more detail that would be much appreciated! 🙏

@tstromberg
Copy link
Contributor

KVM had the folowing failures that did not seem related:

TestErrorSpam - 369.91s
TestFunctional/parallel/ServiceCmd - 83.45s
TestStartStop/group/crio - 780.94s

Likewise docker had:

TestStartStop/group/old-k8s-version - 867.57s
TestStartStop/group/containerd - 356.23s
TestStartStop/group/crio - 930.88s
TestStartStop/group/embed-certs - 794.46s
TestFunctional/parallel/ServiceCmd - 59.56s
TestPause/serial/SecondStartNoReset - 47.51s

Our integration tests are pretty flaky at the moment. They all seem unrelated, but I'll re-run the tests to see if any of these are consistent.

@tstromberg
Copy link
Contributor

/ok-to-test

@jradtilbrook
Copy link
Author

@tstromberg Is there anything I can do to assist?

@tstromberg
Copy link
Contributor

I'm going to have to give this some thought on how to roll this out:

If a user upgrades their minikube, but have an older cluster running - they will end up with a new storage provisioner running on an old ISO. How should we we handle that?

@priyawadhwa priyawadhwa added the triage/discuss Items for discussion label May 19, 2020
Copy link

@priyawadhwa priyawadhwa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @tstromberg

We could add a template field to path in storage-provisioner.yaml.tmpl

path: {{.TmpHostPath}}

and we could set TmpHostPath=/tmp if minikube version < 1.11 and TmpHostPath=/var/tmp if minikube version >= 1.11.

WDYT?

@priyawadhwa priyawadhwa removed the triage/discuss Items for discussion label May 20, 2020
@afbjorklund
Copy link
Collaborator

afbjorklund commented Jul 21, 2020

This also needs to be synchronized with the kicbase implementation:

302a6b0 "Add minimal minikube-automount to the kic image"

As well as documented properly, for current users of the "none" drivers.

https://minikube.sigs.k8s.io/docs/handbook/persistent_volumes/

As I wrote in the issue #7511 (comment), I don't think this change is worth it...

The /tmp location was never meant for storage... And /var/tmp might not be ideal.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 19, 2020
@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
  • Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. and removed cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 19, 2020
@sharifelgamal sharifelgamal removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 11, 2020
@jradtilbrook
Copy link
Author

@sharifelgamal I noticed you removed the stale label. I'm wondering if I should just close this as stale. I don't have time to work on it and have fixed my own issue with a bind mount on my host manually for now

@medyagh
Copy link
Member

medyagh commented Nov 25, 2020

@sharifelgamal I noticed you removed the stale label. I'm wondering if I should just close this as stale. I don't have time to work on it and have fixed my own issue with a bind mount on my host manually for now

@jradtilbrook
do u mind sharing the steps u did manually to fix ?

@jradtilbrook
Copy link
Author

@jradtilbrook
do u mind sharing the steps u did manually to fix ?

@medyagh I enabled a systemd mount unit that bind mounts the directory onto /var/tmp. You can see the unit file at https://github.com/jradtilbrook/dotfiles/blob/master/files/etc/systemd/system/tmp-hostpath%5Cx2dprovisioner.mount

@tstromberg
Copy link
Contributor

Closing by request until author has a chance to revisit this.

@tstromberg tstromberg closed this Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Driver: none host path should be /var/tmp for PVCs