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 1172539 - Node ends up in a reboot loop when a resource with the same name exists
Summary: Node ends up in a reboot loop when a resource with the same name exists
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Andrew Beekhof
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-10 10:30 UTC by Radek Steiger
Modified: 2015-11-19 12:12 UTC (History)
3 users (show)

Fixed In Version: pacemaker-1.1.13-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 12:12:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
cib with dummy resource (8.44 KB, text/plain)
2014-12-10 10:30 UTC, Radek Steiger 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2383 0 normal SHIPPED_LIVE Moderate: pacemaker security, bug fix, and enhancement update 2015-11-19 10:49:49 UTC

Description Radek Steiger 2014-12-10 10:30:24 UTC 
Created attachment 966730 [details]
cib with dummy resource

> Description of problem:

When I create a resource which name is identical to a name of one of the cluster nodes, that node will end up in a reboot or fencing loop.

I can imagine it being a common situation where the admin wants to run for example Apache and calls both the cluster node and the resource 'apache'.


> Version-Release number of selected component (if applicable):
pacemaker-1.1.12-13.el7.x86_64
corosync-2.3.4-3.el7.x86_64
pcs-0.9.137-3.el7.x86_64

> How reproducible:
Always

> Steps to Reproduce:
1. get a cluster running
2. configure fencing
3. choose random node and create a dummy resource with the same name

> Actual results:
The chosen node ends up in reboot/fencing loop.

> Expected results:
No reboots.

> Additional info:
All necessary info should be contained in the attached cib.xml and te crm report.
Comment 3 Andrew Beekhof 2014-12-17 03:34:15 UTC 
Yikes!  Ok, I'll look at this when I get back from the xmas break.
Comment 4 Andrew Beekhof 2015-01-23 00:52:30 UTC 
Ran out of time for this, bumping to 7.2 since there is a viable work-around (dont do that! :-)
Comment 6 Andrew Beekhof 2015-03-31 01:27:55 UTC 
David, I'd prefer you dug into this since it is tying in with the remote node functionality and I don't want to screw anything up :-)


[12:18 PM] beekhof@fedora ~/Development/sources/pacemaker/devel ☺ # tools/crm_simulate -Sx ~/Downloads/pe-error-1.bz2 -VVV

Current cluster status:
Online: [ virt-041 virt-042 virt-043 virt-044 ]

 Fencing	(stonith:fence_xvm):	Started virt-041 
 virt-044	(ocf::heartbeat:Dummy):	Started [ virt-042 virt-044 ]

  notice: check_rsc_parameters: 	Forcing restart of virt-044 on virt-044, type changed: remote -> Dummy
  notice: check_rsc_parameters: 	Forcing restart of virt-044 on virt-044, provider changed: pacemaker -> heartbeat

[...]
Comment 8 David Vossel 2015-06-05 19:34:15 UTC 
patch posted
https://github.com/ClusterLabs/pacemaker/pull/726

This was pretty interesting to track down.

Unit test.

1. create a resource with the exact same name as a pacemaker node.
2. verify no unexpected fencing actions occur after the resource is created.

if the resource successfully starts somewhere without fencing and a bunch of errors/warnings showing up in the logs, then it works.
Comment 12 errata-xmlrpc 2015-11-19 12:12:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2383.html
Note You need to log in before you can comment on or make changes to this bug.