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

Component Readiness: [Node / Kubelet] [FeatureGate:InPlacePodVerticalScaling] test regressed

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Approved
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ⚠️ AI-Generated Content

      Sippy AI-assisted description; please review details for accuracy.

      Filed from: Test Regression Details

      Test Name

      [sig-node] [Serial] Pod InPlace Resize Container (scheduler-focused) [FeatureGate:InPlacePodVerticalScaling] [Beta] pod-resize-scheduler-tests [Suite:openshift/conformance/serial] [Suite:k8s]

      Overview

      This test is experiencing an ExtremeRegression.
      Test has a 86.96% pass rate, but 95.00% is required.

      Statistics

      Sample (being evaluated) Release: 4.20
      Start Time: 2025-10-08
      End Time: 2025-10-15
      Success Rate: 86.96%
      Successes: 20
      Failures: 3
      Flakes: 0

      Base (historical) Release: 4.19
      Start Time: 2025-05-18
      End Time: 2025-06-17
      Success Rate: 0%
      Successes: 0
      Failures: 0
      Flakes: 0

      CRITICAL: This appears to be a new test in the 4.20 release, as there are no historical base statistics. It is being held to a 95% success threshold.

      Sample Failure Outputs

      Job Run 1977319482556682240:

      tpod2" in namespace "e2e-pod-resize-scheduler-tests-9789" to be in phase Pending, but got phase: Running
          {
              s: "Expected pod \"testpod2\" in namespace \"e2e-pod-resize-scheduler-tests-9789\" to be in phase Pending, but got phase: Running",
          }
      

      Job Run 1977610990480527360:

      tpod2" in namespace "e2e-pod-resize-scheduler-tests-3182" to be in phase Pending, but got phase: Running
          {
              s: "Expected pod \"testpod2\" in namespace \"e2e-pod-resize-scheduler-tests-3182\" to be in phase Pending, but got phase: Running",
          }
      

      Job Run 1978004959479730176:

      tpod2" in namespace "e2e-pod-resize-scheduler-tests-5185" to be in phase Pending, but got phase: Running
          {
              s: "Expected pod \"testpod2\" in namespace \"e2e-pod-resize-scheduler-tests-5185\" to be in phase Pending, but got phase: Running",
          }
      

      Links to Relevant Jobs

      Patterns or Insights

      The test consistently fails with the message "Expected pod \"testpod2\" in namespace \"e2e-pod-resize-scheduler-tests-...\" to be in phase Pending, but got phase: Running". This indicates an issue where the pod is not entering the expected 'Pending' phase, but rather immediately transitioning to 'Running'. This suggests a problem with the pod's lifecycle management or the scheduler's interaction with it, specifically related to the InPlacePodVerticalScaling feature. In all observed failures, this test appears to be the primary failing test, suggesting a specific issue with the test or the feature it validates rather than a systemic cluster problem.

              rh-ee-atokubi Ayato Tokubi
              openshift-trt OpenShift Technical Release Team
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: