Designate DNS – missing Notification in queue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
New
|
Undecided
|
Unassigned |
Bug Description
Scenario:
1) Execute all tempest tests with:
sudo tox -e all-plugin – designate_
2) Run this script: http://
3) Actual result:
Missing notification messages has been detected.
Script output:
--> rabbitmqadmin get -V / -u test-admin -p testpass queue=notificat
Error - notification message:
Error - notification message:
Error - notification message:
Error - notification message:
Error - notification message:
I've added some print to the transfer_
@base.handle_errors
def delete_
print(
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-
/usr/lib/
warn(
Tests running...
delete_
delete_
delete_
delete_
delete_
delete_
delete_
delete_
delete_
delete_
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.
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).
Can you check the notification driver( [oslo_messaging _notifications] driver) used in nova and neutron ? /bugs.launchpad .net/tripleo/ +bug/1958138 to find some more details.
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:/