Reviewed:  https://review.openstack.org/415857
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=655942069aa77abad90a742cd47690a81987e9d7
Submitter: Jenkins
Branch:    master

commit 655942069aa77abad90a742cd47690a81987e9d7
Author: Balazs Gibizer <balazs.gibi...@ericsson.com>
Date:   Fri Jan 13 11:00:25 2017 +0100

    handle uninited fields in notification payload
    
    Due to the not strict handling of uninitialized fields during
    notification payload population it is possible that the emitted
    notification missing some of the fields defined in the schema.
    
    There are two problematic cases:
    1) no load tirggered for lazy loaded fields. If the field was not
       loaded it is not added to the payload.
    2) uninitialized, not lazy loadable fields are not added to the
       payload.
    
    This patch makes sure that lazy load is triggered. If the field is
    not lazy loadable and also not initialized then related payload
    field will be set to None. If the payload field is not nullable
    the code will fail to make sure that the inconsistency is detected.
    
    The following changes cannot be split to different commits because
    as soon as the generic schema population code is fixed every listed
    notification starts behaving differently.
    
    In some cases the availability_zone field of the Service object is left
    unitialized by both the constructor and the obj_load_attr function this
    caused that the availability_zone field of the service.update
    notification was missing from the emitted notification payload.
    
    The extra_specs field of the Flavor object is not lazy loadable and not
    initialized in the Flavor destroy case. So the extra_specs field of the
    FlavorPayload needed to be made nullable.
    
    The projects field of the Flavor object is lazy loaded but when the
    Flavor object is loaded as part of an Instance object Flavor is
    orphaned and no lazy load is allowed on that Flavor object. In this
    case the projects field of the FlavorPayload will be set to None to
    signal that the information is not available. This also means that
    the projects field of the FlavorPayload needed to be changed to
    nullable.
    
    The hosts and id fields of the Aggregate object is not initialized
    during the create of the Aggregate before the aggregate.create.start
    needs to be sent. Therefore these fields needs to be nullable.
    
    Closes-Bug: #1653221
    Change-Id: Ib122cd98ee0cc31938d5ff1d5c753053267a3bd4


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
  availability_zone field is missing from the service.update
  notification payload

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===========

  The payload of the service.update notification is defined to contain
  the availability_zone of the service however if there is no
  availability zone is associated to the service the field was missing
  from the notification payload.

  Steps to reproduce
  ==================
  1) set up a devstack with log notification driver
  2) disable the state of one of the nova service with
  nova service disable
  3) check the log to see the content of the emitted service.update notification

  Expected result
  ===============
  {
      "priority": "INFO",
      "payload": {
          "nova_object.namespace": "nova",
          "nova_object.name": "ServiceStatusPayload",
          "nova_object.version": "1.0",
          "nova_object.data": {
              "host": "host1",
              "disabled": false,
              "last_seen_up": "2012-10-29T13:42:05Z",
              "binary": "nova-compute",
              "topic": "compute",
              "disabled_reason": null,
              "report_count": 1,
              "forced_down": false,
              "version": 15
              "availability_zone": null
          }
      },
      "event_type": "service.update",
      "publisher_id": "nova-compute:host1"
  }

  
  Actual result
  =============
  {
      "priority": "INFO",
      "payload": {
          "nova_object.namespace": "nova",
          "nova_object.name": "ServiceStatusPayload",
          "nova_object.version": "1.0",
          "nova_object.data": {
              "host": "host1",
              "disabled": false,
              "last_seen_up": "2012-10-29T13:42:05Z",
              "binary": "nova-compute",
              "topic": "compute",
              "disabled_reason": null,
              "report_count": 1,
              "forced_down": false,
              "version": 15
          }
      },
      "event_type": "service.update",
      "publisher_id": "nova-compute:host1"
  }

  Environment
  ===========
  devstack with nova master a74d3ae4e815e3727961ef67bd801dada0267a0b

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to