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:
According to the help of crm_master it is possible to specify the cluster node to use:
-N, --node=value Set an attribute for the named node (instead of the current one).
However this option is ignored since the Nodename is hardcoded in the commandline when "crm_attribute is called:
# cat /usr/sbin/crm_master
...
crm_attribute -N `crm_node -n` -n master-$OCF_RESOURCE_INSTANCE $options
Version-Release number of selected component (if applicable):
pacemaker-1.1.10-14.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Try to query value of master score on other node:
node1# crm_master -N node2 -l reboot -r prm_RH2_SCS -G
Actual results:
Always returns value from current node:
node1# crm_master -l reboot -r prm_RH2_SCS -G
scope=status name=master-prm_RH2_SCS value=100
node1# crm_master -N node2 -l reboot -r prm_RH2_SCS -G
scope=status name=master-prm_RH2_SCS value=100
Expected results:
Should return info for other node. Or if this doesn't make sense the info about the "-N" option should be removed from the help text and the man-page of crm_master.
Additional info:
Comment 2RHEL Program Management
2013-10-20 10:44:41 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
A related patch has been committed upstream:
https://github.com/beekhof/pacemaker/commit/dc2d0e6
with subject:
Fix: crm_master: Avoid sending redundant "--node" options to crm_attribute
Further details (if any):
(In reply to Andrew Beekhof from comment #4)
> What is the context of this report?
> crm_master shouldn't really be used outside of a resource agent (which
> doesn't have a reason to use -N).
When I was playing around with the "showscores.sh" script I thought I could use the query option (-G) of crm_master to get better information about where pacemaker decided to place a master and a slave resource, and noticed that even though "crm_master advertises the option to specify a node this option isn't actually used because the nodename is hardcoded later in the script.
If necessary we can backport dc2d0e6, but since crm_master is just a wrapper for crm_attribute, it doesn't seem critical.
Comment 7Fabio Massimo Di Nitto
2014-01-13 05:17:42 UTC
(In reply to Andrew Beekhof from comment #6)
> If necessary we can backport dc2d0e6, but since crm_master is just a wrapper
> for crm_attribute, it doesn't seem critical.
And all of those crm_foobar command should be masked behind pcs calls. We are not going to support direct calls to crm_* (except crm_report perhaps). Let's make sure that pcs will grow the ability to handle it.
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/RHBA-2014-1544.html