Bug 1619818
| Summary: | RFE: have pcs ask if pcsd is actually running when it gets a "Failed connect to" error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Corey Marthaler <cmarthal> | ||||
| Component: | pcs | Assignee: | Tomas Jelinek <tojeline> | ||||
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
| Severity: | low | Docs Contact: | Steven J. Levine <slevine> | ||||
| Priority: | low | ||||||
| Version: | 8.0 | CC: | cfeist, cluster-maint, idevat, mlisik, mmazoure, mpospisi, nhostako, omular, slevine, tojeline | ||||
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | 8.4 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | pcs-0.10.8-1.el8 | Doc Type: | No Doc Update | ||||
| Doc Text: |
This is just a change of an error message printed by pcs, no doc update is needed.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-05-18 15:12:05 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Corey Marthaler
2018-08-21 19:56:25 UTC
Created attachment 1746272 [details]
proposed fix
Test:
[root@rh83-node1:~]# systemctl stop pcsd
[root@rh83-node1:~]# pcs cluster enable --all
rh83-node2: Cluster Enabled
rh83-node3: Cluster Enabled
Error: unable to enable all nodes
Unable to connect to rh83-node1, check if pcsd is running there or try setting higher timeout with --request-timeout option (Failed to connect to rh83-node1 port 2224: Connection refused)
Test: [root@r8-node-01 ~]# rpm -q pcs pcs-0.10.8-1.el8.x86_64 [root@r8-node-01 ~]# systemctl stop pcsd [root@r8-node-01 ~]# pcs cluster enable --all r8-node-02: Cluster Enabled Error: unable to enable all nodes Unable to connect to r8-node-01, check if pcsd is running there or try setting higher timeout with --request-timeout option (Failed to connect to r8-node-01 port 2224: Connection refused) BEFORE:
=======
[root@virt-031 ~]# rpm -q pcs
pcs-0.10.7-3.el8.x86_64
## Enabling cluster with stopped pcsd
[root@virt-031 ~]# pcs host auth virt-03{1,2} -u hacluster -p password
virt-032: Authorized
virt-031: Authorized
[root@virt-031 ~]# pcs cluster setup test virt-03{1,2}
{...}
[root@virt-031 ~]# systemctl stop pcsd
[root@virt-031 ~]# pcs cluster enable --all
virt-032: Cluster Enabled
Error: unable to enable all nodes
Unable to connect to virt-031, try setting higher timeout in --request-timeout option (Failed to connect to virt-031 port 2224: Connection refused)
> Enable shows error for the first node without a hint about stopped pcsd
## Starting cluster with stopped pcsd
[root@virt-031 ~]# pcs cluster start --all
virt-031: Unable to connect to virt-031, try setting higher timeout in --request-timeout option (Failed to connect to virt-031 port 2224: Connection refused)
virt-032: Starting Cluster...
Error: unable to start all nodes
virt-031: Unable to connect to virt-031, try setting higher timeout in --request-timeout option (Failed to connect to virt-031 port 2224: Connection refused)
> Start shows error for the first node without a hint about stopped pcsd
## Starting and enabling cluster with running pcsd
[root@virt-031 ~]# systemctl start pcsd
[root@virt-031 ~]# pcs cluster start --all
virt-032: Starting Cluster...
virt-031: Starting Cluster...
[root@virt-031 ~]# pcs cluster enable --all
virt-031: Cluster Enabled
virt-032: Cluster Enabled
> OK: No problem with running pcsd
AFTER:
======
[root@virt-058 ~]# rpm -q pcs
pcs-0.10.8-1.el8.x86_64
## Enabling cluster with stopped pcsd
[root@virt-058 ~]# pcs host auth virt-05{8,9} -u hacluster -p password
virt-059: Authorized
virt-058: Authorized
[root@virt-058 ~]# pcs cluster setup test virt-05{8,9}
{...}
[root@virt-058 ~]# systemctl stop pcsd
[root@virt-058 ~]# pcs cluster enable --all
virt-059: Cluster Enabled
Error: unable to enable all nodes
Unable to connect to virt-058, check if pcsd is running there or try setting higher timeout with --request-timeout option (Failed to connect to virt-058 port 2224: Connection refused)
> OK: Enable shows improved error message for the first node with a hint about stopped pcsd - 'check if pcsd is running there'
## Starting cluster with stopped pcsd
[root@virt-058 ~]# pcs cluster start --all
virt-058: Unable to connect to virt-058, check if pcsd is running there or try setting higher timeout with --request-timeout option (Failed to connect to virt-058 port 2224: Connection refused)
virt-059: Starting Cluster...
Error: unable to start all nodes
virt-058: Unable to connect to virt-058, check if pcsd is running there or try setting higher timeout with --request-timeout option (Failed to connect to virt-058 port 2224: Connection refused)
> OK: Start shows improved error message for the first node with a hint about stopped pcsd - 'check if pcsd is running there'
## Starting and enabling cluster with running pcsd
[root@virt-058 ~]# systemctl start pcsd
[root@virt-058 ~]# pcs cluster start --all
virt-059: Starting Cluster...
virt-058: Starting Cluster...
[root@virt-058 ~]# pcs cluster enable --all
virt-058: Cluster Enabled
virt-059: Cluster Enabled
> OK: No problem with running pcsd
Marking as VERIFIED for pcs-0.10.8-1.el8
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 (pcs bug fix and enhancement update), 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/RHEA-2021:1737 |