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

Stop locking features on platform=none

XMLWordPrintable

    • Moderate
    • None
    • 2
    • Metal Platform 261
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, enabling a provisioning network by editing the cluster-wide `Provisioning` resource was only possible on installer-provisioned infrastructure clusters with platform type `baremetal`. On bare metal, single-node OpenShift (SNO) and user-provisioned infrastructure clusters resulted in a validation error. With this release, the excessive validation check has been removed, and enabling a provisioning network is now possible on bare-metal clusters with platform type `none`. As with installer-provisioned infrastructure clusters, users are responsible for making sure that all networking requirements are met for this operation. (link:https://issues.redhat.com/browse/OCPBUGS-43371[*OCPBUGS-43371*])
      Show
      * Previously, enabling a provisioning network by editing the cluster-wide `Provisioning` resource was only possible on installer-provisioned infrastructure clusters with platform type `baremetal`. On bare metal, single-node OpenShift (SNO) and user-provisioned infrastructure clusters resulted in a validation error. With this release, the excessive validation check has been removed, and enabling a provisioning network is now possible on bare-metal clusters with platform type `none`. As with installer-provisioned infrastructure clusters, users are responsible for making sure that all networking requirements are met for this operation. (link: https://issues.redhat.com/browse/OCPBUGS-43371 [* OCPBUGS-43371 *])
    • Bug Fix
    • Done

      The reality is that a lot of bare-metal clusters end up using platform=none. For example, SNO's only have this platform value, so SNO users can never use provisioning network (and thus any hardware that does not support virtual media). UPI and UPI-like clusters are by definition something that operators configure for themselves, so locking them out of features makes even less sense.

      With OpenStack based on OCP nowadays, I expect to see a sharp increase in complaints about this topic.

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

                Created:
                Updated:
                Resolved: