Bug 1264083
Summary: | rabbitmq-server stops (instead of restart) during update | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | John Eckersberg <jeckersb> |
Component: | rabbitmq-server | Assignee: | Peter Lemenkov <plemenko> |
Status: | CLOSED ERRATA | QA Contact: | nlevinki <nlevinki> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 (Kilo) | CC: | apevec, hrosnet, jeckersb, jguiditt, lhh, mcornea, ohochman, plemenko, rbiba, rhosp-bugs-internal, sclewis, yeylon |
Target Milestone: | async | Keywords: | Triaged, ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rabbitmq-server-3.3.5-6.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, the rabbitmq-server service was stopped when the rabbitmq-server package was updated. Now, the service is conditionally restarted after an update is applied and before the traces of the previous version are removed. As a result, updating to this version does not yet restart the service because the previous package does not yet contain the necessary command; however, with future updates, the service will (conditionally) restart automatically.
|
Story Points: | --- |
Clone Of: | 1259564 | Environment: | |
Last Closed: | 2015-11-19 23:30:31 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: |
Description
John Eckersberg
2015-09-17 13:13:12 UTC
*** Bug 1264688 has been marked as a duplicate of this bug. *** Cleaning up Cc list that got pulled over when cloning Fedora bug... Taking this. *** Bug 1271664 has been marked as a duplicate of this bug. *** automation passed. No issues were found 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-2015:2496 |