Bug 1316153 - Pacemaker fails to start - corosync denied errors
Pacemaker fails to start - corosync denied errors
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker (Show other bugs)
7.2
x86_64 Linux
unspecified Severity urgent
: rc
: ---
Assigned To: Ken Gaillot
cluster-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-09 09:27 EST by Benjamin Schmaus
Modified: 2016-03-09 23:02 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-03-09 13:39:09 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Benjamin Schmaus 2016-03-09 09:27:58 EST
Description of problem:  Customer with RH consulting was in the middle of upgrading OSP 7.0 to OSP 7.2.  During the upgrade process the cluster will not come up.


Version-Release number of selected component (if applicable):
RHEL 7.2
OSP 7.2


How reproducible: 100%


Steps to Reproduce:
1.
2.
3.

Actual results: Cluster does not come up


Expected results: Cluster should form


Additional info:
Comment 4 Ken Gaillot 2016-03-09 13:39:09 EST
This turned out to be a networking issue unrelated to pacemaker.

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