Bug 1344228

Summary: Backport fix for the recent RabbitMQ versions
Product: Red Hat Enterprise Linux 7 Reporter: Marcel Kolaja <mkolaja>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: high Docs Contact:
Priority: high    
Version: 7.4CC: agk, cluster-maint, fdinitto, lnatapov, mjuricek, mnovacek, oalbrigt, plemenko
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: resource-agents-3.9.5-54.el7_2.15 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1342478 Environment:
Last Closed: 2016-08-02 18:23:48 UTC Type: ---
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: 1342478    
Bug Blocks:    

Description Marcel Kolaja 2016-06-09 08:34:36 UTC
This bug has been copied from bug #1342478 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 4 Peter Lemenkov 2016-06-09 10:03:04 UTC
How to test:

* Deploy a cluster of RabbitMQ using an old version (anything from 3.3.5 line - RHOS6, RHOS7, RHOS8).
* Start RabbitMQ cluster.
* Everything starts normally.

* Deploy a cluster of RabbitMQ using a new version (latest 3.6.2 build or higher - available in RHOS9 and later) and using the same resource-agents version.
* Start RabbitMQ cluster.
* Everything starts normally.

Comment 5 Leonid Natapov 2016-06-20 12:19:01 UTC
tested with resource-agents-3.9.5-54.el7_2.12.
Everything starts normally.

Comment 6 Oyvind Albrigtsen 2016-07-05 09:28:34 UTC
New build with additional return codes from: https://github.com/ClusterLabs/resource-agents/pull/833

Comment 9 Leonid Natapov 2016-07-21 11:57:06 UTC
tested with resource-agents-3.9.5-54.el7_2.15.
Everything starts normally.

Comment 11 errata-xmlrpc 2016-08-02 18:23:48 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-1535.html