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.

Bug 1832914

Summary: pcs status on remotes is not working on rhel8.2 any longer [rhel-8.2.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: high    
Version: 8.2CC: cfeist, cluster-maint, idevat, mjuricek, mlisik, mpospisi, nhostako, omular, tojeline
Target Milestone: rcKeywords: Regression, ZStream
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.10.4-6.el8_2.1 Doc Type: Bug Fix
Doc Text:
Cause: User runs 'pcs status' on a remote node. Consequence: Pcs exits with an error complaining corosync.conf is missing. This is wrong as corosync.conf is expected to be missing on remote nodes. Fix: If corosync.conf is missing, read cluster name from CIB instead of corosync.conf. Gracefully skip obtaining and displaying information which depend on corosync.conf presence. Result: The 'pcs status' command works on remote nodes.
 Story Points: ---
Clone Of: 1830552 Environment:
Last Closed: 2020-06-10 14:35:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1830552    
Bug Blocks:    
Attachments:
Description Flags
proposed fix + tests none

Comment 1 Miroslav Lisik 2020-05-28 08:58:13 UTC 
Created attachment 1692983 [details]
proposed fix + tests
Comment 2 Miroslav Lisik 2020-05-28 10:23:16 UTC 
Test:

[root@virt-123 ~]# rpm -q pcs
pcs-0.10.4-6.el8_2.1.x86_64

Install pacemaker-remote package on the remote node.

[root@virt-138 ~]# dnf install -y -q pacemaker-remote
[root@virt-138 ~]# systemctl start pcsd
[root@virt-138 ~]# rpm -q pcs
pcs-0.10.4-6.el8_2.1.x86_64

Add remote node to the cluster:

[root@virt-123 ~]# pcs status nodes
Pacemaker Nodes:
 Online: virt-123 virt-124
 Standby:
 Standby with resource(s) running:
 Maintenance:
 Offline:
Pacemaker Remote Nodes:
 Online:
 Standby:
 Standby with resource(s) running:
 Maintenance:
 Offline:

[root@virt-123 ~]# pcs host auth -u hacluster virt-138
Password: 
virt-138: Authorized

[root@virt-123 ~]# pcs cluster node add-remote virt-138
No addresses specified for host 'virt-138', using 'virt-138'
Sending 'pacemaker authkey' to 'virt-138'
virt-138: successful distribution of the file 'pacemaker authkey'
Requesting 'pacemaker_remote enable', 'pacemaker_remote start' on 'virt-138'
virt-138: successful run of 'pacemaker_remote enable'
virt-138: successful run of 'pacemaker_remote start'
[root@virt-123 ~]# pcs status nodes
Pacemaker Nodes:
 Online: virt-123 virt-124
 Standby:
 Standby with resource(s) running:
 Maintenance:
 Offline:
Pacemaker Remote Nodes:
 Online: virt-138
 Standby:
 Standby with resource(s) running:
 Maintenance:
 Offline:

Run 'pcs status' on the remote node:

[root@virt-138 ~]# pcs status
Cluster name: STSRHTS1758
Cluster Summary:
  * Stack: corosync
  * Current DC: virt-123 (version 2.0.3-5.el8_2.1-4b1f869f0f) - partition with quorum
  * Last updated: Thu May 28 12:13:57 2020
  * Last change:  Thu May 28 12:12:57 2020 by root via cibadmin on virt-123
  * 3 nodes configured
  * 3 resource instances configured

Node List:
  * Online: [ virt-123 virt-124 ]
  * RemoteOnline: [ virt-138 ]

Full List of Resources:
  * fence-virt-123      (stonith:fence_xvm):    Started virt-124
  * fence-virt-124      (stonith:fence_xvm):    Started virt-124
  * virt-138    (ocf::pacemaker:remote):        Started virt-123

Daemon Status:
  corosync: inactive/disabled
  pacemaker: inactive/disabled
  pacemaker_remote: active/enabled
  pcsd: active/enabled
Comment 7 errata-xmlrpc 2020-06-10 14:35:03 UTC 
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/RHSA-2020:2462