Bug 1315842
Summary: | oslo.messaging holds connections when replies fail | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | John Eckersberg <jeckersb> |
Component: | python-oslo-messaging | Assignee: | John Eckersberg <jeckersb> |
Status: | CLOSED ERRATA | QA Contact: | Udi Shkalim <ushkalim> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 (Kilo) | CC: | adahms, apevec, chenders, chricker, christer.eriksson, dmaley, editucci, fahmed, fpercoco, hguemar, jbiao, jdonohue, jeckersb, jmelvin, lhh, mabaakou, mburns, nlevinki, oblaut, ochalups, pcaruana, plemenko, srevivo, ushkalim, zbitter |
Target Milestone: | async | Keywords: | Triaged, ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | hot | ||
Fixed In Version: | python-oslo-messaging-1.8.3-5.el7ost | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1276166 | Environment: | |
Last Closed: | 2016-06-14 14:14:32 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1276166 | ||
Bug Blocks: | 1191185, 1282918, 1301634 |
Comment 1
John Eckersberg
2016-03-08 18:31:04 UTC
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 |