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

Bug 1795241

Summary:	The presto-coordinator pod identifies as `presto`, needs hostAlias loopback for ipv6 to work
Product:	OpenShift Container Platform	Reporter:	Brett Tofel <btofel>
Component:	Metering Operator	Assignee:	Brett Tofel <btofel>
Status:	CLOSED ERRATA	QA Contact:	Peter Ruan <pruan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.0	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:27:22 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 Brett Tofel 2020-01-27 14:10:36 UTC

Description of problem: Presto application starts up and tries to announce itself using the discovery-uri: presto:8080. This fails to work in IPv6 single stack.

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


How reproducible: Launch IPv6 Openshift 4.3 cluster nightly build (should not matter which build). Note presto-coordinator-0 logs filled with announce failures.


Steps to Reproduce:
1. Launch IPv6 Openshift 4.3 cluster nightly build (should not matter which build).
2. Wait for presto-coordinator-o pod to come up.
3. Note presto-coordinator-0 logs filled with announcer failures.



Actual results: Presto fails to start cleanly under IPv6.


Expected results: Presto starts cleanly in the cluster under IPv6


Additional info:

Comment 2 Peter Ruan 2020-03-13 05:55:32 UTC

verified by looking at presto log there are not errors.

4.3.0-0.nightly-2020-02-06-120247-ipv6.6

Comment 4 errata-xmlrpc 2020-05-04 11:27:22 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