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.
Cause:
User is not logged in as root.
Consequence:
User is not able to create, start, stop, enable, disable, destroy a cluster, add and remove nodes using pcs commands.
Fix:
Redirect these commands to local pcsd, ask for login and password if the user is not authenticated yet.
Result:
User is able to run previously mentioned commands even if he/she is not root.
Assuming the user is authenticated, it probably makes sense to send the 'pcs cluster start' command to pcsd if the user is not root (and is authenticated).
Created attachment 1029855[details]
proposed fix
Test:
A non-root user is able to create, start, stop, enable, disable, destroy a cluster, add and remove nodes using pcs commands. If the user is not authenticated to the local pcsd he/she will be prompted for login and password automatically.
Before fix:
[user1@rh71-node1 ~]$ pcs cluster stop
Stopping Cluster (pacemaker)... Redirecting to /bin/systemctl stop pacemaker.service
Failed to issue method call: Access denied
Error: unable to stop pacemaker
[user1@rh71-node1 ~]$ echo $?
1
After fix:
[user1@rh71-node1 ~]$ pcs cluster stop
Please authenticate yourself to the local pcsd
Username: user1
Password:
localhost: Authorized
Stopping Cluster (pacemaker)... Stopping Cluster (corosync)...
[user1@rh71-node1 ~]$ pcs status nodes
Error: error running crm_mon, is pacemaker running?
[user1@rh71-node1 ~]$ pcs cluster start
Starting Cluster...
[user1@rh71-node1 ~]$ pcs status nodes
Pacemaker Nodes:
Online: rh71-node1 rh71-node2
Standby:
Offline:
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-2015-2290.html