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