Skip to content

Conversation

github-actions[bot]
Copy link

This PR contains a snapshot of wallaby from upstream stable/wallaby.

kajinamit and others added 2 commits June 6, 2022 08:35
When a compute node goes down and all instances on the compute node
are evacuated, allocation records about these instance are still left
in the source compute node until nova-compute service is again started
on the node. However if a compute node is completely broken, it is not
possible to start the service again.
In this situation deleting nova-compute service for the compute node
doesn't delete its resource provider record, and even if a user tries
to delete the resource provider, the delete request is rejected because
allocations are still left on that node.

This change ensures that remaining allocations left by successful
evacuations are cleared when deleting a nova-compute service, to avoid
any resource provider record left even if a compute node can't be
recovered. Migration records are still left in 'done' status to trigger
clean-up tasks in case the compute node is recovered later.

Conflicts:
	nova/scheduler/client/report.py

Closes-Bug: #1829479
Change-Id: I3ce6f6275bfe09d43718c3a491b3991a804027bd
(cherry picked from commit e5a34ff)
(cherry picked from commit 037e588)
@github-actions github-actions bot requested a review from a team as a code owner February 19, 2024 08:23
@github-actions github-actions bot added automated Automated action performed by GitHub Actions synchronisation labels Feb 19, 2024
@markgoddard markgoddard merged commit 0eeac39 into stackhpc/wallaby Feb 19, 2024
@markgoddard markgoddard deleted the upstream/wallaby-2024-02-19 branch February 19, 2024 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated Automated action performed by GitHub Actions synchronisation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants