Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1324546

Summary: Corosync fails to start on one of the controllers in an upgraded 7.3->8 IPv6 environment
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: rhosp-directorAssignee: Angus Thomas <athomas>
Status: CLOSED DUPLICATE QA Contact: Arik Chernetsky <achernet>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: aschultz, dbecker, fdinitto, mburns, michele, morazi, rhel-osp-director-maint, vcojot
Target Milestone: ---   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Cause: Corosync sometimes fails to start correctly in IPv6 environments Consequence: Corosync can fail to start on reboot of controller nodes Workaround (if any): On reboot of the controller nodes, when the host comes back up, check for corosync status. If it failed, start the following services manually and in the following order: corosync, pacemaker, pcsd Result: The corosync service and related cluster services should come up correctly when restarted.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-22 12:08:33 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:
Bug Depends On: 1245951    
Bug Blocks:    
Attachments:
Description Flags
corosync fail none

Description Marius Cornea 2016-04-06 15:17:40 UTC 
Created attachment 1144242 [details]
corosync fail

Description of problem:
After reboot corosync fails to start on one of the controllers in an upgraded 7.3->8 IPv6 environment.

Steps to Reproduce:
1. Upgrade overcloud from 7.3->8
2. Once the upgrade is complete reboot the controllers serially

Actual results:
Corosync failed to start when rebooting the last controller.

Expected results:
All the controllers get back online after reboot. 

Additional info:
The issue I am seeing looks pretty similar to the one describe by BZ#1245951

I am attaching the corosync log on the failed controller.
Comment 6 Mike Burns 2016-04-07 21:36:02 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 7 Mike Burns 2016-04-13 14:50:09 UTC 
Moving back to 8.  This isn't targeted for a specific milestone because we're dependent on a RHEL bug fix, but once it's fixed, this will become testonly.
Comment 10 Fabio Massimo Di Nitto 2017-02-22 12:08:33 UTC 

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