97d457f0af
It would be helpful if "Timed out waiting for <service>" log messages at least specified on which `reply_q` it was waited for. Example without the reply_q: ``` 12228 2020-09-14 14:56:37.187 7 WARNING nova.conductor.api [req-1e081db6-808b-4af1-afc1-b87db7839394 - - - - -] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? Reattempting establishment of nova-conductor connection...: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 1640e7ef6f314451ba9a75d9ff6136ad ``` Example after adding the reply_q: ``` 12228 2020-09-14 14:56:37.187 7 WARNING nova.conductor.api [req-1e081db6-808b-4af1-afc1-b87db7839394 - - - - -] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? Reattempting establishment of nova-conductor connection...: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply (reply_2882766a63b540dabaf7d019cf0c0cda) to message ID 1640e7ef6f314451ba9a75d9ff6136ad ``` It could help us to more merely debug and observe if something went wrong with a reply queue. Change-Id: Ied2c881c71930dc631919113adc00112648f9d72 Closes-Bug: #1896925 |
||
---|---|---|
.. | ||
_drivers | ||
_metrics | ||
hacking | ||
notify | ||
rpc | ||
tests | ||
__init__.py | ||
_utils.py | ||
conffixture.py | ||
dispatcher.py | ||
exceptions.py | ||
opts.py | ||
serializer.py | ||
server.py | ||
target.py | ||
transport.py | ||
version.py |