Description of problem: Customer is running ovirt-engine-extension-aaa-ldap-1.4.2 in a RHV 4.4.4 environment. Their AAA config files are unable to reach the LDAP hosts until they disable IPV6 resolution. This issue was supposed to have been resolved/fixed in BZ 1880149. Version-Release number of selected component (if applicable): ovirt-engine-extension-aaa-ldap-1.4.2 How reproducible: Always
This seems to me like duplicate of BZ1896779
Anitha, is it possible to confirm that engine is configured on IPv4 only, but FQDN of LDAP server is relosved to both IPv4 and IPv6 addresses?
(In reply to Martin Perina from comment #3) > Anitha, is it possible to confirm that engine is configured on IPv4 only, > but FQDN of LDAP server is relosved to both IPv4 and IPv6 addresses? yes Martin, I've asked for the info and will revert as soon as I get an update
Moving to 4.4.6-1, because the fix is the same as for BZ1941541
Verified, as BZ1941541 was verified and the fix is the same
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 (0-day RHV Manager (ovirt-engine) [ovirt-4.4.6]), 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/RHBA-2021:2182
Due to QE capacity, we are not going to cover this issue in our automation