[release-4.21] OCPBUGS-94059: backport kubernetes/conformance umbrella suite by bshaw7 · Pull Request #2708 · openshift/kubernetes

bshaw7 · 2026-06-30T07:13:52Z

Summary

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

Same change as the 4.22 backport PR #2705.

What it does

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

Testing

Validated on master via /payload-job: 428 tests, 0 failures
Validated on 4.22 via /payload-job (PR [release-4.22] OCPBUGS-93787: backport kubernetes/conformance umbrella suite #2705): 436 tests, 0 failures
Same 8-line change, same approach

/cc @stbenjam

…rella suite Backport the kubernetes/conformance suite with Conformance label filter from master (PRs openshift#2682 and openshift#2694 combined). The suite provides the minimal true upstream Kubernetes conformance tests used by OPCT for VCSP validations. Without this fix, running openshift-tests run kubernetes/conformance on 4.21 returns 'suite not found'. With this fix, the suite correctly selects only [Conformance]-labeled tests (~428 tests). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

openshift-ci-robot · 2026-06-30T07:13:57Z

@bshaw7: This pull request references Jira Issue OCPBUGS-94059, which is invalid:

expected the bug to target the "4.21.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-94059 to depend on a bug targeting a version in 4.22.0 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.21.

Same change as the 4.22 backport PR #2705.

What it does

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

Testing

Validated on master via /payload-job: 428 tests, 0 failures

Validated on 4.22 via /payload-job (PR [release-4.22] OCPBUGS-93787: backport kubernetes/conformance umbrella suite #2705): 436 tests, 0 failures

Same 8-line change, same approach

/cc @stbenjam

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 · 2026-06-30T07:14:01Z

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: Enterprise

Run ID: c63d1b18-0881-4605-b37b-d23c90556a29

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.}

openshift-ci-robot · 2026-06-30T07:14:02Z

@bshaw7: 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:

5e6c814|UPSTREAM: : OCPBUGS-94059: backport kubernetes/conformance umbrella suite: does not specify an upstream backport in the commit message

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

bshaw7 · 2026-06-30T07:14:23Z

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

openshift-ci · 2026-06-30T07:14:27Z

@bshaw7: 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.21-opct-external-aws-ccm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/52b4e350-7453-11f1-80df-cdf4084544b8-0

openshift-ci · 2026-06-30T07:14:29Z

[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 bertinatto 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:

DOWNSTREAM_OWNERS

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

bshaw7 · 2026-06-30T07:33:17Z

/jira refresh

openshift-ci-robot · 2026-06-30T07:33:22Z

@bshaw7: This pull request references Jira Issue OCPBUGS-94059, which is invalid:

expected the bug to target the "4.21.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 dependent Jira Issue OCPBUGS-84961 to target a version in 4.22.0, but it targets "5.0.0" instead

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.

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 · 2026-06-30T07:37:17Z

/jira refresh

openshift-ci-robot · 2026-06-30T07:37:22Z

@bshaw7: This pull request references Jira Issue OCPBUGS-94059, which is invalid:

expected dependent Jira Issue OCPBUGS-93787 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead
expected dependent Jira Issue OCPBUGS-84961 to target a version in 4.22.0, but it targets "5.0.0" instead

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.

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 · 2026-06-30T07:41:03Z

/jira refresh

openshift-ci-robot · 2026-06-30T07:41:07Z

@bshaw7: This pull request references Jira Issue OCPBUGS-94059, which is invalid:

expected Jira Issue OCPBUGS-94059 to depend on a bug targeting a version in 4.22.0 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.

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 · 2026-06-30T07:48:03Z

/jira refresh

openshift-ci-robot · 2026-06-30T07:48:07Z

@bshaw7: This pull request references Jira Issue OCPBUGS-94059, which is invalid:

expected dependent Jira Issue OCPBUGS-93787 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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.

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 · 2026-06-30T07:50:54Z

/jira refresh

openshift-ci-robot · 2026-06-30T07:50:59Z

@bshaw7: This pull request references Jira Issue OCPBUGS-94059, which is invalid:

expected dependent Jira Issue OCPBUGS-93787 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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.

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 · 2026-06-30T12:25:29Z

CI test shows expected count for openshift-kube-conformance

99-openshift-artifacts-collector   | running    |            | 0/0 (0 failures)          | status=runner=preparing results                   
Tue, 30 Jun 2026 10:40:10 UTC|1h55m0.041241726s> Global Status: post-processing
JOB_NAME                           | STATUS     | RESULTS    | PROGRESS                  | MESSAGE                                           
05-openshift-cluster-upgrade       | complete   |            | 1/1 (0 failures)          | complete                                          
10-openshift-kube-conformance      | complete   |            | 384/419 (0 failures)      | complete                                          
20-openshift-conformance-validated | complete   |            | 739/739 (6 failures)      | complete                                          
80-openshift-tests-replay          | complete   |            | 2/3 (1 failures)          | complete                                          
99-openshift-artifacts-collector   | complete   |            | 0/0 (0 failures)          | complete                                          
time="2026-06-30T10:40:10Z" level=info msg="Waiting for post-processor..."
Tue, 30 Jun 2026 10:45:10 UTC|2h0m0.040641543s> Global Status: complete
JOB_NAME                           | STATUS     | RESULTS    | PROGRESS                  | MESSAGE                                           
05-openshift-cluster-upgrade       | complete   | passed     | 1/1 (0 failures)          |                                                   
10-openshift-kube-conformance      | complete   | passed     | 384/419 (0 failures)      | Total tests processed: 386 (386 pass / 0 failed)  
20-openshift-conformance-validated | complete   | failed     | 739/739 (6 failures)      | Total tests processed: 628 (621 pass / 7 failed)  
80-openshift-tests-replay          | complete   | failed     | 2/3 (1 failures)          | Total tests processed: 4 (2 pass / 2 failed)      
99-openshift-artifacts-collector   | complete   | passed     | 0/0 (0 failures)          | Total tests processed: 16 (16 pass / 0 failed)    
time="2026-06-30T10:45:10Z" level=info msg="The execution has completed! Use retrieve command to collect the results and share the archive with your Red Hat partner."
2026-06-30 07:46:08+00:00> Done with code=0

bshaw7 · 2026-07-01T06:41:29Z

/jira refresh

openshift-ci-robot · 2026-07-01T06:41:37Z

@bshaw7: This pull request references Jira Issue OCPBUGS-94059, 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.21.z) matches configured target version for branch (4.21.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-93787 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-93787 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
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 · 2026-07-01T06:43:27Z

/retest

openshift-ci · 2026-07-01T10:35:56Z

@bshaw7: 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-cgroupsv2	`5e6c814`	link	true	`/test e2e-aws-ovn-cgroupsv2`
ci/prow/e2e-aws-ovn-techpreview	`5e6c814`	link	false	`/test e2e-aws-ovn-techpreview`

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-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jun 30, 2026

openshift-ci Bot requested a review from stbenjam June 30, 2026 07:13

openshift-ci-robot added 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 Jun 30, 2026

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 Jul 1, 2026

Uh oh!

Conversation

bshaw7 commented Jun 30, 2026

Summary

What it does

Testing

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Summary

What it does

Testing

Uh oh!

coderabbitai Bot commented Jun 30, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Uh oh!

bshaw7 commented Jun 30, 2026

Uh oh!

openshift-ci Bot commented Jun 30, 2026

Uh oh!

openshift-ci Bot commented Jun 30, 2026

Uh oh!

bshaw7 commented Jun 30, 2026

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Uh oh!

bshaw7 commented Jun 30, 2026

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Uh oh!

bshaw7 commented Jun 30, 2026

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Uh oh!

bshaw7 commented Jun 30, 2026

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Uh oh!

bshaw7 commented Jun 30, 2026

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Uh oh!

bshaw7 commented Jun 30, 2026

Uh oh!

bshaw7 commented Jul 1, 2026

Uh oh!

openshift-ci-robot commented Jul 1, 2026

Uh oh!

bshaw7 commented Jul 1, 2026

Uh oh!

openshift-ci Bot commented Jul 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants