Bug 2078253

Summary:	[RFE] Request for RHUI Upstream content sites to be able to support IPV6 only RHEL clients
Product:	Red Hat Update Infrastructure for Cloud Providers	Reporter:	jalviso <jalviso>
Component:	Operations	Assignee:	RHUI Bug List <rhui-bugs>
Status:	NEW ---	QA Contact:	Radek Bíba <rbiba>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	gtanzill
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jalviso 2022-04-24 22:30:12 UTC

Description of problem:

AWS customer has deployed and run RHEL clients that only uses pure IPV6.
Fetching updates from Upstream content sites failed with Connection timeout issues. KBase https://access.redhat.com/articles/4720861 listed only IPV4 addresses. Internally deployed RHUA shows it is listening to IPV6 over port 443

Version-Release number of selected component (if applicable): All

How reproducible: always

Steps to Reproduce:

1. On a RHEL8 client assigned only with IPV6, run "dnf update"

Actual results:

2022-04-19T21:23:07+0000 DEBUG error: Curl error (28): Timeout was reached for https://rhui3.us-east-2.aws.ce.redhat.com/pulp/mirror/protected/rhui-client-config/rhel/server/8/x86_64/ha [Connection timed out after 8025618 milliseconds] (https://rhui3.us-east-2.aws.ce.redhat.com/pulp/mirror/protected/rhui-client-config/rhel/server/8/x86_64/ha).

Expected results:

RHEL8 client assigned only with IPV6 to be able to fetch updates.

Additional info:

"dnf update" or any automated update from AWS console succeeds if the client is assigned with IPV4 address