RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.2
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 06:28 UTC by Jaison Raju
Modified: 2019-10-10 11:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-01 09:49:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaison Raju 2016-03-01 06:28:18 UTC
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 06:43:31 UTC
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.