-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.11
-
Quality / Stability / Reliability
-
None
-
None
-
None
-
Moderate
-
None
-
Unspecified
-
None
-
None
-
Rejected
-
ShiftStack Sprint 242
-
1
-
+
-
None
-
If docs needed, set a value
-
None
-
None
-
None
-
None
-
None
Version:
$ openshift-install version
openshift-install 4.11.0-0.nightly-2022-04-12-000004
built from commit 496c1de207b3fd8ef838e832388df20781bd2efe
release image registry.ci.openshift.org/ocp/release@sha256:4c4ae72860c578c0080e83dd2369ec85f0ffc91ab4a6cb6f1ba0e6d44111ec5d
release architecture amd64
Platform: openstack
Please specify:
- IPI with Proxy+BYON with external CCM TP enabled.
What happened?
The installation fails due to bootstrap timing out:
time="2022-04-12T05:47:38-04:00" level=info msg="API v1.23.3+d36f9d8 up"
time="2022-04-12T05:47:38-04:00" level=info msg="Waiting up to 30m0s (until 6:17AM) for bootstrapping to complete..."
time="2022-04-12T06:17:38-04:00" level=debug msg="Fetching Bootstrap SSH Key Pair..."
[...]
time="2022-04-12T06:17:39-04:00" level=error msg="Cluster operator cluster-autoscaler Degraded is True with MissingDependency: machine-api not ready"
The installation is progressing despite the bootstrap stage timed out and the cluster is finally correctly set. This is observed persistently only with Kuryr and OVNKubernetes network type. With OpenshiftSDN we observed one successful installation.
What did you expect to happen?
Installation is successful. On OSP D/S CI it is successful 100% in all the releases < 4.11.
How to reproduce it (as minimally and precisely as possible)?
IPI installation from an installer-vm with two interfaces, one connected to the external network and one connected to a restricted network which is used as BYON in the install-config.yaml (attached). The installer-vm runs a proxy that enables external connectivity to the cluster while deploying.
Anything else we need to know?
must-gather and post-installation bundle linked on private comment.