OpenStack Compute (nova)

instance.update notifications don't always identify the servicev

Bug #1111498 reported by Phil Day
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Phil Day
OpenStack Compute (nova) 2013.1 "grizzly"

Bug Description

instance_update in conductor/manager.py doesn't identify the service when calling notifications.send_update(), resulting in mesages on the notification queue having a service value of None.

Phil Day (philip-day)
Changed in nova:
assignee: nobody → Phil Day (philip-day)
status: New → In Progress
Revision history for this message
Phil Day (philip-day) wrote :

https://review.openstack.org/#/c/20919/

Changed in nova:
status: In Progress → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: none → grizzly-3
Thierry Carrez (ttx)
Changed in nova:
milestone: grizzly-3 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.