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

New install-config fields in 4.13 are ignored without warning

XMLWordPrintable

    • Moderate
    • No
    • Sprint 237
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, when configuring the `install-config.yaml` file for use during an Agent-based installation, changing the `cpuPartitioning` field to a non-default value would not produce a warning to alert users that the field is ignored for Agent-based installations. With this update, changing the `cpuPartitioning` field will cause a warning to users that the configuration will not impact the install. (link:https://issues.redhat.com/browse/OCPBUGS-13662[*OCPBUGS-13662*])
      Show
      Previously, when configuring the `install-config.yaml` file for use during an Agent-based installation, changing the `cpuPartitioning` field to a non-default value would not produce a warning to alert users that the field is ignored for Agent-based installations. With this update, changing the `cpuPartitioning` field will cause a warning to users that the configuration will not impact the install. (link: https://issues.redhat.com/browse/OCPBUGS-13662 [* OCPBUGS-13662 *])
    • Bug Fix
    • Done

      The following install-config fields are new in 4.13:

      • cpuPartitioning
      • platform.baremetal.loadBalancer
      • platform.vsphere.loadBalancer

      These fields are ignored by the agent-based installation method. Until such time as they are implemented, we should print a warning if they are set to non-default values, as we do for other fields that are ignored.

              rh-ee-zniu zhenying niu
              zabitter Zane Bitter
              zhenying niu zhenying niu
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: