Bug 1743731

Summary: tell user there's nothing configured if they try to start a nonexistent cluster
Product: Red Hat Enterprise Linux 8 Reporter: Tomas Jelinek <tojeline>
Component: pcsAssignee: Ondrej Mular <omular>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: medium    
Version: 8.1CC: cfeist, cluster-maint, cluster-qe, cmarthal, idevat, mlisik, mmazoure, nhostako, omular, tojeline
Target Milestone: rc   
Target Release: 8.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: pcs-0.10.4-2.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1448569 Environment:
Last Closed: 2020-04-28 15:27:56 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:

Description Tomas Jelinek 2019-08-20 14:42:06 UTC 
+++ This bug was initially created as a clone of Bug #1448569 +++

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
Comment 2 Ondrej Mular 2019-11-29 08:33:55 UTC 
Upstream fix:
https://github.com/ClusterLabs/pcs/commit/633ab90da8c2d265a213169c1e64361da208a7a6

Test:
[root@rhel82-devel1 pcs]# pcs cluster start
Error: cluster is not currently configured on this node
[root@rhel82-devel1 pcs]# echo $?
1
Comment 3 Miroslav Lisik 2019-11-29 15:28:06 UTC 
Test:
[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.4-2.el8.x86_64

[root@r8-node-01 ~]# pcs cluster start
Error: cluster is not currently configured on this node
[root@r8-node-01 ~]# echo $?
1
Comment 7 errata-xmlrpc 2020-04-28 15:27:56 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/RHEA-2020:1568