yahoo-eng-team team mailing list archive

Thread
Date
[Bug 2077009] [NEW] Nova doesn't clean claims after evacuation

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Viktor Křivák <2077009@xxxxxxxxxxxxxxxxxx>
Date: Wed, 14 Aug 2024 14:59:10 -0000
Reply-to: Bug 2077009 <2077009@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx
Public bug reported:

When a VM is evacuated from the failed server without stating explicit
destination (i.e. letting the scheduler decide) claims to the old
hypervisor in placement are never deleted.

How to replicate:
- Place VM on the hypervisor
- Check that claims are OK:
+--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
| resource_provider                    | generation | resources                     | project_id                       | user_id                          |
+--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
| 229cce5f-3b87-438a-baa9-539be0fc9bd8 |          5 | {'VCPU': 1, 'MEMORY_MB': 256} | 4facfb06808a4621b4f47123a0184a4a | 15da82817e56446198fcdd870a45d8f4 |
+--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
- Stop the hypervisor and after nova pronounce hypervisor dead run evacuation without stating the destination
- Check claims again
+--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
| resource_provider                    | generation | resources                     | project_id                       | user_id                          |
+--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
| 229cce5f-3b87-438a-baa9-539be0fc9bd8 |          6 | {'VCPU': 1, 'MEMORY_MB': 256} | 4facfb06808a4621b4f47123a0184a4a | 15da82817e56446198fcdd870a45d8f4 |
| 5395932e-b5e0-4a0c-be6a-7328af751642 |         14 | {'VCPU': 1, 'MEMORY_MB': 256} | 4facfb06808a4621b4f47123a0184a4a | 15da82817e56446198fcdd870a45d8f4 |
+--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+


Result: Claims to the old hypervisor have not been deleted
Expected results: Only claims for new hypervisor exist


It is possible regression of https://bugs.launchpad.net/nova/+bug/1896463
It probably happened when the resource tracker was improved and the whole migration procedure was rewritten. Migration/resize work because claims deletion happens in confirm/revert action, however, evacuation doesn't have anything like that and so it's never deleted.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/2077009

Title:
  Nova doesn't clean claims after evacuation

Status in OpenStack Compute (nova):
  New

Bug description:
  When a VM is evacuated from the failed server without stating explicit
  destination (i.e. letting the scheduler decide) claims to the old
  hypervisor in placement are never deleted.

  How to replicate:
  - Place VM on the hypervisor
  - Check that claims are OK:
  +--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
  | resource_provider                    | generation | resources                     | project_id                       | user_id                          |
  +--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
  | 229cce5f-3b87-438a-baa9-539be0fc9bd8 |          5 | {'VCPU': 1, 'MEMORY_MB': 256} | 4facfb06808a4621b4f47123a0184a4a | 15da82817e56446198fcdd870a45d8f4 |
  +--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
  - Stop the hypervisor and after nova pronounce hypervisor dead run evacuation without stating the destination
  - Check claims again
  +--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
  | resource_provider                    | generation | resources                     | project_id                       | user_id                          |
  +--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+
  | 229cce5f-3b87-438a-baa9-539be0fc9bd8 |          6 | {'VCPU': 1, 'MEMORY_MB': 256} | 4facfb06808a4621b4f47123a0184a4a | 15da82817e56446198fcdd870a45d8f4 |
  | 5395932e-b5e0-4a0c-be6a-7328af751642 |         14 | {'VCPU': 1, 'MEMORY_MB': 256} | 4facfb06808a4621b4f47123a0184a4a | 15da82817e56446198fcdd870a45d8f4 |
  +--------------------------------------+------------+-------------------------------+----------------------------------+----------------------------------+

  
  Result: Claims to the old hypervisor have not been deleted
  Expected results: Only claims for new hypervisor exist

  
  It is possible regression of https://bugs.launchpad.net/nova/+bug/1896463
  It probably happened when the resource tracker was improved and the whole migration procedure was rewritten. Migration/resize work because claims deletion happens in confirm/revert action, however, evacuation doesn't have anything like that and so it's never deleted.

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