Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-25835

Installer should validate that 'baremetal' capability is enabled for baremetal platform

    XMLWordPrintable

Details

    • Low
    • No
    • Sprint 247, Sprint 248
    • 2
    • False
    • Hide

      None

      Show
      None

    Description

      If the user specifies baselineCapabilitySet: None in the install-config and does not specifically enable the capability baremetal, yet still uses platform: baremetal then the install will reliably fail.

      This failure takes the form of a timeout with the bootkube logs (not easily accessible to the user) full of errors like:

      bootkube.sh[46065]: "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"
      bootkube.sh[46065]: "99_openshift-cluster-api_hosts-0.yaml": unable to get REST mapping for "99_openshift-cluster-api_hosts-0.yaml": no matches for kind "BareMetalHost" in version "metal3.io/v1alpha1"

      Since the installer can tell when processing the install-config if the baremetal capability is missing, we should detect this and error out immediately to save the user an hour of their life and us a support case.

      Although this was found on an agent install, I believe the same will apply to a baremetal IPI install.

      Attachments

        Issue Links

          Activity

            People

              bfournie@redhat.com Robert Fournier
              zabitter Zane Bitter
              Jinyun Ma Jinyun Ma
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: