Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 232139

Summary: ccs_get on /foo/child::*[1] doesn't work if foo's child is an empty tag
Product: [Retired] Red Hat Cluster Suite Reporter: Lon Hohberger <lhh>
Component: ccsAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHBA-2007-0133 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-10 20:58:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 212121    
Description Flags
RHEL4 patch none

Description Lon Hohberger 2007-03-13 22:46:22 UTC
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 22:46:22 UTC
Created attachment 149999 [details]
RHEL4 patch

Comment 3 Kiersten (Kerri) Anderson 2007-03-19 19:55:22 UTC
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 20:04:03 UTC

Comment 8 Red Hat Bugzilla 2007-05-10 20:58:37 UTC
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.