-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.19.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
No
-
None
-
Approved
-
Installer Sprint 270
-
1
-
None
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
During the pre-merge testing of https://issues.redhat.com/browse/OCPBUGS-54902, we tried installing on bastion host, unfortunately failed to wait for bootstrapping to complete, where the control-plane machine keeps telling NetworkPluginNotReady.
Version-Release number of selected component (if applicable):
see the build https://prow.ci.openshift.org/view/gs/test-platform-results/logs/release-openshift-origin-installer-launch-aws-modern/1911592573848260608
How reproducible:
Always
Steps to Reproduce:
1. create VPC network/subnets/etc. 2. create bastion host within the VPC 3. "create install-config", then insert the interested settings (see [3]) 4. "create cluster" (see [4])
Actual results:
The cluster failed on bootstrapping stage, because the control-plane machine has network issue on pulling images, so that only few services running, see [5-7].
Expected results:
The installation on the bastion host should succeed.
Additional info:
The bootstrap log bundle is available at https://drive.google.com/file/d/1_HKQK3ltCQnCEBzEd_oDe9pbPgSrd2eb/view?usp=drive_link FYI in the same VPC, installing a cluster of "publish: External" succeeds (see [10]).
- blocks
-
OCPSTRAT-990 [Tech Preview] Allow customer managed DNS solutions for GCP: Implementation
-
- Closed
-
- is related to
-
OCPBUGS-54902 [GCP custom dns] installing a private cluster failed due to "unable to handle api server override: no ip address found in lbconfig"
-
- Closed
-
- links to
-
RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update