Change setting for events-publisher should restart services, but does not
Bug #1880255 reported by
Xav Paice
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Ceilometer Charm |
Fix Released
|
High
|
Edward Hope-Morley | ||
Bug Description
Charm 20.05, cs:ceilometer-273, cloud:xenial-queens
When changing the setting for events-publisher from default to "", to avoid alarm.all.sample filling up without a consumer, we had to manually restart the Ceilometer services on all units in order for the change to take effect. The config-changed hook should do that.
Revision history for this message
| Edward Hope-Morley (hopem) wrote | #1 |
| Changed in charm-ceilometer: | |
| milestone: | none → 20.08 |
| assignee: | nobody → Edward Hope-Morley (hopem) |
| importance: | Undecided → High |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to charm-ceilometer (master) | #2 |
| Changed in charm-ceilometer: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to charm-ceilometer (master) | #3 |
| Changed in charm-ceilometer: | |
| status: | In Progress → Fix Committed |
| Changed in charm-ceilometer: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Confirmed, this is because the render context for event_pipeline.yaml is not programmed to restart any services when its contents change. Easily fixed, will submit patch shortly.