Bug 1568411

Summary: [UPDATE] rabbitmq fails to start after reboot on updated nodes (osp12, rhel 7.5)
Product: Red Hat OpenStack Reporter: Raviv Bar-Tal <rbartal>
Component: rabbitmq-serverAssignee: Peter Lemenkov <plemenko>
Status: CLOSED DUPLICATE QA Contact: Udi Shkalim <ushkalim>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 12.0 (Pike)CC: apevec, jeckersb, lhh, srevivo
Target Milestone: ---Keywords: 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-04-30 13:27:35 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
docker ps
none
pcs status
none
cluster logs
none
/var/logs/pacemaker
none
/var/log/containers none

Description Raviv Bar-Tal 2018-04-17 12:50:33 UTC
Description of problem:
After minor update of RHOS-12 to new bundle with rhel 7.5

Version-Release number of selected component (if applicable):
rabbitmq-server-3.6.5-5.el7ost.noarch

How reproducible:


Steps to Reproduce:
1. Install osp12 GA 
2. Update to the latest release  (2018-04-04)
3. After update has finished - reboot overcloud nodes

Actual results:
Rabbitmq fail to start with error
Failed Actions:
* rabbitmq_start_0 on rabbitmq-bundle-2 'unknown error' (1): call=18, status=complete, exitreason='',
    last-rc-change='Tue Apr 17 10:59:58 2018', queued=0ms, exec=26095ms
* redis_promote_0 on redis-bundle-0 'unknown error' (1): call=-1, status=Timed Out, exitreason='',
    last-rc-change='Tue Apr 17 11:04:05 2018', queued=0ms, exec=0ms


Expected results:
Rabbitmq starts

Additional info:
See attached logs and sosreport

Comment 1 Peter Lemenkov 2018-04-17 12:57:57 UTC
Hello Raviv, 

(In reply to Raviv Bar-Tal from comment #0)
...
> Additional info:
> See attached logs and sosreport

Looks like you either forgot to attach them or forgot to link a corrwsponding Customer Use Case :)

Comment 2 Raviv Bar-Tal 2018-04-17 14:39:01 UTC
Created attachment 1423068 [details]
docker ps

Comment 3 Raviv Bar-Tal 2018-04-17 14:39:36 UTC
Created attachment 1423069 [details]
pcs status

Comment 4 Raviv Bar-Tal 2018-04-17 14:40:24 UTC
Created attachment 1423070 [details]
cluster logs

Comment 5 Raviv Bar-Tal 2018-04-17 14:59:52 UTC
Created attachment 1423099 [details]
/var/logs/pacemaker

Comment 6 Raviv Bar-Tal 2018-04-17 15:11:09 UTC
Created attachment 1423101 [details]
/var/log/containers

Comment 7 John Eckersberg 2018-04-30 13:27:35 UTC

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