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
Currently, if one node is completely lost and the blockdevice is reattached to another node, ndm will detect that the block device is now on another node, but due to the nodeSelectors on the cspc the diskpool pod container will be in Pending state forever waiting for the lost container until the cspc is edited and the nodeSelector for that blockDevice is changed. Isn't there a way to auto update cspc using the data from ndm ?
The text was updated successfully, but these errors were encountered:
Hi, I am Vaishnavi a contributor to OpenForce 2022. I would like to work on this issue. I would be making a PR as soon as I am done with resolving the issue. Thank you.
Hi @Vaishnavi1411, Thanks for picking up the task please let me know if you need any help in understanding the problem statement in a more detailed way. OpenEBS team will be available in #openebs-dev slack channel in K8s workspace.
Currently, if one node is completely lost and the blockdevice is reattached to another node, ndm will detect that the block device is now on another node, but due to the nodeSelectors on the cspc the diskpool pod container will be in Pending state forever waiting for the lost container until the cspc is edited and the nodeSelector for that blockDevice is changed. Isn't there a way to auto update cspc using the data from ndm ?
The text was updated successfully, but these errors were encountered: