Reviewed: https://review.openstack.org/516264 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e86604fb6579e2333ab9ab5a6926ef84d201152a Submitter: Zuul Branch: master
commit e86604fb6579e2333ab9ab5a6926ef84d201152a Author: Balazs Gibizer <[email protected]> Date: Mon Oct 30 12:59:12 2017 +0100 Document the real behavior of notify_on_state_change The documentation of the notify_on_state_change config param was incomplete and misleading. The code is untouched since 2012 so the document is updated to reflect the current behavior. Change-Id: I51d0deffc4f42ff2722a8d21aa6b8c8008c62723 Closes-Bug: #1535254 ** 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/1535254 Title: illustration of 'notify_on_state_change' are different from implementation Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) ocata series: Confirmed Status in OpenStack Compute (nova) pike series: Confirmed Bug description: I'm using liberty to get notifications from nova. And I found a problem with 'notify_on_state_change'. In the configuration doc, 'notify_on_state_change' means that "If set, send compute.instance.update notifications on instance state changes." Valid values are None, 'vm_state' and 'vm_and_task_state'. However, in current implementation, if it's set to 'vm_state', compute.instance.update notifications will be sent for all the state changes and it will be a special state change notification when the vm state changes. So as to 'vm_and_task_state'. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1535254/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
