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.
DescriptionJan Pokorný [poki]
2015-04-10 16:31:24 UTC
IMHO it would be appropriate to "distributify", at least by the mean
of specifying remote node (and provided that authentication is set up)
as opposed to local-only, all set/query operations provided.
IIRC, with ccs, you could always specify node(s) you want to work with
-- such modus operandi is simply missing in pcs in some cases.
"pcs resources list" is an example of the operation violating such
expectation. This is strange as pcs can be run on a dedicated machine
outside of cluster and hence resource-agents package is likely not
installed then.
[For this operation specifically, it would even make sense to be
sensitive about number of nodes to query
- single one: standard output as usual
- more: redacted output stating which resources are common, and then
per-node extras]
There may be more local-only operations to look at.
Comment 1Jan Pokorný [poki]
2015-04-15 12:34:25 UTC
This bug was originally triggered by discovery that pcs does not depend
on pacemaker{,-cli} in RHEL 6:
# rpm -qR pcs | grep -e pacemaker -e pc | echo Nothing
> Nothing
# rpm -q pcs
> pcs-0.9.139-5.el6.x86_64
Hence I was expecting that this is another form of saying "install pcs
whenever you want, manage arbitrary cluster with that incl. just the
external ones (i.e., the machine running pcs doesn't need to have
anything in common with clusters modulo pcs itself
[no pacemaker CLI tools need to be installed, etc.])".
Comment 2Jan Pokorný [poki]
2015-04-15 13:14:33 UTC
*** Bug 1217166 has been marked as a duplicate of this bug. ***
Comment 5Jan Pokorný [poki]
2016-03-07 15:08:44 UTC
A very specific use-case (commands run on virt-002):
# crm_attribute -t nodes -N virt-002 -n maintenance -v on
OR, when available
# pcs node maintenance virt-002
+
# systemctl status pacemaker.service
# pcs cluster status
> Error: cluster is not currently running on this node
while it (with or without interactive prompt or an extra option set) could
connect to one the active peers (if present) and indeed show the status
for the cluster that virt-002 is still a member of (just temporarily put
into the maintenance mode).
Comment 6Jan Pokorný [poki]
2016-03-07 15:10:15 UTC
re [comment 5]:
s/systemctl status pacemaker.service/systemctl stop pacemaker.service/
Comment 8RHEL Program Management
2020-12-15 07:34:01 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
IMHO it would be appropriate to "distributify", at least by the mean of specifying remote node (and provided that authentication is set up) as opposed to local-only, all set/query operations provided. IIRC, with ccs, you could always specify node(s) you want to work with -- such modus operandi is simply missing in pcs in some cases. "pcs resources list" is an example of the operation violating such expectation. This is strange as pcs can be run on a dedicated machine outside of cluster and hence resource-agents package is likely not installed then. [For this operation specifically, it would even make sense to be sensitive about number of nodes to query - single one: standard output as usual - more: redacted output stating which resources are common, and then per-node extras] There may be more local-only operations to look at.