machine-api-operator: BareMetalHost CRD not being installed
The CRD defined in install/0000_30_machine-api-operator_13_baremetalhost.crd.yaml is not being installed when the machine-api-operator launches, which means that the metal3 app crash loops on baremetal systems.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (15 by maintainers)
Commits related to this issue
- WIP: Ensure the Baremetal CRD is installed Adding the Baremetal CRD to kustomization.yaml to make sure it is applied. Fixes issue #397. — committed to sadasu/machine-api-operator by sadasu 5 years ago
- WIP: Ensure the Baremetal CRD is installed Moving install of the baremetal CRD to before 0000_30_machine-api-operator_11_deployment.yaml so that it is available at the time of Metal3 deployment. Fixe... — committed to sadasu/machine-api-operator by sadasu 5 years ago
- WIP: Ensure the Baremetal CRD is installed Moving install of the baremetal CRD to before 0000_30_machine-api-operator_11_deployment.yaml so that it is available at the time of Metal3 deployment. Fixe... — committed to sadasu/machine-api-operator by sadasu 5 years ago
- Ensure the Baremetal CRD is installed Moving install of the baremetal CRD to before 0000_30_machine-api-operator_11_deployment.yaml so that it is available at the time of Metal3 deployment. Fixes iss... — committed to sadasu/machine-api-operator by sadasu 5 years ago
- Ensure the Baremetal CRD is installed Moving install of the baremetal CRD to before 0000_30_machine-api-operator_11_deployment.yaml so that it is available at the time of Metal3 deployment. Fixes iss... — committed to sadasu/machine-api-operator by sadasu 5 years ago
I don’t understand the question. I think you’re asking why the installer creates them, instead of metal3? The host resources are associated with the master nodes, and allow the baremetal platform to monitor those boxes once the cluster is up. The data in the CRs comes from the installer, and is not available from any source inside the cluster. This is similar to how the Machine resources for the master nodes are created by the installer instead of the cluster API provider.
hey @sadasu the manifests under ./install are managed by the CVO, the fix proposed is unrelated. See https://github.com/openshift/cluster-version-operator/blob/master/docs/dev/operators.md#operator-integration-with-cvo The CRD is actually installed
This is likely a race or a bug in the baremetal component. If the CRD is a requirement for the component you probably want to ensure is installed before the mao deployment by changing the priority
0000_30_machine-api-operator_*of the CRD.