[nova][placement] Zombie placement allocations DB records
Sometimes there are zombie placement allocations records left for hypervisors, meaning there are no mapping VMs running on those hosts, but the placement allocation records still show up in the database. Does this mean that nova conductor/scheduler would still think those resources have already been allocated, while in reality, there's no existing VMs mapped to those zombie placement allocations records?
Le jeu. 14 mars 2024 à 09:26, hai wu <haiwu.us@gmail.com> a écrit :
Sometimes there are zombie placement allocations records left for hypervisors, meaning there are no mapping VMs running on those hosts, but the placement allocation records still show up in the database.
Does this mean that nova conductor/scheduler would still think those resources have already been allocated, while in reality, there's no existing VMs mapped to those zombie placement allocations records?
The scheduler will indeed consider the resources as existing if there are orphaned allocations. That said, nova has a 'nova-manage placement audit' command that looks at orphaned allocations, so you can use it for checking whether those allocations are wrong and then delete them if you want. -S
Thanks! That command with ‘audit’ requires certain version. Is it possible to check version apis to ensure it is ok to upgrade nova manager to use that command? On Thu, Mar 14, 2024 at 4:50 AM Sylvain Bauza <sbauza@redhat.com> wrote:
Le jeu. 14 mars 2024 à 09:26, hai wu <haiwu.us@gmail.com> a écrit :
Sometimes there are zombie placement allocations records left for hypervisors, meaning there are no mapping VMs running on those hosts, but the placement allocation records still show up in the database.
Does this mean that nova conductor/scheduler would still think those resources have already been allocated, while in reality, there's no existing VMs mapped to those zombie placement allocations records?
The scheduler will indeed consider the resources as existing if there are orphaned allocations. That said, nova has a 'nova-manage placement audit' command that looks at orphaned allocations, so you can use it for checking whether those allocations are wrong and then delete them if you want.
-S
Thanks! That command with ‘audit’ requires certain version. Is it possible to check version apis to ensure it is ok to upgrade nova manager to use that command?
On Thu, 2024-03-14 at 07:51 -0500, hai wu wrote: this is a very old command so its unlikely you do not have it. it was intoduced in ussuri https://github.com/openstack/nova/commit/c03716be1f3e9fd5a5e9adf95860c7ce4bf... i dont think it has any specific api version requirement on the placement side. its basically just listing the allcoation on each resouce provider and then trying to corraltation them to either a migration or a instance.
On Thu, Mar 14, 2024 at 4:50 AM Sylvain Bauza <sbauza@redhat.com> wrote:
Le jeu. 14 mars 2024 à 09:26, hai wu <haiwu.us@gmail.com> a écrit :
Sometimes there are zombie placement allocations records left for hypervisors, meaning there are no mapping VMs running on those hosts, but the placement allocation records still show up in the database.
Does this mean that nova conductor/scheduler would still think those resources have already been allocated, while in reality, there's no existing VMs mapped to those zombie placement allocations records?
The scheduler will indeed consider the resources as existing if there are orphaned allocations. That said, nova has a 'nova-manage placement audit' command that looks at orphaned allocations, so you can use it for checking whether those allocations are wrong and then delete them if you want.
-S
participants (3)
-
hai wu
-
smooney＠redhat.com
-
Sylvain Bauza