OpenStack Designate Charm

  1. Bug #1710831
  2. Comment #22

Comment 22 for bug 1710831

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to charm-designate (master)

Reviewed: https://review.openstack.org/540833
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=269ba2bb1d48ea515b315a9a7226dc010784ccaa
Submitter: Zuul
Branch: master

commit 269ba2bb1d48ea515b315a9a7226dc010784ccaa
Author: Dmitrii Shcherbakov <email address hidden>
Date: Mon Feb 5 14:22:54 2018 +0300

    reintroduce designate_notifications topic

    Change I709a6aca1843918a67d43bc4808a0013168fbc55, commit hash
    1879b16ea543b076c9555fdc0258355d39af9ad0 introduced a
    backwards-incompatible change in the fact that designate stopped
    consuming messages using designate_notifications topic from nova and
    neutron.

    While designate.conf change in the mentioned commit is needed to make
    sure Designate emits its own notifications on the topic that ceilometer
    uses ("notifications"), for nova and neutron to designate notifications
    a separate topic should be used as before.

    A revert of the previous commit is not done as it addresses the previous
    issue but introduces a new one.

    Change-Id: I6b5fd1b5f9bae1cd4a1683fd476b456e81d6c79e
    Related-Bug: #1710831