notifications.error should be consumed or not be sent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Medium
|
gordon chung |
Bug Description
In a havana environment, I have noticed that there will be a message sent to notifications.error when nova did live-migrate but fail. After tracking the code, I think in stable/icehouse branch, the same issue exists.
In Ceilometer stable/icehouse, we just comsumes messages send to notifications.info topic, see:
https:/
In Nova stable/icehouse, if instance migrate fails, or something other important vm related action fails, a message will be sent to notifications.
https:/
https:/
https:/
The problem is that, Ceilometer has connected to many OpenStack services, if Nova has this issue, other services may too.
I don't know why service sends a notification which will not be consumed, this only makes operator confuse and (may be low but true) adds AMQP's burden.
So my opinion would be:
1) modify Ceilometer's code, let's consume the notifications.
2) notify other project's contributor, let them stop to send such notifications
Changed in ceilometer: | |
assignee: | nobody → ZhiQiang Fan (aji-zqfan) |
Changed in ceilometer: | |
assignee: | ZhiQiang Fan (aji-zqfan) → gordon chung (chungg) |
Changed in ceilometer: | |
milestone: | none → kilo-3 |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | kilo-3 → 2015.1.0 |
I agree with the first one.
But I don't think dropping them is a good idea. If we dealt with the notifications.info messages, no reason to ignore higher level ones. Maybe we can discuss the topic in ML.
Thanks.