From cba2d8a637ba02e50816381eba5bcf6f1bfbe472 Mon Sep 17 00:00:00 2001 From: Phil Day Date: Thu, 31 Jan 2013 17:08:17 +0000 Subject: instance.update notifications don't always identify the service 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. This change makes sure that the correct service is identified even when running conductor in local mode Change-Id: I1b22c0b46040f51ba715a4d9fa19ef4c98359070 --- nova/compute/api.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'nova/compute') diff --git a/nova/compute/api.py b/nova/compute/api.py index a9d0a1bdd..e4c885af1 100644 --- a/nova/compute/api.py +++ b/nova/compute/api.py @@ -186,7 +186,7 @@ class API(base.Base): (old_ref, instance_ref) = self.db.instance_update_and_get_original( context, instance_uuid, kwargs) - notifications.send_update(context, old_ref, instance_ref) + notifications.send_update(context, old_ref, instance_ref, 'api') return instance_ref -- cgit