yahoo-eng-team team mailing list archive

[Sylvain Bauza <1956432@xxxxxxxxxxxxxxxxxx>]

This is expected behaviour. As we assume that we can only evacuate when
a nova-compute service is down, there are no ways for the nova-compute
service to ask Placement to remove those allocations.

That's only when nova-compute is back up that we can delete those
allocations. We also provide some nova-manage commands for deleting
orphaned allocations in case of a non-recoverable compute service. See
https://docs.openstack.org/nova/latest/cli/nova-manage.html#placement-
audit

** Changed in: nova
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1956432

Title:
  Old allocation of VM is not deleted after evacuating

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  I found that the old instance allocation in placement is not deleted after executing evacuate, 
  it will lead to wrong resources info of old compute node.

  
  ---------

  MariaDB [placement]> select * from  allocations where consumer_id='4c6c29e7-a1f0-4dac-a3ef-a98b5598abe9';
  +---------------------+------------+-------+----------------------+--------------------------------------+-------------------+------+
  | created_at          | updated_at | id    | resource_provider_id | consumer_id                          | resource_class_id | used |
  +---------------------+------------+-------+----------------------+--------------------------------------+-------------------+------+
  | 2022-01-05 08:23:19 | NULL       | 18315 |                   11 | 4c6c29e7-a1f0-4dac-a3ef-a98b5598abe9 |                 2 |    1 |
  | 2022-01-05 08:23:19 | NULL       | 18318 |                   11 | 4c6c29e7-a1f0-4dac-a3ef-a98b5598abe9 |                 1 |  512 |
  | 2022-01-05 08:23:19 | NULL       | 18321 |                   11 | 4c6c29e7-a1f0-4dac-a3ef-a98b5598abe9 |                 0 |    1 |
  | 2022-01-05 08:23:19 | NULL       | 18324 |                   33 | 4c6c29e7-a1f0-4dac-a3ef-a98b5598abe9 |                 0 |    1 |
  | 2022-01-05 08:23:19 | NULL       | 18327 |                   33 | 4c6c29e7-a1f0-4dac-a3ef-a98b5598abe9 |                 1 |  512 |
  | 2022-01-05 08:23:19 | NULL       | 18330 |                   33 | 4c6c29e7-a1f0-4dac-a3ef-a98b5598abe9 |                 2 |    1 |
  +---------------------+------------+-------+----------------------+--------------------------------------+-------------------+------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1956432/+subscriptions