yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #69214
[Bug 1535254] Re: illustration of 'notify_on_state_change' are different from implementation
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => Balazs Gibizer (balazs-gibizer)
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Confirmed
** Changed in: nova/pike
Status: New => Confirmed
** Changed in: nova/ocata
Importance: Undecided => Medium
** Changed in: nova/pike
Importance: Undecided => Medium
--
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):
In Progress
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
References