
This issue comes from this failing test in Tempest 'test_network_basic_ops.py' and function 'test_subnet_details' Not a whole lot of hits, but still good to track this. Root cause debugging notes by Salvatore Orlando, from the bug: "A waiter might fix the problem. The issue does not occur always - which means that cirros surely updated dns servers through DHCP (it would have been weird if it didn't but you can never know). However, once a subnet is updated on the neutron server there is a delay while the DHCP agent receives the update and reloads the corresponding dnsmasq process." Change-Id: I00ca193ab2001aca8c3decdb3209bcb33bb8e529
6 lines
198 B
YAML
6 lines
198 B
YAML
query: >
|
|
message:"MismatchError: set(['9.8.7.6']) != set(['1.2.3.4'])" AND
|
|
message:"Looking for servers: ['9.8.7.6']" AND
|
|
message:"Retrieved DNS nameservers: ['1.2.3.4']" AND
|
|
tags:"console"
|