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

CSI NodeStage stuck on connecting after a Failover #1781

Open
tiagolobocastro opened this issue Dec 9, 2024 · 0 comments
Open

CSI NodeStage stuck on connecting after a Failover #1781

tiagolobocastro opened this issue Dec 9, 2024 · 0 comments

Comments

@tiagolobocastro
Copy link
Contributor

Describe the bug
When a volume has gone through failover and the target sits on another node, the uri in volumeattachment is incorrect.
In this case, if volume is NodeStaged then it will keep failing...

To Reproduce
Steps to reproduce the behavior:

  1. create deployment pinned to an io-engine labelled node with a 2-replica volume
  2. remove io-engine label from target node (target is moved to another node)
  3. reset the node where deployment is pinned to
  4. when node is back, pod will not go to running state

Expected behavior
Pod should go to running state

Additional context
As the CSI publish_context is immutable, this means we need to sync up with the openapi during a node stage...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant