Bug 1896779

Summary:	Unable to access LDAP server using IPv6 when both engine and LDAP are configured with IPv6 interfaces only, but DNS records for LDAP contains also IPv4 address
Product:	[oVirt] ovirt-engine-extension-aaa-ldap	Reporter:	Petr Matyáš <pmatyas>
Component:	General	Assignee:	Martin Perina <mperina>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Guilherme Santos <gdeolive>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.4.2	CC:	bugs, gdeolive
Target Milestone:	ovirt-4.4.6-1	Keywords:	ZStream
Target Release:	1.4.3	Flags:	pm-rhel: ovirt-4.4+ gdeolive: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-extension-aaa-ldap-1.4.3	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-14 07:30:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1940138

Description Petr Matyáš 2020-11-11 14:19:30 UTC

Description of problem:
When I try to setup IPA with a DNS name resolving to both IPv4 and IPv6 addresses (however IPv4 is disabled on IDM and engine) login fails with: An error occurred while attempting to establish a connection to server hostname/ipv4:389:  SocketException(Network is unreachable (connect failed).

Version-Release number of selected component (if applicable):
ovirt-engine-extension-aaa-ldap-setup-1.4.2-1.el8ev.noarch

How reproducible:
always

Steps to Reproduce:
1. have engine and IDM with IPv6 only addresses active
2. have DNS hostname setup to link to both IPv4 and IPv6 for both engine and IDM
3. try to add the IDM as a provider for engine with ovirt-engine-extension-aaa-ldap-setup

Actual results:
unreachable network when it tries to log in

Expected results:
should default to IPv6 and should not fail when IPv4 is unreachable

Additional info:

Comment 2 Martin Perina 2021-05-05 09:41:12 UTC

Moving to 4.4.6-1, because the fix is the same as for BZ1941541

Comment 3 Guilherme Santos 2021-05-10 17:41:57 UTC

Verified, as BZ1941541 was verified and the fix is the same