[openstack/nova] Nanny for orphaned migrations#9335
Draft
fwiesel wants to merge 1 commit into
Draft
Conversation
Member
Author
|
Draft, as it depends on another pr |
fwiesel
force-pushed
the
nova-nanny-db-error-out-orphaned-migrations
branch
from
ba1715f to
4376075
Compare
Since we should only have few migrations ongoing, the query should be quite fast. We trigger it often as it will be a blocker to re-installing kvm hosts, as they get decomissioned each time, but have to wait for no migrations being associated with the compute-host. Disabled for now, so we can activate it selectively in some regions for now.
fwiesel
force-pushed
the
nova-nanny-db-error-out-orphaned-migrations
branch
from
4376075 to
db7c1da
Compare
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.
Since we should only have few migrations ongoing, the query should be quite fast. We trigger it often as it will be a blocker to re-installing kvm hosts, as they get decomissioned each time, but have to wait for no migrations being associated with the compute-host.