Bug 1807169 - bootstrap IP is incorrect on IPv6
Summary: bootstrap IP is incorrect on IPv6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd Operator
Version: 4.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.5.0
Assignee: David Eads
QA Contact: ge liu
URL:
Whiteboard: no-qe
Depends On:
Blocks: 1771572 1807643 1808060
TreeView+ depends on / blocked
 
Reported: 2020-02-25 17:52 UTC by David Eads
Modified: 2020-08-04 18:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1807643 1808060 (view as bug list)
Environment:
Last Closed: 2020-08-04 18:02:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 3175 0 None closed bug 1807169: use localhost for bootstrap IP until bootkube is fixed 2020-06-30 12:15:17 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-08-04 18:02:18 UTC

Description David Eads 2020-02-25 17:52:31 UTC
It is possible to use localhost for the short term to get unstuck and correctly predict "correct" values in individual render commands.  This is a temporary workaround to ship 4.4.  The bootkube should be aware of the 'correct' ipv6 address to configuring rendering of multiple components.

Comment 3 ge liu 2020-03-24 10:04:35 UTC
Pls ignore typo of comment 2.

Comment 4 Sam Batschelet 2020-04-15 00:11:29 UTC
*** Bug 1797796 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2020-08-04 18:02:13 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 (OpenShift Container Platform 4.5 image release 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:2409


Note You need to log in before you can comment on or make changes to this bug.