designate.conf uses a hardcoded messaging (v1) notification driver
Bug #1709840 reported by
Dmitrii Shcherbakov
This bug report is a duplicate of:
Bug #1710831: [any][17.08] notifications_designate.info queue has many unconsumed "dns.pool.update" messages due to ceilometer and designate notification_topics mismatch and missing events in event_definitions.yaml.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Designate Charm |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Currently we use a deprecated notification_driver option in the [DEFAULT] section.
We should use the driver option in oslo_messaging_
[oslo_messaging
driver = messagingv2
Should be the same as in these reviews:
https:/
https:/
https:/
| tags: | added: telemetry-refresh |
| Changed in charm-designate: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 18.02 |
To post a comment you must log in.
