yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Changed in: nova
     Assignee: (unassigned) => Dan Smith (danms)

** Changed in: nova
       Status: New => Triaged

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

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

** Also affects: nova/pike
   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/1735353

Title:
  build_request not deleted when using cellsV1 and local nova_api DB

Status in OpenStack Compute (nova):
  Triaged
Status in OpenStack Compute (nova) ocata series:
  New
Status in OpenStack Compute (nova) pike series:
  New

Bug description:
  Description
  ===========
  build_request not deleted when using cellsV1 and local nova_api

  Placement needs to be enabled in Newton.
  CellsV1 installations can deploy a placement service per child cell in order to have a more efficient schedule during the transition to cellV2. This requires a nova_api DB per cell.

  With this configuration the "build_request" that was created in the
  top nova_api DB is not deleted after the VM creation because is
  triggered in "conductor/manager.py" that runs in the child cell and is
  pointing to the local nova_api DB.

  This leaves new VMs in BUILD state.

  
  Expected result
  ===============
  build_request is removed from top nova_api DB.

  Actual result
  =============
  nova-cells tries to remove build_request from local cell nova_api DB.

  Environment
  ===========
  Nova newton

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