yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

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

** Changed in: nova/ocata
       Status: New => In Progress

** Changed in: nova/ocata
   Importance: Undecided => High

** Changed in: nova/ocata
     Assignee: (unassigned) => melanie witt (melwitt)

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

Title:
  Build notification in conductor fails to send due to InstanceNotFound

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  In Progress
Status in OpenStack Compute (nova) pike series:
  In Progress

Bug description:
  I found this issue while working on improving the CellDatabases
  fixture by defaulting untargeted DB access to 'cell0' instead of
  'cell1'.

  While building an instance in conductor, it sends a notification about
  the changed state using notifications.send_update_with_states. In
  notifications.send_update_with_states, one of the arguments is an
  Instance and if an attribute needs to be lazy-loaded, (example: tags,
  as part of the InstanceUpdatePayload) and the load method contains a
  _check_instance_exists_in_project call in the DB layer,
  InstanceNotFound is raised at that point because the context wasn't
  targeted to the instance's cell.

  We need to target the context in case the notification call needs to
  load something from the instance's cell database.

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