Details
-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.13
-
No
-
False
-
Description
Description of problem:
The installer doesn't refuse to install if the platform is baremetal and the baremetal capability is disabled.
Version-Release number of selected component (if applicable):
4.13
How reproducible:
Always.
Steps to Reproduce:
1. Create a cluster using `platform.type: baremetal` and disabling the `baremetal` capability.
Actual results:
Installation hangs with `bootkube.sh` and `cluster-bootstrap` repeatedly waiting for the `99_baremetal-provisioning-config.yaml` manifest (and any other metal3.io related manifests) to be applied.
Expected results:
The installation is refused immediately with an error message explaining that disabling the `baremetal` capability is incompatible with the baremetal platform.
Additional info:
[core@api ~]$ journalctl -f -u bootkube.service Apr 12 13:41:03 api.kni-qe-51.lab.eng.tlv2.redhat.com cluster-bootstrap[154439]: [#145] failed to create some manifests: Apr 12 13:41:03 api.kni-qe-51.lab.eng.tlv2.redhat.com cluster-bootstrap[154439]: "99_baremetal-provisioning-config.yaml": unable to get REST mapping for "99_baremetal-provisioning-config.yaml": no matches for kind "Provisioning" in version "metal3.io/v1alpha1"
Attachments
Issue Links
- causes
-
OCPBUGS-11712 3-Node Cluster Installation via ZTP Consistently Fails with Error [#145] on Bootstrap Node
- Closed