[SAP] Fix scheduler handling of empty pools list from backends#327
Open
hemna wants to merge 1 commit into
Open
[SAP] Fix scheduler handling of empty pools list from backends#327hemna wants to merge 1 commit into
hemna wants to merge 1 commit into
Conversation
When a backend reports an empty pools list [] (e.g. due to a vCenter connectivity issue), the scheduler would wipe all cached pools and later create a synthetic pool that doesn't correspond to any real datastore, causing volume creation failures. Mark all existing pools as down instead, so the scheduler preserves pool state and avoids scheduling to nonexistent pools. Change-Id: If6e349fdc5725169e922ac2b1aa2f85effaf43c0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When a backend reports an empty pools list [] (e.g. due to a vCenter connectivity issue), the scheduler would wipe all cached pools and later create a synthetic pool that doesn't correspond to any real datastore, causing volume creation failures.
Mark all existing pools as down instead, so the scheduler preserves pool state and avoids scheduling to nonexistent pools.
Change-Id: If6e349fdc5725169e922ac2b1aa2f85effaf43c0