+++ This bug was initially created as a clone of Bug #1188176 +++ 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: --- Additional comment from Juan Hernández on 2015-02-02 06:19:13 EST --- 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. --- Additional comment from Yair Zaslavsky on 2015-02-05 08:57:18 EST --- Juan, any reason groups:add is not represented in RSDL? --- Additional comment from Juan Hernández on 2015-02-05 09:14:58 EST --- (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> --- Additional comment from Juan Hernández on 2015-02-05 09:21:30 EST --- Please set a target release.
If ovirt 3.5.2 == rhevm 3.5.1, should this fix be also in rhev 3.5.1? As I see there older package(rhevm-sdk-python-3.5.2.0-1.el6ev.noarch)
This issue was fixed in ovirt-engine-sdk-python-3.5.2.1 and rhevm-sdk-python-3.5.2.0 doesn't contain it because it is based on ovirt-engine-sdk-python-3.5.2.0. Currently there is no downstream bug requesting this fix, so at the moment it is not planned to include this fix in the RHEV-M 3.5.1 release. However, if the next 3.5.1 build is rebased using ovirt-engine-3.5.2 then the engine fix will be included in RHEV-M, and then the rhevm-sdk-python will need to be regenerated. Once it is regenerated this fix will be included.
ghf
What is the question?
Oops, sorry, the needinfo and comment message have been submitted by mistake, please ignore.
Verified on ovirt-engine-sdk-python-3.5.2.1
ovirt 3.5.2 was GA'd. closing current release.