Designate DNS – missing Notification in queue

[Arkady Shtempler]

Scenario:
1) Execute all tempest tests with:
sudo tox -e all-plugin – designate_tempest_plugin.tests

2) Run this script: http://pastebin.test.redhat.com/1021659 as “root” to detect missing Designate notification messages:

3) Actual result:
Missing notification messages has been detected.
Script output:

--> rabbitmqadmin get -V / -u test-admin -p testpass queue=notifications.info count=10000000
Error - notification message:dns.zone.touch was not detected:
Error - notification message:dns.record.update was not detected:
Error - notification message:dns.zone_transfer_request.update was not detected:
Error - notification message:dns.zone_transfer_accept.update was not detected:
Error - notification message:dns.zone_transfer_accept.delete was not detected:

I've added some print to the transfer_request_client.py trying to understand why "dns.zone_transfer_accept is missing by adding a print into its client:

@base.handle_errors
def delete_transfer_request(self, uuid, params=None):
    print('delete_transfer_request')
and in fact, I do see that the tempest does send these messages (not a surprise, we have cleanups and tests for delete)

 (test are PAS)
stack@ubuntu-0104-1338:~/
/usr/lib/python3.8/runpy.py:
  warn(RuntimeWarning(msg))
Tests running...
delete_transfer_request
delete_transfer_request
delete_transfer_request
delete_transfer_request
delete_transfer_request
delete_transfer_request
delete_transfer_request
delete_transfer_request
delete_transfer_request
delete_transfer_request

Ran 7 tests in 84.098s
OK

and I still don't see these notification messages, how could it be?
Tests are PASS, all cleanups seem to be OK.
There are no queues except the "notifications.info" with existing messages (in list command all the rest of the queues are shown with 0 messages).

4) Expected Result:
We would expect all the notification to be exist in the queue after executing Tempest tests (all APIs are covered in it).

[Takashi Kajinami (kajinamit)]

Can you check the notification driver([oslo_messaging_notifications] driver) used in nova and neutron ?
If the issue is found in TripleO deployment I think this is the problem with configuration made by TripleO, instead of a bug in software. See https://bugs.launchpad.net/tripleo/+bug/1958138 to find some more details.

[Takashi Kajinami (kajinamit)]

Sorry ignore what is written in #1 ... I misunderstood the "notification" mentioned here.

It'd be still useful to check whether notification driver is enabled in "designate".
Looking at the output of the test script, it expects notification from designate service thus notification driver should NOT be 'noop' in designate.conf.