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.
Cause:
User specifies both the --all flag and a list of nodes when running "pcs cluster start", "pcs cluster stop", "pcs cluster enable" or "pcs cluster disable".
Consequence:
Pcs ignores the node list and uses the --all flag.
Fix:
Check if both a list of nodes and the --all flag are specified.
Result:
Pcs exits with an error explaining only one of the --all flag and a list of nodes can be specified.
DescriptionJan Pokorný [poki]
2016-05-24 19:02:21 UTC
Looking merely at the provided syntax, it's not apparent there
is an internal mutual exclusion of "--all" and a list of nodes
(not reading further explanation, one might think that "--all"
is just a command modifier, i.e., do the start/stop in a coordinated
manner between the nodes being started/stopped, while this is true
modulo all known nodes are involved).
What about:
> start [[--all] | [node] [...]] [--wait[=<n>]]
plus perhaps a check that nodes are not being passed when --all is
present?
After Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.156-1.el7.x86_64
[vm-rhel72-1 ~] $ pcs cluster stop vm-rhel72-1 vm-rhel72-3 --all
Error: Cannot specify both --all and a list of nodes.
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/RHBA-2017:1958
Looking merely at the provided syntax, it's not apparent there is an internal mutual exclusion of "--all" and a list of nodes (not reading further explanation, one might think that "--all" is just a command modifier, i.e., do the start/stop in a coordinated manner between the nodes being started/stopped, while this is true modulo all known nodes are involved). What about: > start [[--all] | [node] [...]] [--wait[=<n>]] plus perhaps a check that nodes are not being passed when --all is present?