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:
pcs status as non root user gives feedback cluster is not running, even if this is not true.
Version-Release number of selected component (if applicable):
7.6
How reproducible:
login as non root and type pcs status
sudo pcs status gives proper feedback, that cluster is running
Steps to Reproduce:
1.login as root
2.pcs status # Cluster is running
3.login as non root and type pcs status
Error: cluster is not currently running on this node
Actual results:
pcs status
Error: cluster is not currently running on this node
Expected results:
You are not authorized to use this command, please login as different user
Additional info:
Reassigning to pcs because the message appears to be coming from there.
FYI, in RHEL 7.7, in this situation crm_mon would print:
Error: cluster is not available on this node
The problem is pcs does not know why it cannot get cluster status because pacemaker does not know either: see bz1486869.
I just checked that with pacemaker-1.1.20-5.el7: crm_mon returns 107 and prints "Error: cluster is not available on this node" in both cases when cluster is stopped and a non-root user is trying to access a running cluster.
So what we can do is this:
1) Print an error coming from crm_mon instead of pcs' own. This way pcs would stop giving misleading info.
2) If a non-root user runs pcs and pcs gets an error from crm_mon, add a message like "you may not have permissions to manage the cluster" to the error coming from crm_mon. Or it can be added every time.
We can also check if pacemaker is running with 'systemctl is-active pacemaker.service'. We need to check it works for non-root users in all cases, though.
Hello,
please check the user and give as feedback for non root users:
"Please run as user root"
The issue still exists whith RHEL 8
I would not try to get it fixed, running it as non root user
Thanks Markus