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 1838084 - pcs cluster stop --all throws errors and doesn't seem to honor the request-timeout option [rhel-8.2.0.z]
Summary: pcs cluster stop --all throws errors and doesn't seem to honor the request-ti...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.2
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: 8.2
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1833506
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-20 13:00 UTC by RHEL Program Management Team
Modified: 2022-04-07 09:13 UTC (History)
14 users (show)

Fixed In Version: pcs-0.10.4-6.el8_2.1
Doc Type: Bug Fix
Doc Text:
Cause: Communication between pcsd components times out if there is no response in 30 seconds. Consequence: Actions performed by pcsd taking longer than 30 seconds never succeed. Fix: Remove the timeout for internal pcsd communication. Result: Actions taking a long time work properly.
Clone Of: 1833506
Environment:
Last Closed: 2020-06-10 14:35:03 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed fix (1.18 KB, patch)
2020-05-28 08:52 UTC, Miroslav Lisik
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Github ClusterLabs/pcs/commit/765b1be9be659bd49eb0a2398906a474ed609177 0 None None None 2020-06-16 06:34:10 UTC
Red Hat Issue Tracker RHELPLAN-43957 0 None None None 2022-04-07 09:13:00 UTC
Red Hat Product Errata RHSA-2020:2462 0 None None None 2020-06-10 14:35:17 UTC

Comment 1 Miroslav Lisik 2020-05-28 08:52:45 UTC
Created attachment 1692979 [details]
proposed fix

Comment 2 Miroslav Lisik 2020-05-28 08:54:57 UTC
Test:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.4-6.el8.x86_64

[root@virt-123 ~]# pcs resource create test ocf:heartbeat:Delay startdelay=1 stopdelay=35 op stop timeout=40
[root@virt-123 ~]# pcs resource
  * test        (ocf::heartbeat:Delay): Started virt-123
[root@virt-123 ~]# time pcs cluster stop --all
virt-124: Stopping Cluster (pacemaker)...
virt-123: Stopping Cluster (pacemaker)...
virt-123: Stopping Cluster (corosync)...
virt-124: Stopping Cluster (corosync)...

real    0m39.457s
user    0m0.825s
sys     0m0.112s

Comment 3 Miroslav Lisik 2020-05-28 10:26:43 UTC
Version on virt-123 is:

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

Comment 9 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


Note You need to log in before you can comment on or make changes to this bug.