You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
create deployment pinned to an io-engine labelled node with a 2-replica volume
remove io-engine label from target node (target is moved to another node)
reset the node where deployment is pinned to
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...
The text was updated successfully, but these errors were encountered:
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:
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...The text was updated successfully, but these errors were encountered: