Bug 232139 - ccs_get on /foo/child::*[1] doesn't work if foo's child is an empty tag
ccs_get on /foo/child::*[1] doesn't work if foo's child is an empty tag
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: ccs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
Depends On:
Blocks: 212121
  Show dependency treegraph
Reported: 2007-03-13 18:46 EDT by Lon Hohberger
Modified: 2009-04-16 16:22 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2007-0133
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-10 16:58:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
RHEL4 patch (2.80 KB, patch)
2007-03-13 18:46 EDT, Lon Hohberger
no flags Details | Diff

  None (edit)
Description Lon Hohberger 2007-03-13 18:46:22 EDT
Description of problem:

If we have the following xml, and we issue the query "/foo/child::*[1]" to ccs:


It does not work - and returns -ENODATA.  If we change the XML to have some sort
of child - even a text node, i.e.:

  <bar>hello, world</bar>

ccs_get /foo/child::*[1] works correctly (returns "bar=hello, world").

This fix is required for #212121 to be completed correctly; with the attached
patch, ccs returns  "bar=" as the result of querying the first example instead

The patch also fixes ccs_set_state (which doesn't work at all).
Comment 1 Lon Hohberger 2007-03-13 18:46:22 EDT
Created attachment 149999 [details]
RHEL4 patch
Comment 3 Kiersten (Kerri) Anderson 2007-03-19 15:55:22 EDT
Can't be in both rhel 4.5 and cluster 4.5.  This is a cluster product fix, so
removing the rhel4.5 tag.  This one is good to go if we have a fix.  Do we have
a fix?
Comment 4 Lon Hohberger 2007-03-19 16:04:03 EDT
Comment 8 Red Hat Bugzilla 2007-05-10 16:58:37 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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