Skip to content

OPCT-380: Fix PinnedImages test to respect node taints#30970

Open
bshaw7 wants to merge 2 commits intoopenshift:release-4.20from
bshaw7:OPCT-380-backport-pinnedimages-4.20
Open

OPCT-380: Fix PinnedImages test to respect node taints#30970
bshaw7 wants to merge 2 commits intoopenshift:release-4.20from
bshaw7:OPCT-380-backport-pinnedimages-4.20

Conversation

@bshaw7
Copy link
Copy Markdown
Contributor

@bshaw7 bshaw7 commented Apr 7, 2026

Backport of OCPBUGS-78617 fix from main to release-4.20.

Problem

The PinnedImages conformance test was selecting worker nodes without considering node taints, causing test failures in environments with dedicated/tainted nodes (like OPCT test infrastructure).

Changes

  • Added GetReadySchedulableWorkerNodes() utility function in test/extended/util/nodes.go to filter out nodes with NoSchedule/NoExecute taints and nodes with control-plane/master roles
  • Updated addWorkerNodesToCustomPool() in pinnedimages.go to use the new utility function
  • Tests now skip gracefully when insufficient schedulable worker nodes exist (handles SNO and compact cluster scenarios)

This ensures the test works correctly across cluster topologies, including SNO and compact clusters.

Original PR

#30913

Related

/cc @bshaw7

Backport of OCPBUGS-78617 fix from main to release-4.20.

The PinnedImages conformance test was selecting worker nodes without
considering node taints, causing test failures in environments with
dedicated/tainted nodes (like OPCT test infrastructure).

Changes:
- Added GetReadySchedulableWorkerNodes() utility function in
  test/extended/util/nodes.go to filter out nodes with NoSchedule/NoExecute
  taints and nodes with control-plane/master roles
- Updated addWorkerNodesToCustomPool() in pinnedimages.go to use the new
  utility function
- Tests now skip gracefully when insufficient schedulable worker nodes exist
  (handles SNO and compact cluster scenarios)

This ensures the test works correctly across cluster topologies.

Original PR: openshift#30913
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 7, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 7, 2026

@bshaw7: This pull request references OPCT-380 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.z" version, but no target version was set.

Details

In response to this:

Backport of OCPBUGS-78617 fix from main to release-4.20.

Problem

The PinnedImages conformance test was selecting worker nodes without considering node taints, causing test failures in environments with dedicated/tainted nodes (like OPCT test infrastructure).

Changes

  • Added GetReadySchedulableWorkerNodes() utility function in test/extended/util/nodes.go to filter out nodes with NoSchedule/NoExecute taints and nodes with control-plane/master roles
  • Updated addWorkerNodesToCustomPool() in pinnedimages.go to use the new utility function
  • Tests now skip gracefully when insufficient schedulable worker nodes exist (handles SNO and compact cluster scenarios)

This ensures the test works correctly across cluster topologies, including SNO and compact clusters.

Original PR

#30913

Related

/cc @bshaw7

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 7, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d354fd8e-40cd-4d88-9c6b-8d8f9bdf8c98

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ 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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 7, 2026

@bshaw7: GitHub didn't allow me to request PR reviews from the following users: bshaw7.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

Backport of OCPBUGS-78617 fix from main to release-4.20.

Problem

The PinnedImages conformance test was selecting worker nodes without considering node taints, causing test failures in environments with dedicated/tainted nodes (like OPCT test infrastructure).

Changes

  • Added GetReadySchedulableWorkerNodes() utility function in test/extended/util/nodes.go to filter out nodes with NoSchedule/NoExecute taints and nodes with control-plane/master roles
  • Updated addWorkerNodesToCustomPool() in pinnedimages.go to use the new utility function
  • Tests now skip gracefully when insufficient schedulable worker nodes exist (handles SNO and compact cluster scenarios)

This ensures the test works correctly across cluster topologies, including SNO and compact clusters.

Original PR

#30913

Related

/cc @bshaw7

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.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 7, 2026

@bshaw7: This pull request references OPCT-380 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.z" version, but no target version was set.

Details

In response to this:

Backport of OCPBUGS-78617 fix from main to release-4.20.

Problem

The PinnedImages conformance test was selecting worker nodes without considering node taints, causing test failures in environments with dedicated/tainted nodes (like OPCT test infrastructure).

Changes

  • Added GetReadySchedulableWorkerNodes() utility function in test/extended/util/nodes.go to filter out nodes with NoSchedule/NoExecute taints and nodes with control-plane/master roles
  • Updated addWorkerNodesToCustomPool() in pinnedimages.go to use the new utility function
  • Tests now skip gracefully when insufficient schedulable worker nodes exist (handles SNO and compact cluster scenarios)

This ensures the test works correctly across cluster topologies, including SNO and compact clusters.

Original PR

#30913

Related

/cc @bshaw7

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
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 7, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bshaw7
Once this PR has been reviewed and has the lgtm label, please assign xueqzhan 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

@mtulio
Copy link
Copy Markdown
Contributor

mtulio commented Apr 7, 2026

/payload-job periodic-ci-openshift-release-main-nightly-4.20-opct-external-aws-ccm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 7, 2026

@mtulio: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-4.20-opct-external-aws-ccm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/82a672c0-328d-11f1-93ad-5f295a37ec7e-0

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 7, 2026

@bshaw7: The following test 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-gcp-ovn 863a27d link true /test e2e-gcp-ovn

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.

@mtulio
Copy link
Copy Markdown
Contributor

mtulio commented Apr 7, 2026

@mtulio: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-4.20-opct-external-aws-ccm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/82a672c0-328d-11f1-93ad-5f295a37ec7e-0

job failed to install, considering healthy history, I am re-trying:

/payload-job periodic-ci-openshift-release-main-nightly-4.20-opct-external-aws-ccm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 7, 2026

@mtulio: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-4.20-opct-external-aws-ccm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e4592150-32b2-11f1-9405-7f11b79bc11d-0

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

Labels

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.

3 participants