Bug 1813232

Summary:	openshift-insights endpoints are down on ipv6 cluster
Product:	OpenShift Container Platform	Reporter:	Junqi Zhao <juzhao>
Component:	Insights Operator	Assignee:	Martin Kunc <mkunc>
Status:	CLOSED WORKSFORME	QA Contact:	Angelina Vasileva <anikifor>
Severity:	medium	Docs Contact:	Radek Vokál <rvokal>
Priority:	unspecified
Version:	4.3.z	CC:	avicenzi, calfonso, elgerman, inecas, wsun
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:
Clones:	1813233 1813234 (view as bug list)		Environment:
Last Closed:	2020-09-14 12:35:38 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:

Comment 2 Martin Kunc 2020-03-16 09:03:42 UTC

Hi Junqi,
when I looked that the cluster today, it looks that even Console doesn't work well and it looks more like a configuration issue.
Now it looks even Authentication pod doesn't work and even Openshift Monitoring service is not available in the DNS.
Unfortunatelly I dont know who to contact to check the cluster configuration.


Nevertheless, we did some Ipv6 tests and Insights Operator should be ready. I have verified with Monitoring Operator team and their operator should be also ready for Ipv6.

Can I suggest to move this case to someone responsible for the cluster, to adjust the configuration and if that still persists after that, feel free to assign back to me for further investigation.

Comment 7 Martin Kunc 2020-06-01 04:55:25 UTC

Jingi, this doesn't look its specific for Insights operators. Would it be fine to close the case ?

Comment 8 Martin Kunc 2020-06-01 05:01:49 UTC

This doesnt seem to be specific to IO or to IO 4.5, moving to 4.5.z until we decide whether there is something to fix.

Comment 9 Junqi Zhao 2020-06-01 05:57:07 UTC

(In reply to Martin Kunc from comment #7)
> Jingi, this doesn't look its specific for Insights operators. Would it be
> fine to close the case ?

if the issue is fixed, it's fine to close, otherwise, we should assign the bug to the corrosponding team

Comment 10 Martin Kunc 2020-06-01 06:01:27 UTC

Jingi, can you please verify if it is still reproducible ?