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.
Bug 1230908 - pcs cluster cib-push doesn't allow to utilize XPath filter provided by underlying cibadmin
Summary: pcs cluster cib-push doesn't allow to utilize XPath filter provided by underl...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.2
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1230368
Blocks: 1212909
TreeView+ depends on / blocked
 
Reported: 2015-06-11 18:23 UTC by Jan Pokorný [poki]
Modified: 2016-10-21 13:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1230368
Environment:
Last Closed: 2016-10-21 13:02:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Pokorný [poki] 2015-06-11 18:23:59 UTC
Split from original bug as this is rather orhogonal:

+++ This bug was initially created as a clone of Bug #1230368 +++

Note that this situation (EDIT: see [bug 1230368 comment 0]) was
created just by pcs commands:

# pcs cluster setup --start ...
# pcs -f cib.xml ...; pcs -f cib.xml ...; ...
# pcs cluster cib-push cib.xml --config

so a user's carelessness is not to be blamed here

Note that underlying cibadmin command does support also --xpath option
and it would be helpful:

1/ add support for xpath passthrough (e.g., if scope starts with
   a slash, treat it as an XPath expression)

2/ --config option was made an alias to
>  scope=/cib/config/*[name() != 'nodes']
   so the nodes section is not included (hence overwritten)

Comment 2 Jan Pokorný [poki] 2015-06-24 21:36:09 UTC
This bug shall be resolved so as to make clufter "pcs commands"
output useful when batching the changes is enabled (default).
Hence a blocker for standalone clufter reintroduction: [bug 1212909].

Comment 6 Tomas Jelinek 2016-10-21 13:02:01 UTC
The original issue has been resolved as described in bz1230368.

We cannot really implement what is requested in part 2:
> 2/ --config option was made an alias to
> >  scope=/cib/config/*[name() != 'nodes']
>    so the nodes section is not included (hence overwritten)
If we make it to work this way, it would not be possible to update node attributes and utilization.

The only thing which is to be done is support for xpath in the "pcs cluster cib-push" command. This is rather advanced feature as it requires detailed understanding of CIB structure and pacemaker. Moreover it appears to be no longer demanded.

Closing this as wontfix. We can reopen if there is a demand for this feature in a future.


Note You need to log in before you can comment on or make changes to this bug.