Bug 1069799

Summary:	Under certain circumstances pacemaker can create node entries for unknown nodes
Product:	Red Hat Enterprise Linux 7	Reporter:	Frank Danapfel <fdanapfe>
Component:	pacemaker	Assignee:	Andrew Beekhof <abeekhof>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	cluster-maint, dvossel, fdanapfe, fdinitto, jkortus, lmiccini, mnovacek
Target Milestone:	rc
Target Release:	7.0
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	pacemaker-1.1.12-4.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1069795	Environment:
Last Closed:	2015-03-05 09:59:51 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:

Description Frank Danapfel 2014-02-25 16:48:54 UTC

+++ This bug was initially created as a clone of Bug #1069795 +++

Description of problem:
Under certain circumstances it can happen that pacemaker creates node entries for unknown nodes. So far this has been observed in the following cases (see comments in the upstream pull request for more information):

- using "stonith_admin -C" to manually confirm a fencing operation
- "crmadmin -S/--status"
- "crmadmin -K/--kill"

Version-Release number of selected component (if applicable):
pacemaker-1.1.10-24.el7

How reproducible:
sometimes

Steps to Reproduce:
1. run one of the commands above
2.
3.

Actual results:
sometimes node entries for unknown nodes are created

Expected results:
no node entries for unknown nodes should be created

Additional info:
The fixes for this issue are provided by the following upstream pull request:
https://github.com/ClusterLabs/pacemaker/pull/427

Comment 8 michal novacek 2014-12-02 11:37:19 UTC

I have verified that the pach is present, looks sane and that the source would compile with it.

Comment 10 errata-xmlrpc 2015-03-05 09:59:51 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/RHBA-2015-0440.html