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

[release-4.14]Extra reboot with performance profile on 4.14 when mcp worker resumes with upgrade

XMLWordPrintable

    • -
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, after you performed an EUS-to-EUS update on your {product-title} cluster that involved pausing and unpausing the machine config pool, two reboot operations occured after the unpause operation. This additional reboot was not expected and was caused by the performance profile controller being reconciled against an older `MachineConfig` that is listed in the `MachineConfigPool`. With this release, the performance profile controller reconciles against the latest `MachineConfig` that is listed in the `MachineConfigPool` so that the extra reboot does not occur. (link:https://issues.redhat.com/browse/OCPBUGS-32980[*OCPBUGS-32980*])
      Show
      Previously, after you performed an EUS-to-EUS update on your {product-title} cluster that involved pausing and unpausing the machine config pool, two reboot operations occured after the unpause operation. This additional reboot was not expected and was caused by the performance profile controller being reconciled against an older `MachineConfig` that is listed in the `MachineConfigPool`. With this release, the performance profile controller reconciles against the latest `MachineConfig` that is listed in the `MachineConfigPool` so that the extra reboot does not occur. (link: https://issues.redhat.com/browse/OCPBUGS-32980 [* OCPBUGS-32980 *])
    • Bug Fix
    • Done

      When a PerformanceProfile is applied to a minor version upgrade and the worker mcp paused and then resumed at target version. The worker nodes go thru two reboots rendering multiple worker mc configs. With a default upgrade ( no PerformanceProfle) only the expected one reboot is observed.  

      Version-Release number of selected component (if applicable): 

      How reproducible 

          100%

      Steps to Reproduce:

          1.Create PerfProfile at pre upgrade 4.14 release
    2.pause worker mcp
    3.Upgrade to target version
    4. Resume MCP

      Actual results:

          workers need 2 reboots

      Expected results:

          One reboot

      Additional info:

          apiVersion: performance.openshift.io/v2
kind: PerformanceProfile
metadata:
  name: perf-profile-2m-worker
spec:
  cpu:
    reserved: 0-3
    isolated: 4-63
  workloadHints:
    realTime: false
  hugepages:
    defaultHugepagesSize: "2M"
    pages:
    - size: "2M"
      count: 24000
      node: 0
    - size: "2M"
      count: 24000
      node: 1
  realTimeKernel:
    enabled: false
  numa:
    topologyPolicy: "best-effort"
  net:
    userLevelNetworking: false
  nodeSelector:
    node-role.kubernetes.io/worker: ""

              vgrinber@redhat.com Vitaly Grinberg
              wilsondav Dave Wilson
              Mallapadi Niranjan Mallapadi Niranjan
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: