-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14.0
Description of problem:
Openshift Installer supports HTTP Proxy configuration in a restricted environment. However, it seems the bootstrap node doesn't use the given proxy when it grabs ignition assets.
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-04-27-113605
How reproducible:
Always
Steps to Reproduce:
1. try IPI installation in a restricted/disconnected network with "publish: Internal", and without using Google Private Access
Actual results:
The installation failed, because bootstrap node failed to fetch its ignition config.
Expected results:
The installation should succeed.
Additional info:
We'd ever fixed similar issue on AWS (and Alibabacloud) by https://bugzilla.redhat.com/show_bug.cgi?id=2090836.
- blocks
-
OCPBUGS-33205 [gcp] Bootstrap node should honor http proxy when fetching bootstrap ignition
- Closed
- causes
-
OCPBUGS-32133 GCP Bucket creation twice
- Closed
- is cloned by
-
OCPBUGS-33205 [gcp] Bootstrap node should honor http proxy when fetching bootstrap ignition
- Closed
- relates to
-
OCPBUGS-32338 [gcp] bootstrap failed in restricted network + http proxy scenario, with cloud-credential telling "credentials requests are failing to sync"
- Closed
-
OCPBUGS-33709 Bootstrap proxy no longer used
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update
- mentioned on