Bug 1552043

Summary: [UPDATE] rabbitmq fails to start after reboot on updated nodes IPv6
Product: Red Hat OpenStack Reporter: Raviv Bar-Tal <rbartal>
Component: puppet-rabbitmqAssignee: John Eckersberg <jeckersb>
Status: CLOSED DUPLICATE QA Contact: Raviv Bar-Tal <rbartal>
Severity: high Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: fdinitto, jeckersb, jjoyce, jschluet, slinaber, tvignaud
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-19 15:04:22 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:
Attachments:
Description Flags
sos report - contrroler
none
pcs status none

Description Raviv Bar-Tal 2018-03-06 11:59:43 UTC 
Description of problem:
rabbitmq fails to start after reboot on updated nodes

Version-Release number of selected component (if applicable):
pcs-0.9.158-6.el7_4.1.x86_64
rabbitmq-server-3.6.3-6.el7ost.noarch


How reproducible:


Steps to Reproduce:
1. Install ops 9 overcloud
2. Update cloud to 'latest' (currently 2018-02-23.1)
3. Reboot  controllers

Actual results:
rabbitmq fail to start and get disabled 

Expected results:
rabbitmq start normally 

Additional info:
Comment 1 Raviv Bar-Tal 2018-03-06 12:07:16 UTC 
Created attachment 1404773 [details]
sos report - contrroler
Comment 2 Raviv Bar-Tal 2018-03-06 12:07:51 UTC 
Created attachment 1404774 [details]
pcs status
Comment 3 John Eckersberg 2018-03-16 14:49:48 UTC 
This is likely because older OSP is missing https://github.com/voxpupuli/puppet-rabbitmq/pull/552.  To work around this while I attempt to get everything backported:

- Add to /etc/rabbitmq/rabbitmq-env.conf:

export ERL_INETRC=/etc/rabbitmq/inetrc

- Create /etc/rabbitmq/inetrc with content:

{inet6, true}.

- Make sure you have erlang >= erlang-18.3.4.5-3.el7ost (latest in OSP 9-12 is erlang-18.3.4.7-1.el7ost)
Comment 4 John Eckersberg 2018-03-19 15:04:22 UTC 

*** This bug has been marked as a duplicate of bug 1557519 ***