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

Extra reboot with performance profile on 4.14 when mcp worker resumes with upgrade

XMLWordPrintable

    • -
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, during {product-title} updates in performance-tuned clusters, resuming a `MachineConfigPool` resource resulted in additional restarts for nodes in the pool. This was due to the performance profile controller reconciling against outdated machine configurations while the pool was paused. With this update, the controller reconciles against the latest planned machine configurations before the pool resumes, preventing additional node reboots. (link:https://issues.redhat.com/browse/OCPBUGS-31271[*OCPBUGS-31271*])
      Show
      * Previously, during {product-title} updates in performance-tuned clusters, resuming a `MachineConfigPool` resource resulted in additional restarts for nodes in the pool. This was due to the performance profile controller reconciling against outdated machine configurations while the pool was paused. With this update, the controller reconciles against the latest planned machine configurations before the pool resumes, preventing additional node reboots. (link: https://issues.redhat.com/browse/OCPBUGS-31271 [* OCPBUGS-31271 *])
    • 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:
              1 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: