Bug 1038686

Summary: rest: accepted request body for glusterhook resolve action is incorrect
Product: Red Hat Gluster Storage Reporter: Dustin Tsang <dtsang>
Component: rhsc-sdkAssignee: Ramesh N <rnachimu>
Status: CLOSED ERRATA QA Contact: Dustin Tsang <dtsang>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 2.1CC: dpati, dtsang, mmahoney, mmccune, rhs-bugs, rnachimu, sharne
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cb11 Doc Type: Bug Fix
Doc Text:
Previously, the accepted format for the action parameter for the glusterhook resolve action was incorrect. Now, with this update, the format of the action parameter is corrected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 08:07:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
excerpt none

Description Dustin Tsang 2013-12-05 15:53:45 UTC
Created attachment 833224 [details]
excerpt

Description of problem:

The accepted body for a call to the glusterhooks/resolve action incorrect.
(POST api/clusters/{cluster:id}/glusterhooks/{glusterhook:id}/resolve)
rsdl excerpt attached.

Currently what is accepted:
<action>
  <host.name>${name}</host.name>
</action>

To follow the convention followed by all the other calls defined in the rsdl the request should allow:

<action>
  <host>
    <name>${name}</name>
  </host>
</action>
Version-Release number of selected component (if applicable):
rhsc-cb10

Comment 2 Dustin Tsang 2013-12-13 22:09:23 UTC
verified as fixed in rhsc-cb11

Comment 3 Shalaka 2014-01-21 08:52:29 UTC
Please review the edited DocText and signoff.

Comment 4 Ramesh N 2014-01-21 09:35:15 UTC
Doc test looks good.

Comment 6 errata-xmlrpc 2014-02-25 08:07:56 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.

http://rhn.redhat.com/errata/RHEA-2014-0208.html