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

vSphere cloud provider did not detach volume when shutdown node #63577

Closed
liqlin2015 opened this issue May 9, 2018 · 9 comments

Comments

@liqlin2015
Copy link

commented May 9, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

What happened:

  1. Set up Kubernetes v1.10 cluster with vsphere cloud provider enabled.
  2. Create a deployment nginx using some vsphere persistent volume.
  3. Shutdown node where nginx pod is running. The nginx pod will be scheduled to another ready node.
  4. Try to start above node was shutting off. The node cannot be started because attached vmdk volume.
  5. After manually removed the vmdk volume from the node, the node can be started.

What you expected to happen:

After node was shut down, vsphere volume plugin should be able to detach volume from the node when pod was removed.

How to reproduce it (as minimally and precisely as possible):

See above steps.

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): 1.10
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): Ubuntu 16.04
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@liqlin2015

This comment has been minimized.

Copy link
Author

commented May 9, 2018

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node and removed needs-sig labels May 9, 2018

@w-leads

This comment has been minimized.

Copy link
Contributor

commented May 9, 2018

Hi, I've faced the same kind of issue, and raised a pull request which is under review phase now.
I'm not sure if this is exactly the same as your case, also if this pr will be merged though... but just let me share it here.
#63413
Thank you

@fejta-bot

This comment has been minimized.

Copy link

commented Aug 7, 2018

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

@nikhita

This comment has been minimized.

Copy link
Member

commented Aug 10, 2018

/remove-lifecycle stale
/sig vmware

@hakanisaksson

This comment has been minimized.

Copy link

commented Sep 18, 2018

Yes, please keep it open, the vsphere cloud plugin is completely useless until this is fixed.

@fejta-bot

This comment has been minimized.

Copy link

commented Dec 17, 2018

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

@fejta-bot

This comment has been minimized.

Copy link

commented Jan 16, 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@fejta-bot

This comment has been minimized.

Copy link

commented Feb 15, 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

commented Feb 15, 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.