Bug 1896779 - 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
Summary: Unable to access LDAP server using IPv6 when both engine and LDAP are configu...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-extension-aaa-ldap
Classification: oVirt
Component: General
Version: 1.4.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.6-1
: 1.4.3
Assignee: Martin Perina
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On:
Blocks: 1940138
TreeView+ depends on / blocked
 
Reported: 2020-11-11 14:19 UTC by Petr Matyáš
Modified: 2021-05-14 07:30 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-extension-aaa-ldap-1.4.3
Clone Of:
Environment:
Last Closed: 2021-05-14 07:30:25 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+
gdeolive: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 114519 0 None NEW Fix detection of IP version available 2021-04-28 08:01:02 UTC

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
Note You need to log in before you can comment on or make changes to this bug.