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

Prevent non-virtual-media drivers from being used with ProvisioningNetwork disabled

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • Important
    • None
    • None
    • Rejected
    • Metal Platform 271, Metal Platform 272
    • 2
    • In Progress
    • Bug Fix
    • Hide
      Previously, it was possible to create BareMetalHosts with a driver that requires network boot (such as IPMI or Redfish without virtual media) when provisioning network is disabled in the cluster configuration. This caused failures to boot during inspection or provisioning since nothing provided the correct DHCP options.

      Now such a host will fail to register with a "registration error" status and an error message pointing at disabled provisioning network. Customers must either enable the provisioning network or use a virtual media based driver (such as redfish-virtualmedia).
      Show
      Previously, it was possible to create BareMetalHosts with a driver that requires network boot (such as IPMI or Redfish without virtual media) when provisioning network is disabled in the cluster configuration. This caused failures to boot during inspection or provisioning since nothing provided the correct DHCP options. Now such a host will fail to register with a "registration error" status and an error message pointing at disabled provisioning network. Customers must either enable the provisioning network or use a virtual media based driver (such as redfish-virtualmedia).
    • None
    • None
    • None
    • None

      Description of problem: our customers hit this problem over and over again. They set "provisioningNetwork" to disabled in their install-config or Provisioning resource and then try to use IPMI.

      Right now, the result is machines failing to boot. Let us turn it to a validation failure.

      If the provisioningNetwork is set to "disabled":

      1. install-config validation must fail if a non-virtual-media driver is used on any host
      2. BMO fails to reconcile hosts with a non-virtual-media driver

      The AccessDetails interface already exposes a necessary flag: https://github.com/metal3-io/baremetal-operator/blob/main/pkg/hardwareutils/bmc/access.go#L92-L93

      We need a new BMO flag/environment variable to let it know that provisioning network is disabled.

      TBD: if we need an opt-out for the ZTP integration.

              rhn-engineering-dtantsur Dmitry Tantsur
              rhn-engineering-dtantsur Dmitry Tantsur
              None
              None
              Jad Haj Yahya Jad Haj Yahya
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: