https://code.engineering.redhat.com/gerrit/#/c/69408/
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
*** Bug 1329742 has been marked as a duplicate of this bug. ***
python-oslo-messaging-1.8.3-4.el7ost.noarch is installed on the latest ospd-7 deployment. Could it be that the package did not get in to latest ospd7 ?
It would be assumed that people do an update post install to get newer packages than our latest images. A new deployment would *not* have the package, but once the admin updates, it would get it.
Verified on: python-oslo-messaging-1.8.3-5.el7ost.noarch Steps done to recreate the problem: 1. Launched an instance with nova boot command - nova boot --image cirros-pop-osp --flavor m1.tiny --nic net-id=f05674ff-a734-4c08-8d6d-2318421b35c6 cirros 2. Restarted heat and rabbitmq - systemctl restart *heat* ; systemctl restart *rabbitmq* Rabbit logs on the controllers are not showing any repeated errors. Was able to launch a new instance after the restart.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1227