Bug 1316633 - rabbitmq resource-agents wipes too much data on recovery and kills additional users configuration
Summary: rabbitmq resource-agents wipes too much data on recovery and kills additional...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: Leonid Natapov
URL: https://github.com/lemenkov/resource-...
Whiteboard:
Depends On: 1303803
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-10 16:17 UTC by Marcel Kolaja
Modified: 2022-09-13 20:05 UTC (History)
14 users (show)

Fixed In Version: resource-agents-3.9.5-54.el7_2.8
Doc Type: Bug Fix
Doc Text:
Cause: The resource agent wipes too much data on recovery Consequence: Users are lost Fix: Backup and restore users to avoid losing them Result: Users still available after recovery
Clone Of: 1303803
Environment:
Last Closed: 2016-03-31 22:08:50 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2374351 0 None None None 2022-09-13 20:05:58 UTC
Red Hat Product Errata RHBA-2016:0556 0 normal SHIPPED_LIVE resource-agents bug fix update 2016-04-01 01:53:30 UTC

Description Marcel Kolaja 2016-03-10 16:17:02 UTC
This bug has been copied from bug #1303803 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 7 Leonid Natapov 2016-03-16 13:24:50 UTC
resource-agents-3.9.5-67.el7

rabbitmq new user survives resource restart and still exist.

Comment 12 errata-xmlrpc 2016-03-31 22:08:50 UTC
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://rhn.redhat.com/errata/RHBA-2016-0556.html


Note You need to log in before you can comment on or make changes to this bug.