Description of problem: Version-Release number of selected component (if applicable): rhevm-restapi-3.5.0-0.30.el6ev.noarch rhevm-cli-3.5.0.5-1.el6ev.noarch How reproducible: always Steps to Reproduce: 1. Add ldap domain into engine(ie via engine-manage-domains) 2. add user from this domain to engine. shell (connected)]# add user correlation_id domain-id domain-name expect user_name Actual results: Missing principal and namespace parameter Expected results: principal and namespace parameter are not missing Additional info:
This happens because the "principal" and "namespace" parameters aren't correctly documented in the RSDL metadata. Once the metadata is fixed the Python and Java SDKs will need to be regenerated. The CLI itself won't need any change.
Juan, any reason groups:add is not represented in RSDL?
(In reply to Yair Zaslavsky from comment #2) > Juan, any reason groups:add is not represented in RSDL? It is represented. From "rsdl_metadata.yaml": - name: /groups|rel=add description: add a new group to the system request: body: parameterType: Group signatures: - mandatoryArguments: {group.name: 'xs:string'} description: add a new group to the system urlparams: {} headers: Content-Type: {value: application/xml|json, required: true} Correlation-Id: {value: 'any string', required: false} And from the generated RSDL document: <link href="groups" rel="add"> <description>add a new group to the system</description> <request> <http_method>POST</http_method> <headers> <header required="true"> <name>Content-Type</name> <value>application/xml|json</value> </header> <header required="false"> <name>Correlation-Id</name> <value>any string</value> </header> </headers> <body> <type>Group</type> <parameters_set> <description>add a new group to the system</description> <parameter required="true" type="xs:string"> <name>group.name</name> </parameter> </parameters_set> </body> </request> <response> <type>Group</type> </response> </link>
Please set a target release.
What is the reason of have this in RHEV tracker and not have sdks there too? REST will work without this patch anyway(afaik), sdks not.. ? Also I think this should be ON_QA..
Juan? btw, I moved it to 3.5.3 because there were concerns about the ability to verify that in the near future.
I don't know why it is in the RHEV-M 3.5.1 tracker, I'm removing it.
(In reply to Juan Hernández from comment #7) > I don't know why it is in the RHEV-M 3.5.1 tracker, I'm removing it. Do we have a CLI release with this change? If so, can you move it to ON_QA?
This isn't a CLI bug, but a engine bug. As ovirt-engine-3.5.2_rc2 is already available for testing and contains the fix we can move to ON_QA. [1] http://lists.ovirt.org/pipermail/devel/2015-March/010087.html - oVirt 3.5.2 Second Release Candidate is now available for testing
# add user correlation_id domain-id domain-name expect namespace principal user_name
ovirt 3.5.2 was GA'd. closing current release.