Bug 1313156 – pacemaker fails to bring up VIPs and the rest of the cluster on OpenStack HA environment

Bug 1313156 - pacemaker fails to bring up VIPs and the rest of the cluster on OpenStack HA environment

Summary:	pacemaker fails to bring up VIPs and the rest of the cluster on OpenStack HA ...

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pacemaker (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	All Linux

Priority	unspecified Severity urgent
Target Milestone:	rc
Target Release:	---
Assigned To:	Ken Gaillot
QA Contact:	cluster-qe@redhat.com
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-03-01 01:28 EST by Jaison Raju
Modified:	2016-09-05 07:53 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-03-01 04:49:33 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jaison Raju 2016-03-01 01:28:18 EST

Description of problem:
In an environment using ipv6 for internal communication , on 29 day time , 
the pacemaker brought down services .
Not able to bring up the resources & pcs tends to fence other nodes .

Version-Release number of selected component (if applicable):
OSP Director 7.3
OpenStack 7.0.4
resource-agents-3.9.5-54.el7_2.6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

- OSP3 was been provision with Director
- IPV6 is being used here for internal communication 
- none of 3 node want to be part of cluster and start failing eventually
- manually few resources started but failed again. 
- All the nodes rebooted and same scenario
- tried to put standby two nodes (slnec1ctl0 slnec1ctl1) and try to start one node(slnec1ctl2), even not working

Comment 3 Fabio Massimo Di Nitto 2016-03-01 01:43:31 EST

Please add also sosreports from the undercloud as we might be hitting this bug https://bugzilla.redhat.com/show_bug.cgi?id=1245298 that causes the nodes to be rebooted/fenced in a loop similar to what you describe.

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