@Roman This massage about the lost queue you can see each time when you rebooted RabbitMQ cluster during the rpc call.
If client have started an rpc-call and awating the anwer
In the case if queue disappeared during rpc-call, client will wait reply until timeout and
if server replies in this period then server recreates reply queue
So the message "queue not found" is not an error
reply queue will be recreated by client at the moment of new rpc-call start
So, the real issue in this case is the lost reply-message or server not replied at all
To avoid continous service interruption Nova should handle Timeout exception raised by oslo.messaging and we should investigate why reply message may be lost
@Roman This massage about the lost queue you can see each time when you rebooted RabbitMQ cluster during the rpc call.
If client have started an rpc-call and awating the anwer
In the case if queue disappeared during rpc-call, client will wait reply until timeout and
if server replies in this period then server recreates reply queue
So the message "queue not found" is not an error
reply queue will be recreated by client at the moment of new rpc-call start
So, the real issue in this case is the lost reply-message or server not replied at all
To avoid continous service interruption Nova should handle Timeout exception raised by oslo.messaging and we should investigate why reply message may be lost