fix: throw error if volume is down state and with pending status, it might not recover #2383
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
In case the underlying storage driver fails to create the volume and puts it in down state and keep it pending forever due to kvdb miss, it could also be that it is unable to rollback too since the kvdb is down.
the check added helps us break out of that loop.
Which issue(s) this PR fixes (optional)
PWX-35130
Testing Notes
While creating a volume if the kvdb is unavailable and the volume enters a down state
CSI should throw an error