Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

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:

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

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):

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

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