yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Changed in: nova
     Assignee: Matt Riedemann (mriedem) => Surya Seetharaman (tssurya)

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Also affects: nova/pike
   Importance: Undecided
       Status: New

** Changed in: nova/pike
       Status: New => Confirmed

** Changed in: nova/queens
       Status: New => Confirmed

** Changed in: nova/pike
   Importance: Undecided => Medium

** Changed in: nova/queens
   Importance: Undecided => Medium

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

Title:
  Host is not unmapped when the host_mapping is deleted during
  delete_cell operation

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) pike series:
  Confirmed
Status in OpenStack Compute (nova) queens series:
  Confirmed

Bug description:
  Presently when a host_mapping is deleted during the nova-manage
  cell_v2 deleted_cell operation, the compute node record still remains
  with its mapped field set to 1. Due to this, if we delete a cell, and
  later create a new cell, the discover_hosts command will not work and
  the compute node will not get mapped to the new cell.

  Solution:

  Before the host is deleted during the delete_cell operation, the
  mapped field in compute_nodes table should be set to 0.

  This bug is similar to this one :
  https://bugs.launchpad.net/nova/+bug/1735719, hence what was done for
  the delete_host command should be done for the delete_cell command as
  well.

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