Skip to content

[release-4.20] OCPBUGS-105592: backport kubernetes/conformance umbrella suite - #2741

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.20from
redhat-chai-bot:OCPBUGS-105592-backport-conformance-suite
Sep 4, 2026
Merged

[release-4.20] OCPBUGS-105592: backport kubernetes/conformance umbrella suite#2741
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.20from
redhat-chai-bot:OCPBUGS-105592-backport-conformance-suite

Conversation

@redhat-chai-bot

@redhat-chai-bot redhat-chai-bot commented Aug 11, 2026

Copy link
Copy Markdown

Summary

Backport the kubernetes/conformance suite with Conformance label filter from master (combines PRs #2682 and #2694) to release-4.20.

Same change as the 4.22 backport PR #2705 and 4.21 backport PR #2708.

What it does

Adds the kubernetes/conformance suite that selects only [Conformance]-labeled tests (~414 tests). This suite is used by OPCT for VCSP partner validations.

Without this fix, openshift-tests run kubernetes/conformance on 4.20 returns "suite not found".

Related


AI-generated. Review for accuracy.

@mtulio requested in Slack thread

@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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 11, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 11, 2026

Copy link
Copy Markdown

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-105592, which is invalid:

  • expected the bug to target the "4.20.z" version, but no target version was set
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-105592 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

Summary

Backport the kubernetes/conformance suite with Conformance label filter from master (combines PRs #2682 and #2694) to release-4.20.

Same change as the 4.22 backport PR #2705 and 4.21 backport PR #2708.

What it does

Adds the kubernetes/conformance suite that selects only [Conformance]-labeled tests (~414 tests). This suite is used by OPCT for VCSP partner validations.

Without this fix, openshift-tests run kubernetes/conformance on 4.20 returns "suite not found".

Related


AI-generated. Review for accuracy.

@mtulio requested in Slack thread

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

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 77c718ac-bd40-475c-a1b6-6e7e9d178e12

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

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.

@openshift-ci-robot

Copy link
Copy Markdown

@redhat-chai-bot: 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-merge-bot

Copy link
Copy Markdown

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@mtulio

mtulio commented Aug 11, 2026

Copy link
Copy Markdown

/payload-job periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-opct-platform-external-aws-upgrade

@mtulio

mtulio commented Aug 27, 2026

Copy link
Copy Markdown

/lgtm
/verified by CI (opct is using /minimal while this fix is not landing in 4.20.)
/assign @stbenjam @bshaw7

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 27, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mtulio: This PR has been marked as verified by CI (opct is using /minimal while this fix is not landing in 4.20.).

Details

In response to this:

/lgtm
/verified by CI (opct is using /minimal while this fix is not landing in 4.20.)
/assign @stbenjam @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 openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2026
@openshift-merge-bot

Copy link
Copy Markdown

Scheduling required tests:
/test configmap-scale
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-crun
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-runc
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp
/test e2e-metal-ipi-ovn-ipv6
/test k8s-e2e-conformance-aws
/test k8s-e2e-gcp-ovn
/test k8s-e2e-gcp-serial
/test perfscale-control-plane-6nodes

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn-hypershift

@redhat-chai-bot

Copy link
Copy Markdown
Author

/retest-required

The e2e-aws-ovn-hypershift failure is infrastructure-related (DNS resolution failures and TCP timeouts to hypershift devcluster API servers). Unrelated to this PR's 8-line suite definition change — all other 20 checks passed.


AI-generated. Review for accuracy.

@mtulio

mtulio commented Aug 28, 2026

Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@mtulio: This pull request references Jira Issue OCPBUGS-105592, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-105592 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

/jira refresh

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.

@mtulio

mtulio commented Aug 28, 2026

Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 28, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-94059 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-94059 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents
Details

In response to this:

/jira refresh

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.

@bshaw7

bshaw7 commented Aug 31, 2026

Copy link
Copy Markdown

/payload-job periodic-ci-openshift-release-main-nightly-4.20-opct-external-aws-ccm
/payload-job periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-opct-platform-external-aws-upgrade

@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown

@bshaw7: trigger 2 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
  • periodic-ci-openshift-release-main-nightly-4.21-upgrade-from-stable-4.20-opct-platform-external-aws-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/06af6440-a53a-11f1-974a-93916e0fc9db-0

@stbenjam

stbenjam commented Sep 4, 2026

Copy link
Copy Markdown
Member

/lgtm
/label backport-risk-assessed
/remove-label backports/unvalidated-commits
/label backports/validated-commits

@openshift-ci openshift-ci Bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. backports/validated-commits Indicates that all commits come to merged upstream PRs. labels Sep 4, 2026
@openshift-ci openshift-ci Bot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Sep 4, 2026

@bertinatto bertinatto left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/approve

@openshift-ci

openshift-ci Bot commented Sep 4, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, mtulio, redhat-chai-bot, stbenjam

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 4, 2026
@openshift-ci

openshift-ci Bot commented Sep 4, 2026

Copy link
Copy Markdown

@redhat-chai-bot: all tests passed!

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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 4012064 into openshift:release-4.20 Sep 4, 2026
22 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@redhat-chai-bot: Jira Issue Verification Checks: Jira Issue OCPBUGS-105592
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-105592 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Summary

Backport the kubernetes/conformance suite with Conformance label filter from master (combines PRs #2682 and #2694) to release-4.20.

Same change as the 4.22 backport PR #2705 and 4.21 backport PR #2708.

What it does

Adds the kubernetes/conformance suite that selects only [Conformance]-labeled tests (~414 tests). This suite is used by OPCT for VCSP partner validations.

Without this fix, openshift-tests run kubernetes/conformance on 4.20 returns "suite not found".

Related


AI-generated. Review for accuracy.

@mtulio requested in Slack thread

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-merge-robot

Copy link
Copy Markdown

Fix included in release 4.20.0-0.nightly-2026-09-05-062521

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. backports/validated-commits Indicates that 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.