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.

Here are my current properties:
# pcs property
Cluster Properties:
 bar: bandini
 cluster-infrastructure: corosync
 cluster-name: cluster_name
 dc-version: 1.1.13-10.el7-44eb2dd
 have-watchdog: false
 stonith-enabled: false
Node Attributes:
 centos: foo=bar


I was surprised that when showing a non existing property:
# pcs property show baz
Cluster Properties:
Node Attributes:
 centos: foo=bar

I think it should show only the node properties that match the property asked
on the command line. (aka none in this case). Related to BZ#1301993

Node properties should be moved to "pcs node" command.

Created attachment 1182767 [details]
proposed fix

Setup:
[vm-rhel72-1 ~] $ pcs node standby vm-rhel72-3
[vm-rhel72-1 ~] $ pcs property
Cluster Properties:
 cluster-infrastructure: corosync
 cluster-name: devcluster
 dc-version: 1.1.15-7.el7-e174ec8
 have-watchdog: false
Node Attributes:
 vm-rhel72-3: standby=on

Before Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-4.el7.x86_64
[vm-rhel72-1 ~] $ pcs property show baz
Cluster Properties:
Node Attributes:
 vm-rhel72-3: standby=on

After Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-5.el7.x86_64
[vm-rhel72-1 ~] $ pcs property show baz
Cluster Properties:

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-2016-2596.html