-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.14
-
Critical
-
None
-
Approved
-
False
-
Description of problem:
disconnect(proxy behind) private cluster, bootstrap node download ignition file from public s3
Version-Release number of selected component (if applicable):
4.12
How reproducible:
always
Steps to Reproduce:
1.install private cluster on disconnect cluster (proxy behind) platform: ibmcloud: region: eu-gb resourceGroupName: maxu-d1-rg vpcName: maxu-d1-vpc controlPlaneSubnets: - maxu-d1-control-plane-eu-gb-3 - maxu-d1-control-plane-eu-gb-2 - maxu-d1-control-plane-eu-gb-1 computeSubnets: - maxu-d1-compute-eu-gb-3 - maxu-d1-compute-eu-gb-2 - maxu-d1-compute-eu-gb-1 pullSecret: HIDDEN networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 serviceNetwork: - 172.30.0.0/16 machineNetwork: - cidr: 10.242.0.0/16 networkType: OpenShiftSDN publish: Internal proxy: httpProxy: http://proxy-user1:JYgU8...@10.242.128.4:3128 httpsProxy: http://proxy-user1:JYgU8...@10.242.128.4:3128 noProxy: test.no-proxy.com credentialsMode: Manual baseDomain: ibmcloud.qe.devcluster.openshift.com
Actual results:
bootstrap node fail to running
Expected results:
bootstrap running, install cluster succeed.
Additional info:
https://coreos.slack.com/archives/C01U40AM37F/p1665657861936119
- links to
-
RHEA-2023:5006 rpm