Description of problem: ovirt-engine-extension-aaa-ldap-setup generates to following properties file /etc/ovirt-engine/aaa/ldap-profile.properties include = <rfc2307-openldap.properties> pool.authz.auth.type = none pool.default.serverset.type = round-robin pool.default.serverset.round-robin.00.server = ldap01.example.com pool.default.serverset.round-robin.00.server = 636 pool.default.serverset.round-robin.01.server = ldap02.example.com pool.default.serverset.round-robin.01.server = 636 pool.default.serverset.round-robin.02.server = ldap03.example.com pool.default.serverset.round-robin.02.server = 636 pool.default.ssl.enable = true pool.default.ssl.insecure = true This is incorrect as the server is then set to 636 instead of the DNS record. Version-Release number of selected component (if applicable): ovirt-engine-extension-aaa-ldap-setup-1.3.7-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. LDAP implementations: 8 (OpenLDAP RFC-2307 Schema) 2. Use DNS (Yes, No) [Yes]: Yes 3. Available policy method: 3 (Round-robin between multiple hosts) 4. Please enter space separated list of hosts: ldap01.example.com ldap02.example.com ldap03.example.com Actual results: Provided properties file Expected results: pool.default.serverset.round-robin.00.port = 636 pool.default.serverset.round-robin.01.port = 636 pool.default.serverset.round-robin.02.port = 636 Additional info:
Verified on ovirt-engine-extension-aaa-ldap-1.3.9-0.0.master.gitaeab284.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1072