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:
If pcs connects to a remote node, but it hangs or doesn't respond, then 'pcs status' will hang. We should probably have some sane timeouts (and error messages) if this happens.
This was original discovered with an MTU mismatch, so the opening TCP connection to pcs succeeded, but no other packets could get through.
So when running 'pcs status' the status just hung where pcsd was being queried.
upstream patches:
https://github.com/ClusterLabs/pcs/commit/076b8b6ea473835810596f967bef41d7cf1fhttps://github.com/ClusterLabs/pcs/commit/731127b8cfffd29c8546bd4a8a461f7aade5
New parameter --request-timeout has been added to pcs.
TEST:
2 node cluster: rhel7-node1 rhel7-node2
Block port 2224 (pcsd) on rhel7-node2
[root@rhel7-node2 ~]# iptables -I OUTPUT -p tcp --dport 2224 -j DROP
[root@rhel7-node2 ~]# iptables -I INPUT -p tcp --dport 2224 -j DROP
Then try to run some commands on rhel7-node1 (they should timed out instead of hang):
[root@rhel7-node1 ~]# pcs cluster auth rhel7-node2 -uhacluster --request-timeout=3
Password:
Error: Operation timed out
Error: Unable to communicate with rhel7-node2
[root@rhel7-node1 ~]# pcs stonith sbd status --request-timeout=3
Warning: rhel7-node2: Connection timeout (Connection timed out after 3001 milliseconds)
Warning: Unable to get status of SBD from node 'rhel7-node2'
SBD STATUS
<node name>: <installed> | <enabled> | <running>
rhel7-node1: NO | NO | NO
rhel7-node2: N/A | N/A | N/A
After Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.156-1.el7.x86_64
[vm-rhel72-1 ~] $ pcs stonith sbd status --request-timeout=3
Warning: vm-rhel72-3: Connection timeout (Connection timed out after 3001 milliseconds)
Warning: Unable to get status of SBD from node 'vm-rhel72-3'
SBD STATUS
<node name>: <installed> | <enabled> | <running>
vm-rhel72-1: YES | NO | NO
vm-rhel72-3: N/A | N/A | N/A
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-2017:1958