yahoo-eng-team team mailing list archive

[Balazs Gibizer <balazs.gibizer@xxxxxxxxxxxx>]

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

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

Title:
  fixed_ips missing from compute.update.end notifications

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  This is part of a series of reports around discrepancies between the
  nova servers API response and notification payloads as affects
  Searchlight; see https://bugs.launchpad.net/nova/+bug/1637634 for
  background.

  An example API response to retrieve a server's information is at
  http://paste.openstack.org/show/xbv2CwtHnhhl1nLLiJeN/

  An example compute.create.end notification is at
  http://paste.openstack.org/show/zG5aJeUpC3LAGr0J0P2T/

  An example compute.update.end notification is at
  http://paste.openstack.org/show/uwh1izVsaW5eg7zDrgFm/

  fixed_ips is present in compute.create.end notifications and contains
  IP/MAC/network information related to neutron ports added during
  instance creation. This field is missing from compute.update.end
  notification payloads, and this causes us a problem because it's much
  better from Searchlight's perspective if notification payloads are
  consistent and complete representations of a resource's state.

  Searchlight currently has an optimization to detect whether
  compute.update.end notifications represent scheduler state changes
  like suspending, resuming, etc, and for those does a partial update.
  For other events it currently has to go the nova API to get the
  current representation of the affected server.

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