yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1908405] [NEW] Nova-manage placement audit 'resource_provider' argument does not work

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Andrew Bonney <1908405@xxxxxxxxxxxxxxxxxx>
Date: Wed, 16 Dec 2020 13:17:02 -0000
Reply-to: Bug 1908405 <1908405@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Public bug reported:

Running 'nova-manage placement audit --verbose' results in various
reports of orphaned resources. However, if one resource provider is
selected and 'nova-manage placement --verbose --resource_provider
<uuid>' is used this always indicates that the resource provider does
not exist.

For example:

(nova-21.0.1) root@infra1-nova-api-container-c49119df:~# nova-manage placement audit --verbose                                                         
Allocations were set against consumer UUID 7cbee49d-6af9-4cf7-98e9-b374872fe35b but no existing instances or active migrations are related. 
Allocations for consumer UUID 7cbee49d-6af9-4cf7-98e9-b374872fe35b on Resource Provider 84840425-2122-4452-ab44-205c262b5ec5 can be deleted: {'VCPU': 1, 'MEMORY_MB': 512}

(nova-21.0.1) root@infra1-nova-api-container-c49119df:~# nova-manage placement audit --verbose --resource_provider 84840425-2122-4452-ab44-205c262b5ec5
Resource provider with UUID 84840425-2122-4452-ab44-205c262b5ec5 does not exist.

This is caused by an '&' rather than '?' in the construction of a URL
query parameter at
https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L2670

Fixing this results in:

(nova-21.0.1) root@infra1-nova-api-container-c49119df:~# nova-manage placement audit --verbose --resource_provider 84840425-2122-4452-ab44-205c262b5ec5
Allocations were set against consumer UUID 7cbee49d-6af9-4cf7-98e9-b374872fe35b but no existing instances or active migrations are related. 
Allocations for consumer UUID 7cbee49d-6af9-4cf7-98e9-b374872fe35b on Resource Provider 84840425-2122-4452-ab44-205c262b5ec5 can be deleted: {'VCPU': 1, 'MEMORY_MB': 512}

I'll submit a patch shortly.

** 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/1908405

Title:
  Nova-manage placement audit 'resource_provider' argument does not work

Status in OpenStack Compute (nova):
  New

Bug description:
  Running 'nova-manage placement audit --verbose' results in various
  reports of orphaned resources. However, if one resource provider is
  selected and 'nova-manage placement --verbose --resource_provider
  <uuid>' is used this always indicates that the resource provider does
  not exist.

  For example:

  (nova-21.0.1) root@infra1-nova-api-container-c49119df:~# nova-manage placement audit --verbose                                                         
  Allocations were set against consumer UUID 7cbee49d-6af9-4cf7-98e9-b374872fe35b but no existing instances or active migrations are related. 
  Allocations for consumer UUID 7cbee49d-6af9-4cf7-98e9-b374872fe35b on Resource Provider 84840425-2122-4452-ab44-205c262b5ec5 can be deleted: {'VCPU': 1, 'MEMORY_MB': 512}

  (nova-21.0.1) root@infra1-nova-api-container-c49119df:~# nova-manage placement audit --verbose --resource_provider 84840425-2122-4452-ab44-205c262b5ec5
  Resource provider with UUID 84840425-2122-4452-ab44-205c262b5ec5 does not exist.

  This is caused by an '&' rather than '?' in the construction of a URL
  query parameter at
  https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L2670

  Fixing this results in:

  (nova-21.0.1) root@infra1-nova-api-container-c49119df:~# nova-manage placement audit --verbose --resource_provider 84840425-2122-4452-ab44-205c262b5ec5
  Allocations were set against consumer UUID 7cbee49d-6af9-4cf7-98e9-b374872fe35b but no existing instances or active migrations are related. 
  Allocations for consumer UUID 7cbee49d-6af9-4cf7-98e9-b374872fe35b on Resource Provider 84840425-2122-4452-ab44-205c262b5ec5 can be deleted: {'VCPU': 1, 'MEMORY_MB': 512}

  I'll submit a patch shortly.

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