yahoo-eng-team team mailing list archive

[Chen <1785193@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
Changing a node's cell through nova.conf and then restarting nova-compute will result in duplicate hypervisor records for that node.

Steps to reproduce
==================
1. edit nova.conf on a compute node, to update [database].connection and [DEFAULT].transport_url to another cell's.
2 restart nova-compute service
3 nova hypervisor-list

Expected result
===============
Not sure what to expect yet.

Actual result
=============
+--------------------------------------+---------------------+-------+---------+
| ID                                   | Hypervisor hostname | State | Status  |
+--------------------------------------+---------------------+-------+---------+
| a40d3d87-21c0-5728-a9ea-c2bdc544a148 | compute             | up    | enabled |
| b87f790c-4160-4540-b4a9-2dbcfbe9d019 | compute             | up    | enabled |
+--------------------------------------+---------------------+-------+---------+

The following error is also captured in nova-compute.log:

nova.scheduler.client.report [req-ee9c94db-9ea6-7358-97a7-444a31db3a2c -
- - - -] [req-7b4fa3d6-3f17-5895-a3c5-54562d02b10b] Failed to create
resource provider record in placement API for UUID a40d3d87-21c0-5728
-a9ea-c2bdc544a148. Got 409: {"errors": [{"status": 409, "request_id":
"req-7b4fa3d6-3f17-5895-a3c5-54562d02b10b", "detail": "There was a
conflict when trying to complete your request.\n\n Conflicting resource
provider name: compute already exists.  ", "title": "Conflict"}]}.

Environment
===========
openstack-nova-compute-17.0.5-1.el7.noarch (queens release)

Logs & Configs
==============
not related

** Affects: nova
     Importance: Undecided
     Assignee: Chen (chenn2)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Chen (chenn2)

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

Title:
  changing a node's cell results in duplicate hypervisors

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Changing a node's cell through nova.conf and then restarting nova-compute will result in duplicate hypervisor records for that node.

  Steps to reproduce
  ==================
  1. edit nova.conf on a compute node, to update [database].connection and [DEFAULT].transport_url to another cell's.
  2 restart nova-compute service
  3 nova hypervisor-list

  Expected result
  ===============
  Not sure what to expect yet.

  Actual result
  =============
  +--------------------------------------+---------------------+-------+---------+
  | ID                                   | Hypervisor hostname | State | Status  |
  +--------------------------------------+---------------------+-------+---------+
  | a40d3d87-21c0-5728-a9ea-c2bdc544a148 | compute             | up    | enabled |
  | b87f790c-4160-4540-b4a9-2dbcfbe9d019 | compute             | up    | enabled |
  +--------------------------------------+---------------------+-------+---------+

  The following error is also captured in nova-compute.log:

  nova.scheduler.client.report [req-ee9c94db-9ea6-7358-97a7-444a31db3a2c
  - - - - -] [req-7b4fa3d6-3f17-5895-a3c5-54562d02b10b] Failed to create
  resource provider record in placement API for UUID a40d3d87-21c0-5728
  -a9ea-c2bdc544a148. Got 409: {"errors": [{"status": 409, "request_id":
  "req-7b4fa3d6-3f17-5895-a3c5-54562d02b10b", "detail": "There was a
  conflict when trying to complete your request.\n\n Conflicting
  resource provider name: compute already exists.  ", "title":
  "Conflict"}]}.

  Environment
  ===========
  openstack-nova-compute-17.0.5-1.el7.noarch (queens release)

  Logs & Configs
  ==============
  not related

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