Bug 2090836
Summary: | Bootstrap node should honor http proxy | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Heather Heffner <heheffne> |
Component: | Installer | Assignee: | Nobody <nobody> |
Installer sub component: | openshift-installer | QA Contact: | Yunfei Jiang <yunjiang> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | urgent | ||
Priority: | unspecified | CC: | acathrow, bmontgom, mpytlak, nmalik, padillon, skhoury, tkatarki, yunjiang |
Version: | 4.11 | Keywords: | ServiceDeliveryImpact |
Target Milestone: | --- | ||
Target Release: | 4.12.0 | ||
Hardware: | All | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-01-17 19:49:26 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: | |||
Bug Depends On: | |||
Bug Blocks: | 2104727 |
Description
Heather Heffner
2022-05-26 16:31:26 UTC
Installer Team: The CFE team will be working on this bugzilla - we have CFEPLAN-90 tracking progress. Setting this as blocker - as there are clear workarounds. @padillon what are the workarounds? where are they documented? Can we get an update on this bug - is this being planned Andrew - we are currently working on this bug the PR is ready and we are working on the e2e tests. > @padillon what are the workarounds? where are they documented? There are two workarounds: 1. User edits bootstrap ignition config to add proxy 2. User configures vpc as described in docs: https://docs.openshift.com/container-platform/4.10/installing/installing_aws/installing-aws-network-customizations.html#installation-configure-proxy_installing-aws-network-customizations > Can we get an update on this bug - is this being planned There is a PR open but it was not correctly linked. That should be corrected now but here is the link: https://github.com/openshift/installer/pull/5973 verified. PASS. OCP version: 4.12.0-0.nightly-2022-07-11-054352 Test scenarios: https://github.com/openshift/installer/pull/5973#issuecomment-1178510229 Note for UPI installation: When you provide ignition file to bootstrap instance, s3-uri format (e.g. s3://yunjiang-11p2d-07111019/bootstrap_07111019.ign) does not works with ignition proxy feature [1]. You can use s3-presign format. [1] https://coreos.github.io/ignition/configuration-v3_1 After speaking with Patrick, confirmed that this issue does not require doc text (bug fix) in the 4.12 release notes. The 4.11 doc for AWS was updated to accurately reflect the options user now have when deploying to a restricted environment, which includes using a proxy without VPC endpoints. [1] https://docs.openshift.com/container-platform/4.11/installing/installing_aws/installing-restricted-networks-aws-installer-provisioned.html#installation-custom-aws-vpc-requirements_installing-restricted-networks-aws-installer-provisioned 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 (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), 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/RHSA-2022:7399 |