© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Sorry, yes, the role is `ansible-
The logic is that it first checks for `ipaserver_domain` and then `ipaclient_domain` and errors out when neither is set [1]. When I debugged the play, `ipaserver_domain` was not set. I am not sure what is responsible to set it, but that in principle should be the default method of configuration, using `CloudDomain`.
[1] https:/
About the discovered through dns, that is unclear to the logic of that discovery. In principle, those should be group variables that set both `ipaserver_domain` and `ipaserver` is defined according to `CloudDomain` and the keytab info or undercloud registration.
But actually I don't think that the heat template would even handle this configuration properly, where the `CloudDomain` is different than ipaserver domain, even though the deploy documentation implies that it should work. For example, which `ipaclient_realm` will be used there?