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 running pcs as a non-rot user some commands require the user to be authenticated to the local pcsd. The authentication procedure is confusing for some users.


Version-Release number of selected component (if applicable):
pcs-0.9.162-2.el7.x86_64


How reproducible:
always, easily


Actual results:
[clouduser@node03 ~]$ pcs cluster start --all
Please authenticate yourself to the local pcsd
Username: hacluster
Password:
Port (default: 2224):


Expected results:
[clouduser@node03 ~]$ pcs cluster start --all
Please authenticate yourself to the local pcsd or run this command as root
Username: hacluster
Password:
Pcsd port (press enter for default: 2224):

Created attachment 1507577 [details]
proposed fix

Test:

1) switch to a non-root user
2) run `pcs cluster start`
3) pcs should inform you that root user is required to run the command or you should authenticate
4) run the advised command `pcs client local-auth` and authenticate the non-root user
5) run `pcs cluster start`, this time it should work

After Fix:

[kid76 ~] $ rpm -q pcs
pcs-0.9.167-1.el7.x86_64

[kid76 ~] $ su user1
[user1@kid76 root]$ pcs cluster start
Error: Unable to authenticate against the local pcsd. Run the same command as root or authenticate yourself to the local pcsd using command 'pcs client local-auth'
[user1@kid76 root]$ pcs client local-auth
Username: user1
Password:
localhost: Authorized
[user1@kid76 root]$ pcs cluster start
Starting Cluster (corosync)...
Starting Cluster (pacemaker)...

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/RHBA-2019:2244