Bug 1011618 – Slave roles inconsistent in pcs status xml (or crm_mon)

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1011618 - Slave roles inconsistent in pcs status xml (or crm_mon)

Summary:	Slave roles inconsistent in pcs status xml (or crm_mon)

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	pacemaker (Show other bugs)
Sub Component:
Version:	6.5
Hardware:	Unspecified Unspecified

Priority	high Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Andrew Beekhof
QA Contact:	Cluster QE
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-09-24 12:15 EDT by Jaroslav Kortus
Modified:	2013-11-21 07:10 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:	pacemaker-1.1.10-12.el6
Doc Type:	Bug Fix
Doc Text:	No description necessary
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-11-21 07:10:20 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.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2013:1635	normal	SHIPPED_LIVE	Low: pacemaker security, bug fix, and enhancement update	2013-11-20 16:53:44 EST

Groups: None (edit)

Description Jaroslav Kortus 2013-09-24 12:15:16 EDT

Description of problem:
When Master/Slave set is started, it's underlying resources have the following roles:
Master: role="Master"
Slaves: role="Started"

When pcs resource move --master <resource> is used (which is effectively ban of master on current node), the new set looks like this:
New Master: role="Master"
Old Master: role="Slave"
Old Slave: role="Started"

Please remove this inconsistency and set them to either "Slave" or "Started" at all times.

Version-Release number of selected component (if applicable):
pacemaker-1.1.10-9.el6.x86_64


How reproducible:


Steps to Reproduce:
1.# pcs resource create dummy ocf:pacemaker:Stateful
2.# pcs resource master dummy
3.# pcs resource move dummy-master


Actual results:
Inconsistent roles in pcs status xml for slave nodes

Expected results:
Consistent roles in pcs status xml for all slave nodes

Additional info:

Comment 1 Jaroslav Kortus 2013-09-24 12:17:12 EDT

Tested with pcs-0.9.85-1.el6.noarch, but same results are achievable by

crm_resource --resource dummy-master --move --master
and
crm_mon  -1 -r -X

Comment 4 Andrew Beekhof 2013-09-24 21:54:41 EDT

A related patch has been committed upstream:
  https://github.com/beekhof/pacemaker/commit/bc5e0b6

with subject:

   Fix: Bug rhbz#1011618 - Consistently use 'Slave' as the role for unpromoted master/slave resources

Further details (if any):

Comment 7 Jaroslav Kortus 2013-10-02 10:53:52 EDT

Fixed in pacemaker-1.1.10-12.el6.x86_64, marking as verified.

Comment 8 errata-xmlrpc 2013-11-21 07:10:20 EST

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.

http://rhn.redhat.com/errata/RHSA-2013-1635.html

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