Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1797801

Summary:	Metering IPV6 install fails when TLS/authentication is enabled
Product:	OpenShift Container Platform	Reporter:	tflannag
Component:	Metering Operator	Assignee:	tflannag
Status:	CLOSED ERRATA	QA Contact:	Peter Ruan <pruan>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	sd-operator-metering
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:33:06 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 tflannag 2020-02-03 22:11:38 UTC

Description of problem:
When attempting to run a Metering install on an AWS IPV6 cluster with TLS/authentication enabled (the default setting), the Hive metastore/server and reporting-operator ghostunnel sidecar containers fail to communicate with each other. 

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


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Peter Ruan 2020-03-13 06:59:13 UTC

verified with 4.4 tagged metering

pruan@MacBook-Pro ~/workspace/gocode/src/github.com/operator-framework/operator-metering (master●)$ oc get pods
NAME                                  READY   STATUS    RESTARTS   AGE
hive-metastore-0                      2/2     Running   0          3m17s
hive-server-0                         3/3     Running   0          3m17s
metering-operator-7b96748b96-96njb    2/2     Running   0          5m54s
presto-coordinator-0                  2/2     Running   0          2m43s
reporting-operator-6fc7fc5c4c-nl2pl   2/2     Running   0          2m8s

Comment 5 errata-xmlrpc 2020-05-04 11:33:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581