Skip to content

OCPBUGS-63132: disabled_tests: add flaky InPlacePodVerticalScaling tests#2642

Open
dgrisonnet wants to merge 1 commit intoopenshift:masterfrom
dgrisonnet:disable-flaky-ipvs-tests
Open

OCPBUGS-63132: disabled_tests: add flaky InPlacePodVerticalScaling tests#2642
dgrisonnet wants to merge 1 commit intoopenshift:masterfrom
dgrisonnet:disable-flaky-ipvs-tests

Conversation

@dgrisonnet
Copy link
Copy Markdown
Member

Since the InPlacePodVerticalScaling feature became beta and on by default in 1.33/4.20, its tests have been flaky both upstream and downstream.

This PR disables the tests known to flake to reduce the impact on component readiness until the tests are stabilized upstream.

@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Apr 10, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@dgrisonnet: This pull request references Jira Issue OCPBUGS-63132, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Since the InPlacePodVerticalScaling feature became beta and on by default in 1.33/4.20, its tests have been flaky both upstream and downstream.

This PR disables the tests known to flake to reduce the impact on component readiness until the tests are stabilized upstream.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Copy Markdown

@dgrisonnet: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 10, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dce88720-3cea-4090-8bc9-8d6a24edeccc

📥 Commits

Reviewing files that changed from the base of the PR and between 0a8ca47 and 2545e4d.

📒 Files selected for processing (1)
  • openshift-hack/cmd/k8s-tests-ext/disabled_tests.go

Walkthrough

Updated the disabled-tests list: one issue URL was replaced and multiple additional test names were added to the "Broken" disabled-tests category; no control-flow or logic changes.

Changes

Cohort / File(s) Summary
Disabled Tests Configuration
openshift-hack/cmd/k8s-tests-ext/disabled_tests.go
Replaced an OCPBUGS-63132 issue link from https://issues.redhat.com/... to https://redhat.atlassian.net/.... Appended several new disabled test entries to the "Broken" category (additional pod resize variants, a scheduler-related resize test, extra retry/deferred resize cases, multiple Burstable QoS resize scenarios, and a PodRejectionStatus test).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@dgrisonnet dgrisonnet force-pushed the disable-flaky-ipvs-tests branch from e0fa38e to 0a8ca47 Compare April 10, 2026 13:54
@openshift-ci-robot
Copy link
Copy Markdown

@dgrisonnet: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial April 10, 2026 13:55
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 10, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dgrisonnet
Once this PR has been reviewed and has the lgtm label, please assign jerpeter1 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dgrisonnet
Copy link
Copy Markdown
Member Author

/validate-backports

@openshift-ci-robot
Copy link
Copy Markdown

@dgrisonnet: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
openshift-hack/cmd/k8s-tests-ext/disabled_tests.go (1)

166-177: Move these new entries from Broken to Flaky for accurate triage taxonomy.

These additions are described as flaky in the PR objective, but they’re currently filed under Broken. That makes future cleanup/reporting noisier and obscures stabilization status.

Suggested diff
@@
-			// https://redhat.atlassian.net/browse/OCPBUGS-63132
-			"[sig-node] [Serial] Pod InPlace Resize Container (deferred-resizes) [FeatureGate:InPlacePodVerticalScaling] pod-resize-retry-deferred-test-3",
-			"[sig-node] [Serial] Pod InPlace Resize Container (scheduler-focused) [FeatureGate:InPlacePodVerticalScaling] [Beta] pod-resize-scheduler-tests"
-
-			// https://redhat.atlassian.net/browse/OCPBUGS-77990
-			"[sig-node] [Serial] Pod InPlace Resize Container (deferred-resizes) [FeatureGate:InPlacePodVerticalScaling] pod-resize-retry-deferred-test-2"
-
-			// https://redhat.atlassian.net/browse/OCPBUGS-64847
-			"[sig-node] Pod InPlace Resize Container [FeatureGate:InPlacePodVerticalScaling] [Beta] Burstable QoS pod, one container with cpu & memory requests + limits - decrease memory requests and increase memory limits"
-
-			// https://redhat.atlassian.net/browse/OCPBUGS-82071
-			"[sig-node] Pod InPlace Resize Container burstable pods - 1 container with all requests & limits set and resize policy mem restart resizing cpu requests"
-			"[sig-node] PodRejectionStatus Kubelet should reject pod when the node didn't have enough resource"
@@
 		"Flaky": {
 			"Job should run a job to completion when tasks sometimes fail and are not locally restarted", // seems flaky, also may require too many resources
+			// https://redhat.atlassian.net/browse/OCPBUGS-63132
+			"[sig-node] [Serial] Pod InPlace Resize Container (deferred-resizes) [FeatureGate:InPlacePodVerticalScaling] pod-resize-retry-deferred-test-3",
+			"[sig-node] [Serial] Pod InPlace Resize Container (scheduler-focused) [FeatureGate:InPlacePodVerticalScaling] [Beta] pod-resize-scheduler-tests",
+			// https://redhat.atlassian.net/browse/OCPBUGS-77990
+			"[sig-node] [Serial] Pod InPlace Resize Container (deferred-resizes) [FeatureGate:InPlacePodVerticalScaling] pod-resize-retry-deferred-test-2",
+			// https://redhat.atlassian.net/browse/OCPBUGS-64847
+			"[sig-node] Pod InPlace Resize Container [FeatureGate:InPlacePodVerticalScaling] [Beta] Burstable QoS pod, one container with cpu & memory requests + limits - decrease memory requests and increase memory limits",
+			// https://redhat.atlassian.net/browse/OCPBUGS-82071
+			"[sig-node] Pod InPlace Resize Container burstable pods - 1 container with all requests & limits set and resize policy mem restart resizing cpu requests",
+			"[sig-node] PodRejectionStatus Kubelet should reject pod when the node didn't have enough resource",
 		},

As per coding guidelines, "Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@openshift-hack/cmd/k8s-tests-ext/disabled_tests.go` around lines 166 - 177,
The listed test names currently placed under the Broken list should be moved to
the Flaky list to match the PR intent: remove the entries for the Pod InPlace
Resize Container and PodRejectionStatus tests (the three
deferred/rescheduler/scheduler-focused strings and the Burstable/QoS/resizing
entries shown in the diff) from the Broken collection and add them to the Flaky
collection; preserve the surrounding Jira comment lines (OCPBUGS-77990,
OCPBUGS-64847, OCPBUGS-82071) and maintain ordering/formatting in the Flaky
slice so triage reflects these tests as flaky rather than broken.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@openshift-hack/cmd/k8s-tests-ext/disabled_tests.go`:
- Around line 166-177: The listed test names currently placed under the Broken
list should be moved to the Flaky list to match the PR intent: remove the
entries for the Pod InPlace Resize Container and PodRejectionStatus tests (the
three deferred/rescheduler/scheduler-focused strings and the
Burstable/QoS/resizing entries shown in the diff) from the Broken collection and
add them to the Flaky collection; preserve the surrounding Jira comment lines
(OCPBUGS-77990, OCPBUGS-64847, OCPBUGS-82071) and maintain ordering/formatting
in the Flaky slice so triage reflects these tests as flaky rather than broken.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9d38d350-1207-414b-99ff-e2a880ad480d

📥 Commits

Reviewing files that changed from the base of the PR and between 9193b12 and e0fa38e.

📒 Files selected for processing (1)
  • openshift-hack/cmd/k8s-tests-ext/disabled_tests.go

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@openshift-hack/cmd/k8s-tests-ext/disabled_tests.go`:
- Around line 167-177: The multiline []string composite literal in
disabled_tests.go has several string entries missing trailing commas (the
elements like "[sig-node] [Serial] Pod InPlace Resize Container
(scheduler-focused) ...", "[sig-node] [Serial] Pod InPlace Resize Container
(deferred-resizes) ...", "[sig-node] Pod InPlace Resize Container ...",
"[sig-node] Pod InPlace Resize Container burstable pods ...", and "[sig-node]
PodRejectionStatus Kubelet should reject pod ...") which breaks Go parsing; fix
by adding a trailing comma after each string element in that slice literal
(ensure every line in the []string block ends with a comma, including the final
element) and run gofmt/go vet to confirm formatting and syntax correctness.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d2ef4e62-b3ad-40ec-9611-17acebf38535

📥 Commits

Reviewing files that changed from the base of the PR and between e0fa38e and 0a8ca47.

📒 Files selected for processing (1)
  • openshift-hack/cmd/k8s-tests-ext/disabled_tests.go

Comment thread openshift-hack/cmd/k8s-tests-ext/disabled_tests.go Outdated
…g tests

Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>
@dgrisonnet dgrisonnet force-pushed the disable-flaky-ipvs-tests branch from 0a8ca47 to 2545e4d Compare April 10, 2026 14:34
@openshift-ci-robot
Copy link
Copy Markdown

@dgrisonnet: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@dgrisonnet
Copy link
Copy Markdown
Member Author

@pacevedom I added the bug you are working on to this list, in case your port doesn't make it in time for 4.22. Please let me know if it makes sense to you

@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 10, 2026

@dgrisonnet: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-hypershift 2545e4d link true /test e2e-aws-ovn-hypershift
ci/prow/e2e-aws-ovn-runc 2545e4d link false /test e2e-aws-ovn-runc
ci/prow/e2e-aws-ovn-crun 2545e4d link true /test e2e-aws-ovn-crun
ci/prow/e2e-aws-ovn-fips 2545e4d link true /test e2e-aws-ovn-fips
ci/prow/verify 2545e4d link true /test verify

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants