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

Cluster Compare - power save mode show deviation for RAN RDS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.14, 4.16, 4.18, 4.19
    • GitOps ZTP
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • Rejected
    • cluster-compare sprint 270, cluster-compare sprint 271
    • 2
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-55646. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-54201. The following is the description of the original issue:

      Description of problem:

          Deploying RAN RDS configuration with "powersave" mode cause Cluster Compare to report it as a deviation!

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

          4.19

      How reproducible:

          100%

      Steps to Reproduce:

          1. Add powersave configuration to ztp-site-conifg
          2. Deploy
          

      Actual results:

          Differences found in CR: tuned.openshift.io/v1_Tuned_openshift-cluster-node-tuning-operator_performance-patch, Compared To Reference CR: required/node-tuning-operator/TunedPerformancePatch.yaml
      diff -u -N /tmp/MERGED-1318713186/tuned-openshift-io-v1_tuned_openshift-cluster-node-tuning-operator_performance-patch /tmp/LIVE-2609132346/tuned-openshift-io-v1_tuned_openshift-cluster-node-tuning-operator_performance-patch
      --- /tmp/MERGED-1318713186/tuned-openshift-io-v1_tuned_openshift-cluster-node-tuning-operator_performance-patch	2024-11-06 17:58:59.284268445 -0500
      +++ /tmp/LIVE-2609132346/tuned-openshift-io-v1_tuned_openshift-cluster-node-tuning-operator_performance-patch	2024-11-06 17:58:59.284268445 -0500
      @@ -16,6 +16,10 @@
             [service]
             service.stalld=start,enable
             service.chronyd=stop,disable
      +      # vvv- Added for powersave mode
      +      [sysfs]
      +      /sys/devices/system/cpu/intel_pstate/max_perf_pct=75
      +      # ^^^- Added for powersave mode
           name: performance-patch
         recommend:
         - machineConfigLabels: 
      Differences found in CR: performance.openshift.io/v2_PerformanceProfile_openshift-node-performance-profile, Compared To Reference CR: required/node-tuning-operator/PerformanceProfile.yaml
      diff -u -N /tmp/MERGED-1039046811/performance-openshift-io-v2_performanceprofile_openshift-node-performance-profile /tmp/LIVE-223065574/performance-openshift-io-v2_performanceprofile_openshift-node-performance-profile
      --- /tmp/MERGED-1039046811/performance-openshift-io-v2_performanceprofile_openshift-node-performance-profile	2024-11-06 17:58:59.550273565 -0500
      +++ /tmp/LIVE-223065574/performance-openshift-io-v2_performanceprofile_openshift-node-performance-profile	2024-11-06 17:58:59.550273565 -0500
      @@ -6,11 +6,7 @@
         name: openshift-node-performance-profile
       spec:
         additionalKernelArgs:
      -  - efi=runtime
      -  - module_blacklist=irdma
      -  - rcupdate.rcu_normal_after_boot=0
      -  - vfio_pci.disable_idle_d3=1
      -  - vfio_pci.enable_sriov=1
      +  - cpufreq.default_governor=schedutil
         cpu:
           isolated: 2-31,34-63
           reserved: 0-1,32-33
      @@ -29,5 +25,5 @@
           enabled: true
         workloadHints:
           highPowerConsumption: false
      -    perPodPowerManagement: false
      +    perPodPowerManagement: true
           realTime: true  

      Expected results:

          Since it's a supported deployment configuration, this should not cause a deviation for cluster compare tool

      Additional info:

          

              jramsay1@redhat.com Jim Ramsay
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Dwaine Gonyier Dwaine Gonyier
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: