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
    • Done
    • Bug Fix
    • Hide
      * Before this update, when the provisioning network was disabled in the cluster configuration, you could create a bare-metal host with a driver that required a network boot, for example Intelligent Platform Management Interface (IPMI) or Redfish without virtual media. As a result, boot failures occurred during inspection or provisioning because the correct DHCP options could not be identified. With this release, when you create a bare-metal host in this scenario the host fails to register and the reported error references the disabled provisioning network. To create the host, you must enable the provisioning network or use a virtual-media-based driver, for example, Redfish virtual media. (link:https://issues.redhat.com/browse/OCPBUGS-54965[OCPBUGS-54965])
      Show
      * Before this update, when the provisioning network was disabled in the cluster configuration, you could create a bare-metal host with a driver that required a network boot, for example Intelligent Platform Management Interface (IPMI) or Redfish without virtual media. As a result, boot failures occurred during inspection or provisioning because the correct DHCP options could not be identified. With this release, when you create a bare-metal host in this scenario the host fails to register and the reported error references the disabled provisioning network. To create the host, you must enable the provisioning network or use a virtual-media-based driver, for example, Redfish virtual media. (link: https://issues.redhat.com/browse/OCPBUGS-54965 [ OCPBUGS-54965 ])
    • 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:
              6 Start watching this issue

                Created:
                Updated: