Bug 1200835 - find_prop_value.sh shows also values from different keys
Summary: find_prop_value.sh shows also values from different keys
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhs-hadoop-install
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.0.4
Assignee: Jeff Vance
QA Contact: BigData QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-11 13:14 UTC by Martin Kudlej
Modified: 2015-05-13 17:54 UTC (History)
5 users (show)

Fixed In Version: 2.45-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-31 10:18:44 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:0761 0 normal SHIPPED_LIVE Red Hat Storage Server 3 Hadoop plug-in enhancement update 2015-03-31 14:17:20 UTC

Description Martin Kudlej 2015-03-11 13:14:04 UTC
Description of problem:
$ curl "http://localhost:8080/api/v1/clusters/TestCluster/configurations?type=core-site&tag=version1426078485279" -s -H 'X-Requested-By: X-Requested-By' -u admin:admin | grep key10
        "key10" : "value101",
        "key100" : "value100",

$ ./find_prop_value.sh key10 core localhost:8080 admin:admin TestCluster
value101,
        key100 : value100

but result from this command should be just: "value101". This problem is solved by proposed patch.

Version-Release number of selected component (if applicable):
rhs-hadoop-install-2_44-1.el6rhs.noarch

How reproducible:
100%


Proposed patch:

39c39
<     | grep $prop)"
---
>     | grep \"$prop\")"

Comment 2 Jeff Vance 2015-03-12 12:02:05 UTC
I agree with your patch. Good catch.

Comment 3 Jeff Vance 2015-03-16 23:37:37 UTC
fixed in 2.45

Comment 5 Martin Kudlej 2015-03-24 12:21:16 UTC
Tested with rhs-hadoop-install-2_47-1.el6rhs.noarch and it works -->VERIFIED

Comment 7 errata-xmlrpc 2015-03-31 10:18:44 UTC
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://rhn.redhat.com/errata/RHEA-2015-0761.html


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