This patch fixes a regression I introduced in
2d36facf14f4eb2742ba46274e04a73b5231aece. In that patch, I adjusted the
content_type for messages sent with the qpid notifier to be
'application/json' to match a change that went into the kombu notifier.
Unfortunately, it's wrong.
I assumed based on the kombu change that notifications were being json
encoded before being passed into the notification driver. That's not
the case. The message is a dict. So, just revert the change to set the
content_type and let Qpid encode the notification as 'amqp/map'.
(cherry picked from commit 5bed23cbc962d3c6503f0ff93e6d1e326efbd49d)
Reviewed: https:/ /review. openstack. org/6761 github. com/openstack/ glance/ commit/ 5838b6390353e4c 34762828684cee9 0410e4f8b1
Committed: http://
Submitter: Jenkins
Branch: stable/essex
commit 5838b6390353e4c 34762828684cee9 0410e4f8b1
Author: Russell Bryant <email address hidden>
Date: Tue Apr 24 12:24:39 2012 -0400
Fix content type for qpid notifier.
Fix bug 980872.
This patch fixes a regression I introduced in 4eb2742ba46274e 04a73b5231aece. In that patch, I adjusted the n/json' to match a change that went into the kombu notifier.
2d36facf14f
content_type for messages sent with the qpid notifier to be
'applicatio
Unfortunately, it's wrong.
I assumed based on the kombu change that notifications were being json
encoded before being passed into the notification driver. That's not
the case. The message is a dict. So, just revert the change to set the
content_type and let Qpid encode the notification as 'amqp/map'.
(cherry picked from commit 5bed23cbc962d3c 6503f0ff93e6d1e 326efbd49d)
Change-Id: I8ba039612d9603 377028ba72cb80a e89d675c741