Bug 1448569
| Summary: | Tell user there's nothing configured if they try to start a nonexistent cluster | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Corey Marthaler <cmarthal> | |
| Component: | pcs | Assignee: | Ondrej Mular <omular> | |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | |
| Severity: | low | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 7.4 | CC: | cfeist, cluster-maint, idevat, mmazoure, omular, tojeline | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | pcs-0.9.169-1.el7 | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1743731 (view as bug list) | Environment: | ||
| Last Closed: | 2020-09-29 20:10:26 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: | ||||
Upstream fix: https://github.com/ClusterLabs/pcs/commit/f318267d96cbfc3d834f93405e56bf2b403db4ff Test: [root@rhel7-node1 pcs]# pcs cluster start Error: cluster is not currently configured on this node [root@rhel7-node1 pcs]# echo $? 1 After Fix [kid76 ~] $ pcs cluster start Error: cluster is not currently configured on this node [kid76 ~] $ echo $? 1 BEFORE:
=======
[root@virt-202 ~]# rpm -q pcs
pcs-0.9.168-4.el7.x86_64
[root@virt-202 ~]# pcs cluster corosync
Error: Unable to read /etc/corosync/corosync.conf: No such file or directory
[root@virt-202 ~]# pcs cluster start
Starting Cluster (corosync)...
Job for corosync.service failed because the control process exited with error code. See "systemctl status corosync.service" and "journalctl -xe" for details.
Error: unable to start corosync
[root@virt-202 ~]# echo $?
1
[root@virt-202 ~]# systemctl status corosync.service
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/usr/lib/systemd/system/corosync.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-04-14 15:36:15 CEST; 35s ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Process: 27799 ExecStart=/usr/share/corosync/corosync start (code=exited, status=1/FAILURE)
Apr 14 15:36:15 virt-202.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Starting Corosync Cluster Engine...
Apr 14 15:36:15 virt-202.cluster-qe.lab.eng.brq.redhat.com corosync[27806]: Can't read file /etc/corosync/corosync.conf reason = (No such file or directory)
Apr 14 15:36:15 virt-202.cluster-qe.lab.eng.brq.redhat.com corosync[27799]: Starting Corosync Cluster Engine (corosync): [FAILED]
Apr 14 15:36:15 virt-202.cluster-qe.lab.eng.brq.redhat.com systemd[1]: corosync.service: control process exited, code=exited status=1
Apr 14 15:36:15 virt-202.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Failed to start Corosync Cluster Engine.
Apr 14 15:36:15 virt-202.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Unit corosync.service entered failed state.
Apr 14 15:36:15 virt-202.cluster-qe.lab.eng.brq.redhat.com systemd[1]: corosync.service failed.
AFTER:
======
[root@virt-012 ~]# rpm -q pcs
pcs-0.9.169-1.el7.x86_64
[root@virt-012 ~]# pcs cluster corosync
Error: Unable to read /etc/corosync/corosync.conf: No such file or directory
[root@virt-012 ~]# pcs cluster start
Error: cluster is not currently configured on this node
> OK
[root@virt-012 ~]# echo $?
1
[root@virt-012 ~]# systemctl status corosync.service
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/usr/lib/systemd/system/corosync.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Apr 14 15:48:24 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[31960]: [QB ] withdrawing server sockets
Apr 14 15:48:24 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[31960]: [SERV ] Service engine unloaded: corosync configuration map access
Apr 14 15:48:24 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[31960]: [QB ] withdrawing server sockets
Apr 14 15:48:24 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[31960]: [SERV ] Service engine unloaded: corosync configuration service
Apr 14 15:48:24 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[31960]: [QB ] withdrawing server sockets
Apr 14 15:48:24 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[31960]: [SERV ] Service engine unloaded: corosync cluster closed process group service v1.01
Apr 14 15:48:24 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[31960]: [QB ] withdrawing server sockets
Apr 14 15:48:24 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[31960]: [SERV ] Service engine unloaded: corosync cluster quorum service v0.1
Apr 14 15:48:25 virt-012.cluster-qe.lab.eng.brq.redhat.com corosync[1068]: Waiting for corosync services to unload:.[ OK ]
Apr 14 15:48:25 virt-012.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Stopped Corosync Cluster Engine.
> log unrelated to the 'pcs cluster start' action, corosync didn't fail
[root@virt-012 ~]# pcs cluster start --wait
Error: cluster is not currently configured on this node
[root@virt-012 ~]# pcs cluster start --wait=10
Error: cluster is not currently configured on this node
[root@virt-012 ~]# pcs cluster start --request-timeout=100
Error: cluster is not currently configured on this node
> OK
Marking as VERIFIED in pcs-0.9.169-1.el7
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/RHBA-2020:3964 |
Description of problem: [root@mckinley-01 ~]# pcs status Error: cluster is not currently running on this node # Proposed behavior [root@mckinley-01 ~]# pcs cluster start Error: cluster is not currently configured on this node # Current behavior [root@mckinley-01 ~]# pcs cluster start Starting Cluster... Job for corosync.service failed because the control process exited with error code. See "systemctl status corosync.service" and "journalctl -xe" for details. Error: unable to start corosync [root@mckinley-01 ~]# systemctl status corosync.service â<97><8f> corosync.service - Corosync Cluster Engine Loaded: loaded (/usr/lib/systemd/system/corosync.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2017-05-05 13:59:58 CDT; 30s ago Docs: man:corosync man:corosync.conf man:corosync_overview Process: 6968 ExecStart=/usr/share/corosync/corosync start (code=exited, status=1/FAILURE) May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: Starting Corosync Cluster Engine... May 05 13:59:58 mckinley-01.lab.msp.redhat.com corosync[6968]: Starting Corosync Cluster Engine (corosync): [FAILED] May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: corosync.service: control process exited, code=exited status=1 May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: Failed to start Corosync Cluster Engine. May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: Unit corosync.service entered failed state. May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: corosync.service failed. Version-Release number of selected component (if applicable): pcs-0.9.157-1.el7.x86_64