Bug 1743314 - [RHHI.next] baremetal: installer uses wrong route IP for CACHEURL
Summary: [RHHI.next] baremetal: installer uses wrong route IP for CACHEURL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.0
Assignee: Russell Bryant
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-19 15:52 UTC by Steven Hardy
Modified: 2019-10-16 06:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:36:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:37:22 UTC

Description Steven Hardy 2019-08-19 15:52:33 UTC
Description of problem:

The initial baremetal integration can use the wrong IP for CACHEURL in some environments, notably most baremetal environments where the default route for the external network is likely to be an external router.

To avoid hitting deployment timeouts during cluster bootstrapping (and to save time/bandwidth when doing repeated testing, e.g in CI) we need to instead point to the default route for the provisioning network, such that a httpd mirror optionally can be run on the provisioning host.

Upstream references:

https://github.com/openshift/installer/issues/2232

https://github.com/openshift/installer/pull/2233

It's a one-line fix and only affects the experimental baremetal IPI installer platform.

Comment 2 errata-xmlrpc 2019-10-16 06:36:35 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-2019:2922


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