Bug 1810470: carry: Check for optimizing state too #167
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.
Without checking for optimizing state the resizing operation takes far
too long and hence we are going to bring it back.
The reason for bringing optimizing check back is the root cause of previous flake was volume was entering desired size before it was done being modified (so
describeVolumereports higher size while volume is still being modified), so optimizing state was not root of the problem.On the other hand - not checking for optimizing state makes resizing very slow
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1810470