-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.17, 4.18
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
Unspecified
-
Production
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Configuring a multiline value for sshKey in install-config.yaml will prevent the Metal3 provisioning due to syntactically kernel parameters. This applies to initial installation openshift-install create cluster and also to the expansion of an existing BM IPI cluster (which can be installed with a "faulty" install-config.yaml by using platform=baremetal ABI).
Version-Release number of selected component (if applicable):
OpenShift 4.18.21
How reproducible:
Always with multiline sshKey
Steps to Reproduce:
1.Create install-config.yaml with multiline sshKey field. 2a. Attempt baremetal IPI. 3a. It fails to provision baremetal hosts. 2b. Install cluster with agent-based installation (using ISO file to circumvent described metal3 issue). 3b. In installed cluster, add a new BareMetalHost object. 4b. It fails to provision new BMH.
Actual results:
CBO/metal3 fails to provision a new BareMetalHost (or generally fails IPI installation). The Host will be stuck in the inspection image with no configured IP addresses and the error "Failed to start Acquire Live PXE rootfs Image".
Expected results:
CBO/metal3 successfully provisions a new BareMetalHost (or generally succeeds IPI installation)
Additional info:
See https://github.com/openshift/cluster-baremetal-operator/issues/509 for more detailed analysis. CBO should support multiline SSH Key in cluster/install-config or otherwise the installer should fail to validate install-config.yaml