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 a non-root user runs pcs and uses --options in the command, the options are ignored by pcs


Version-Release number of selected component (if applicable):
pcs-0.10.2-2.el8


How reproducible:
always, easily


Steps to Reproduce:
1. switch to a non-root user
2. pcs cluster start --all


Actual results:
Cluster is started on the local node only:
$ pcs cluster start --all
Starting Cluster...


Expected results:
Cluster is started on all cluster nodes:
$ pcs cluster start --all
rh80-node1: Starting Cluster...
rh80-node2: Starting Cluster...


Additional info:
This was working fine in pcs-0.10.1

Created attachment 1586667 [details]
proposed fix

Test is in comment 0.

After Fix

[ant8 ~] $ rpm -q pcs
pcs-0.10.2-3.el8.x86_64
[ant8 ~] $ su user1
[user1@ant8 root]$ pcs status
Error: cluster is not currently running on this node
[user1@ant8 root]$ pcs cluster start --all
bee8: Starting Cluster...
ant8: Starting Cluster...

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://access.redhat.com/errata/RHEA-2019:3311