98c30ac431
While attempting to reproduce a rabbitmq related failure on an AIO-DX system, I somehow caused a situation where the rabbitmq pods were running, but were missing some of the nova queues - specifically, the notifications.info queue was missing. When the VIM initialized, it attempted to attach a consumer to this non existent queue, resulting in an exception, which prevents the VIM from coming up, which causes SM to decide the host was unhealthy, which resulted in a swact to the other controller. The same problem happened there, which caused an endless series of swacts. The VIM already has code to check whether the nova exchange has been created in the rabbitmq pod, but it did not catch the case where the exchange was there, but some of the queues were missing. This fix updates the VIM to detect this situation and avoid attempting to create its consumer until the queue has been created. Change-Id: Ib5446bd15823cb0e7204ad8d0ff4f37270044c4b Closes-Bug: 1816766 Signed-off-by: Bart Wensley <barton.wensley@windriver.com> |
||
---|---|---|
.. | ||
centos | ||
nfv-client | ||
nfv-common | ||
nfv-debug-tools/histogram_analysis | ||
nfv-plugins | ||
nfv-tests | ||
nfv-tools | ||
nfv-vim | ||
.coveragerc | ||
.gitignore | ||
.stestr.conf | ||
PKG-INFO | ||
pylint.rc | ||
test-requirements.txt | ||
tox.ini |