- Situation arises when trying to remove/delete the Compute service resource provider from Placement service because the compute was removed then re-added with the
same hostnameand delete operation failed as one of the orphaned VM was showing some allocation for this Compute in placement service records.
- Other scenario can happen in which a compute service host is having problems so the administrator forces it down and evacuates servers from it. Note that in this case
evacuatesrefers to the server evacuate action, not live migrating all servers from the running compute service. Assume the compute host is down and fenced.In this case, the servers may have allocations tracked in placement against both the down source compute node and their current destination compute host. So, the VMs can show allocation in both compute and the allocation from removed Compute provider should be deleted for those VMs.
- Red Hat OpenStack Platform 13 (RHOSP)
- Red Hat OpenStack Platform 16 (RHOSP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.