No way to disable notifications from services
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Emilien Macchi |
Bug Description
We recently added an environment to disable telemetry services in the overcloud[1], but it turns out this is actually dangerous in a real-world deployment. Without anything consuming notifications, the rabbit queues fill up and eventually start causing failures due to an inability to deal with that many pending messages.
We need to be able to set notification_driver for the other services to "noop", but currently this is not exposed via t-h-t. Ideally these would be wired in as template parameters so they could be set in the disable-telemetry environment file.
I believe this is already exposed via the puppet modules[2], so it should be possible to address mostly within t-h-t.
1: https:/
2: https:/
Changed in tripleo: | |
assignee: | nobody → Emilien Macchi (emilienm) |
Changed in tripleo: | |
assignee: | nobody → Emilien Macchi (emilienm) |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Note, the easier fix would be setting expiration for notification queues globally