Skip to content

Commit 49817d3

Browse files
committed
Handle oslo.messaging ping endpoint
We have a test that attempts to emulate a messaging endpoint and fails if anything other than the endpoint's target property is inspected. With the addition of the ping endpoint in I51cf67e060f240e6eb82260e70a057fe599f9063, this now blows up with the latest oslo.messagin release. To handle this situation, our fake class just needs to also check for the oslo_rpc_server_ping attribute. Change-Id: I970c953f9c21df99fac5f572f9e9dca5c615f06c Signed-off-by: Sean McGinnis <[email protected]>
1 parent 6bb1639 commit 49817d3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

nova/tests/unit/test_test.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ def test_rpc_consumer_isolation(self):
5050
class NeverCalled(object):
5151

5252
def __getattribute__(self, name):
53-
if name == 'target':
53+
if name == 'target' or name == 'oslo_rpc_server_ping':
5454
# oslo.messaging 5.31.0 explicitly looks for 'target'
5555
# on the endpoint and checks it's type, so we can't avoid
5656
# it here, just ignore it if that's the case.

0 commit comments

Comments
 (0)