Bug 1217166

Summary: "pcs cluster stop <nodes>" from outside of cluster fails
Product: Red Hat Enterprise Linux 7 Reporter: Patrik Hagara <phagara>
Component: pcsAssignee: Chris Feist <cfeist>
Status: CLOSED DUPLICATE QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: cluster-maint, jpokorny, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-20 15:42:16 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 Patrik Hagara 2015-04-29 16:55:19 UTC
Description of problem:
"pcs cluster stop [node1] [node2] [node3]" appears to be trying to stop cluster on local node (that is not part of any cluster).

Version-Release number of selected component (if applicable):
[root@virt-069 ~]# rpm -q pcs
pcs-0.9.137-13.el7.x86_64

How reproducible:
always

Steps to Reproduce:
[root@virt-069 ~]# pcs cluster auth virt-0{78,79,80}
virt-078: Already authorized
virt-079: Already authorized
virt-080: Already authorized
[root@virt-069 ~]# pcs cluster stop virt-0{78,79,80}
Error: Unable to read /etc/corosync/corosync.conf: No such file or directory
[root@virt-069 ~]# pcs cluster stop --all
Error: Unable to read /etc/corosync/corosync.conf: No such file or directory
[root@virt-069 ~]# pcs cluster stop virt-078        
Error: Unable to read /etc/corosync/corosync.conf: No such file or directory
[root@virt-069 ~]# pcs cluster stop --all virt-0{78,79,80}
Error: Unable to read /etc/corosync/corosync.conf: No such file or directory
[root@virt-069 ~]# pcs cluster stop --help  

Usage: pcs cluster stop...
    stop [--all] [node] [...]
        Stop corosync & pacemaker on specified node(s), if a node is not
        specified then corosync & pacemaker are stopped on the local node.
        If --all is specified then corosync & pacemaker are stopped on all
        nodes.

Actual results:
see above

Expected results:
cluster stopped remotely

Additional info:
none

Comment 2 Jan Pokorný [poki] 2015-04-30 15:02:02 UTC
This could be dupe of [bug 1210833].  Yes, user's expectations are not
in line with what is implemented.

Comment 4 Tomas Jelinek 2015-11-20 15:42:16 UTC

*** This bug has been marked as a duplicate of bug 1210833 ***