Do you have any other service running that may consume the messages like Ceilometer? Can you check in your rabbit that Designate is the consumer in the queue you are sending the notifications to?
If you have more than one consumer (other than Designate), then may be you can try configuring a separate queue for designate sink in Neutron and Nova and have the sink handler listen to this new queue. On Wed, Aug 5, 2015 at 1:53 AM, Jaime Fernández <jjja...@gmail.com> wrote: > We've migrated our OST platform from qpid to rabbitmq. After this > migration, we don't receive any notification from nova/neutron in > designate-sink (so there is no DNS registration for new VMs or floating > IPs). However, designate is correctly integrated with rabbitmq because > designate-api replies successfully to API requests. > > There is a user/password for designate in rabbitmq and every rabbit user > has all the possible permissions. > > Do you have any hint? I don't think it's a wrong configuration in > designate because it was already working with qpid. Could you suggest where > I should inspect in order to find the problem? > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
