Hide Forgot
Description of problem: I would recommend that manage-domains tool will try to resolve FQDNs of machines that are provided using -ldapServers, prior to adding a domain. For example if -ldapSevers=a.example.com,b.example.com Then the tool should have a validation check that will check that a.example.com and b.example.com are resolvable. This is an idea that was raised by Marina at BZ994205 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This bug is referenced in ovirt-engine-3.4.0-beta3 logs. Moving to ON_QA
Tested the fix is present in ovirt-engine-tools-3.4.0-0.11.beta3.el6.noarch. I have two objections here. The error message should probably end with a dot instead of a comma. I'd also suggest removing the "Details" part, since the exception contains the domain name, so it makes no sense to show it twice. # engine-manage-domains add --domain=example.com --user=vdcadmin --provider=ActiveDirectory --ldap-servers="foo.example.com,not.resolvable.at.all" Cannot resolve LDAP server hostname 'not.resolvable.at.all'. Details: not.resolvable.at.all, Enter password: The domain example.com has been added to the engine as an authentication source but no users from that domain have been granted permissions within the oVirt Manager. Users from this domain can be granted permissions by editing the domain using action edit and specifying --add-permissions or from the Web administration interface logging in as admin@internal user. oVirt Engine restart is required in order for the changes to take place (service ovirt-engine restart). Manage Domains completed successfully
Verified in rhevm-tools-3.4.0-0.3.master.el6ev.noarch [root@pb-rh34 ~]# engine-manage-domains add --domain=example.com --user=vdcadmin --provider=ActiveDirectory --ldap-servers="foo.example.com,not.resolvable.at.all" Cannot resolve LDAP server hostname 'not.resolvable.at.all'. Enter password: The domain example.com has been added to the engine as an authentication source but no users from that domain have been granted permissions within the oVirt Manager. Users from this domain can be granted permissions by editing the domain using action edit and specifying --add-permissions or from the Web administration interface logging in as admin@internal user. oVirt Engine restart is required in order for the changes to take place (service ovirt-engine restart). Manage Domains completed successfully
Closing as part of 3.4.0