-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
4.13
-
Critical
-
No
-
AI-28
-
1
-
Rejected
-
False
-
-
-
4/18: telco reviewed
Description of problem:
Installation of 3-node compact cluster via ZTP fails with the following error on the bootstrap node: [154392]: [#145] failed to create some manifests: [154392]: "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"
Version-Release number of selected component (if applicable):
OCP 4.13.0-rc.2
How reproducible:
Consistently
Steps to Reproduce:
1. Configure hub cluster with OCP 4.13.0-rc.2, TALM, GitOps, ACM 2.7.3 2. Create 3-node compact bare metal managedcluster configuration in git 3. Initiate installation of managedcluster via ZTP 4. Cluster installation succeeds on regular nodes, fails on bootstrap node.
Actual results:
Bootstrap node installation fails with errors: [core@api ~]$ journalctl -b -f -u release-image.service -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"
Expected results: Managedcluster installation succeeds.
Additional info:
See comments for location of log files, must-gather, and install-related CRs from hub cluster.
- is caused by
-
OCPBUGS-11867 Installer doesn't reject installation when platform is baremetal and the baremetal capability is disabled
- New