Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 2Jan 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.
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