Bug 1241117 - Unable to show entities by it's parent name/id via CLI
Summary: Unable to show entities by it's parent name/id via CLI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-cli
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-3.6.1
: ---
Assignee: Juan Hernández
QA Contact: Ondra Machacek
URL:
Whiteboard: infra
Depends On: 1281803
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-08 13:37 UTC by Ondra Machacek
Modified: 2019-04-28 13:26 UTC (History)
6 users (show)

Fixed In Version: ovirt-engine-cli-3.6.0.0-0.4
Clone Of:
Environment:
Last Closed: 2015-12-22 13:29:05 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-3.6.z+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 43341 0 master MERGED cli: Don't remove "--" before validating parent options Never

Description Ondra Machacek 2015-07-08 13:37:41 UTC
Description of problem:
It is not possible to show user by it's domain name/id, because parameters --parent-domain-name nor --parent-domain-identifier are not supported.

Version-Release number of selected component (if applicable):
ovirt-engine-sdk-python-3.6.0.0-0.13.20150515.gitdd15fbf.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. Attach external ldap domain to engine.
2. Add few users from the ldap domain.
3. List those user by the domain name/id. $ show user admin --parent-domain-name external-domain

Actual results:
option "--parent-domain-name" is not supported, see help for more details.

Expected results:
User 'admin' from external-domain is shown.

Additional info:

Comment 1 Juan Hernández 2015-07-08 14:22:01 UTC
This happens because the validation of the "--parent-..." options isn't performed correctly, and it affects all the "show" commands, not just users. For example, it also fails for clusters, the following command will also fail:

  show cluster mycluster --parent-datacenter-name mydc

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-18 08:33:42 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

Comment 3 Ondra Machacek 2015-11-13 10:53:02 UTC
Not possible to verify, because of bug 1281736

Comment 4 Juan Hernández 2015-11-13 13:00:27 UTC
Note that the changes in the CLI required to fix this issue have already been made and are included since version 3.6.0.0 of the CLI, but verification is blocked by the engine bug 1281736. I'm changing the target milestone just for this reason.

Comment 5 Red Hat Bugzilla Rules Engine 2015-11-13 13:00:31 UTC
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.

Comment 6 Red Hat Bugzilla Rules Engine 2015-11-13 13:00:31 UTC
Fixed bug tickets must have target milestone set prior to fixing them. Please set the correct milestone and move the bugs back to the previous status after this is corrected.

Comment 7 Red Hat Bugzilla Rules Engine 2015-11-13 13:00:31 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 8 Ondra Machacek 2015-11-26 09:15:31 UTC
[root@om-ovirt36 ~]# rpm -q rhevm-cli
rhevm-cli-3.6.0.0-1.el6ev.noarch

[root@om-ovirt36 ~]# rpm -q rhevm
rhevm-3.6.1-0.2.el6.noarch

[RHEVM shell (connected)]# show user admin --parent-domain-name internal-authz

id         : 34663766626661392D633035372D343666322D626639322D303062333862636338636466
name       : admin
department : 
domain-id  : 696E7465726E616C2D617574687A
domain-name: internal-authz
email      : 
last_name  : 
namespace  : *
principal  : admin
user_name  : admin@internal-authz

Comment 9 Sandro Bonazzola 2015-12-16 12:22:26 UTC
Accordiing to target milestone and verification status this bug should be solved in oVirt 3.6.1. However, missing the target release field, this bug can't be moved to closed current release automatically.
Please check target_milestone and target_release and move to closed current release if included in oVirt <= 3.6.1.
Thanks.

Comment 10 Sandro Bonazzola 2015-12-22 13:29:05 UTC
oVirt 3.6.1 has been released and bz verified, moving to closed current release


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