From 9f7be1a10b0a53c6d8bd783a714fac2864186600 Mon Sep 17 00:00:00 2001 From: Peter Stachowski Date: Tue, 3 May 2016 12:36:15 -0400 Subject: [PATCH] Notification exceptions not sent back correctly With the new notification feature added recently, exceptions that occur on the guest are sent back to the conductor. Due to a mis-match in the code however, the wrong call is being issued. The conductor api makes a call to notify_exception instead of notify_exc_info. This has been fixed. Change-Id: Ib2e04bb903c92b4d570913aba2e985db63c45096 Closes-Bug: #1577848 --- .../notes/fix_notification_err_msgs-e52771108633c9cf.yaml | 4 ++++ trove/conductor/api.py | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) create mode 100644 releasenotes/notes/fix_notification_err_msgs-e52771108633c9cf.yaml diff --git a/releasenotes/notes/fix_notification_err_msgs-e52771108633c9cf.yaml b/releasenotes/notes/fix_notification_err_msgs-e52771108633c9cf.yaml new file mode 100644 index 0000000000..d01b2b828b --- /dev/null +++ b/releasenotes/notes/fix_notification_err_msgs-e52771108633c9cf.yaml @@ -0,0 +1,4 @@ +--- +fixes: + - Fixed wrong call in conductor when reporting a guest + notification exception. Bug 1577848 diff --git a/trove/conductor/api.py b/trove/conductor/api.py index e8d13112f7..617ccb5e7f 100644 --- a/trove/conductor/api.py +++ b/trove/conductor/api.py @@ -90,6 +90,6 @@ class API(object): context = self.context serialized = SerializableNotification.serialize(context, context.notification) - cctxt.cast(self.context, "notify_exception", + cctxt.cast(self.context, "notify_exc_info", serialized_notification=serialized, message=message, exception=exception)