Bug 1172619 - [Docs][Technical][Async] RHEV REST API Invalid XML Example
Summary: [Docs][Technical][Async] RHEV REST API Invalid XML Example
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Andrew Burden
QA Contact: Tahlia Richardson
URL:
Whiteboard:
Depends On:
Blocks: 1200186
TreeView+ depends on / blocked
 
Reported: 2014-12-10 13:20 UTC by Philipp Gassmann
Modified: 2015-04-29 05:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1139266
Environment:
Build Name: 22723, Technical Guide-3.4-1.0 Build Date: 25-08-2014 13:27:56 Topic ID: 7641-591799 [Specified]
Last Closed: 2015-04-29 05:29:39 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Philipp Gassmann 2014-12-10 13:20:08 UTC
Title: RHEV REST API Invalid XML Example

Describe the issue:
The XML Example is syntactically invalid.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Technical_Guide/index.html#Power_Management_Elements

- It contains values outside of tags (order="primary")
- value is missing = (value "false">)

        <agents>
            <agent type="rsa">
                <address>192.168.1.111</address>
                <username>e.xample</username> order="primary"
                <password>p@55w0rd!</password>
                <options>
                    <option name="443" value="true"/> 
                    <option name="secure" value "false"/>
                </options>
                <concurrent>false</concurrent>
                <order>1</order>
            </agent>
            <agent type="ipmi">
                <address>192.168.1.112</address>
                <username>e.xample</username> order="primary"
                <password>p@55w0rd!</password>
                <options>
                    <option name="443" value="true"/> 
                    <option name="secure" value "false"/>
                </options>
                <concurrent>false</concurrent>
                <order>2</order>
            </agent>


Versions Applicable: 3.5, 3.4

Comment 2 Andrew Burden 2015-03-25 04:12:02 UTC
Thanks for the feedback, Philipp.

I've updated the topic to remove the floating 'order="primary"' element and included the following description for the 'options' element:
"
Fencing options for the selected type= specified with the option name="" and value="" strings.
"

Thanks again


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