Bug 1795325

Summary:	Downloads deployment will fail on nodes configured with ipv6.disable=1
Product:	OpenShift Container Platform	Reporter:	bpeterse
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, jokerman, spadgett, yapei
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-15 17:33:44 UTC	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 bpeterse 2020-01-27 17:11:23 UTC

The console downloads deployment was updated to handle IPv6 with a graceful fallback to IPv4 under most circumestances:

https://github.com/openshift/console-operator/pull/375/files#diff-d6f339970508d6b626a788b9035d6c48R120

There are details in the comments on that PR. 
If nodes are explicitly configured to disable IPv6 via ipv6.disable=1, then the Python script is likely to fail and cli downloads will be unavailable.

Comment 1 bpeterse 2020-01-27 17:13:02 UTC

Severity here is unknown, I think it may be fine to bump this to a non-blocking 4.4.z stream bug but will look to confirm.

Comment 2 Yadan Pei 2020-03-26 08:21:06 UTC

Hi Ben, 

Does changing target release to 4.5.0 mean this issue is not a 4.4 release blocker? Is this intended? Do we still want to fix for 4.4? 

From QE's perspective, it should be fixed in 4.4

Comment 4 Yadan Pei 2020-04-03 07:55:32 UTC

Setting severity and target release, let me know if it's wrong

Comment 5 bpeterse 2020-05-08 16:09:30 UTC

We have not addressed this issue yet.

Comment 6 bpeterse 2020-05-15 20:55:26 UTC

Bumped to 4.6, not a 4.5 priority.

Comment 8 Samuel Padgett 2020-06-15 17:33:44 UTC


*** This bug has been marked as a duplicate of bug 1846922 ***