Skip to content

[release-4.22] OCPBUGS-93787: backport kubernetes/conformance umbrella suite#2705

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
bshaw7:backport-conformance-fix
Jun 30, 2026
Merged

[release-4.22] OCPBUGS-93787: backport kubernetes/conformance umbrella suite#2705
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
bshaw7:backport-conformance-fix

Conversation

@bshaw7

@bshaw7 bshaw7 commented Jun 29, 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.22.

Cherry-pick of:

Combined into a single clean change since #2694 simplified the approach from #2682. The final implementation adds the suite with its own Conformance qualifier, without needing AddGlobalSuite or parent references.

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.

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

Testing

/cc @stbenjam

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jun 29, 2026
@openshift-ci openshift-ci Bot requested a review from stbenjam June 29, 2026 06:50
@openshift-ci-robot 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 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

  • expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "5.0.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
  • 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-77783 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) instead
  • expected dependent Jira Issue OCPBUGS-77783 to target a version in 5.0.0, but no target version was set

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

Cherry-pick of:

Combined into a single clean change since #2694 simplified the approach from #2682. The final implementation adds the suite with its own Conformance qualifier, without needing AddGlobalSuite or parent references.

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.

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

Testing

/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

coderabbitai Bot commented Jun 29, 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: Enterprise

Run ID: adbf962c-aefc-431e-8ba0-ebd26d3a25db

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

Copy link
Copy Markdown

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

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

@bshaw7 bshaw7 force-pushed the backport-conformance-fix branch from 51b79f5 to 06a9b2a Compare June 29, 2026 07:00
@openshift-ci-robot

Copy link
Copy Markdown

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

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

@bshaw7

bshaw7 commented Jun 29, 2026

Copy link
Copy Markdown
Author

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

@openshift-ci

openshift-ci Bot commented Jun 29, 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.22-opct-platform-external-aws-ccm
  • periodic-ci-openshift-release-main-nightly-4.22-opct-platform-external-aws

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/41c1b7b0-7392-11f1-8bea-2179195cc66a-0

@stbenjam

Copy link
Copy Markdown
Member

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

Jira needs fixing I think

@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. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Jun 29, 2026
@bshaw7 bshaw7 changed the title [release-4.22] OCPBUGS-84961: backport kubernetes/conformance umbrella suite OCPBUGS-93787: backport kubernetes/conformance umbrella suite Jun 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

  • expected the bug to target the "4.22.0" 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-93787 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.22.

Cherry-pick of:

Combined into a single clean change since #2694 simplified the approach from #2682. The final implementation adds the suite with its own Conformance qualifier, without needing AddGlobalSuite or parent references.

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.

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

Testing

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

@bshaw7 bshaw7 changed the title OCPBUGS-93787: backport kubernetes/conformance umbrella suite [release-4.22] OCPBUGS-93787: backport kubernetes/conformance umbrella suite Jun 29, 2026
…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.22 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>
@bshaw7 bshaw7 force-pushed the backport-conformance-fix branch from 06a9b2a to 89525b2 Compare June 29, 2026 10:55
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jun 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

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

@openshift-ci-robot openshift-ci-robot removed the backports/validated-commits Indicates that all commits come to merged upstream PRs. label Jun 29, 2026
@bshaw7

bshaw7 commented Jun 29, 2026

Copy link
Copy Markdown
Author

/validate-backports

@openshift-ci-robot

Copy link
Copy Markdown

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

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

@bshaw7

bshaw7 commented Jun 29, 2026

Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

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

  • expected Jira Issue OCPBUGS-93787 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

@bshaw7

bshaw7 commented Jun 29, 2026

Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bshaw7: This pull request references Jira Issue OCPBUGS-93787, 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.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-84961 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-84961 targets the "5.0.0" version, which is one of the valid target versions: 5.0.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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jun 29, 2026
@bshaw7

bshaw7 commented Jun 29, 2026

Copy link
Copy Markdown
Author

Both CI test opct-platform-external-aws-ccm and opct-platform-external-aws shows openshift-kube-conformance count as 436 .

99-openshift-artifacts-collector   | running    |            | 0/0 (0 failures)          | status=runner=preparing results                   
Mon, 29 Jun 2026 12:12:30 UTC|2h26m10.077355956s> 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   |            | 401/436 (0 failures)      | complete                                          
20-openshift-conformance-validated | complete   |            | 820/820 (7 failures)      | complete                                          
80-openshift-tests-replay          | complete   |            | 3/4 (2 failures)          | complete                                          
99-openshift-artifacts-collector   | complete   |            | 0/0 (0 failures)          | complete                                          
time="2026-06-29T12:12:30Z" level=info msg="Waiting for post-processor..."
Mon, 29 Jun 2026 12:17:40 UTC|2h31m20.078686015s> 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     | 401/436 (0 failures)      | Total tests processed: 406 (406 pass / 0 failed)  
20-openshift-conformance-validated | complete   | failed     | 820/820 (7 failures)      | Total tests processed: 702 (694 pass / 8 failed)  
80-openshift-tests-replay          | complete   | failed     | 3/4 (2 failures)          | Total tests processed: 8 (5 pass / 3 failed)      
99-openshift-artifacts-collector   | complete   | passed     | 0/0 (0 failures)          | Total tests processed: 16 (16 pass / 0 failed)    
time="2026-06-29T12:17:40Z" 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-29 08:46:11+00:00> Done with code=0
Mon, 29 Jun 2026 12:05:57 UTC|2h23m40.679692363s> 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   |            | 401/436 (0 failures)      | complete                                          
20-openshift-conformance-validated | complete   |            | 820/820 (7 failures)      | complete                                          
80-openshift-tests-replay          | complete   |            | 3/4 (2 failures)          | complete                                          
99-openshift-artifacts-collector   | complete   |            | 0/0 (0 failures)          | complete                                          
time="2026-06-29T12:05:57Z" level=info msg="Waiting for post-processor..."
Mon, 29 Jun 2026 12:11:07 UTC|2h28m50.679582849s> 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     | 401/436 (0 failures)      | Total tests processed: 406 (406 pass / 0 failed)  
20-openshift-conformance-validated | complete   | failed     | 820/820 (7 failures)      | Total tests processed: 702 (694 pass / 8 failed)  
80-openshift-tests-replay          | complete   | failed     | 3/4 (2 failures)          | Total tests processed: 8 (5 pass / 3 failed)      
99-openshift-artifacts-collector   | complete   | passed     | 0/0 (0 failures)          | Total tests processed: 16 (16 pass / 0 failed)    
time="2026-06-29T12:11:07Z" 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-29 08:42:00+00:00> Done with code=0

@jubittajohn

Copy link
Copy Markdown

/retest

@jubittajohn

Copy link
Copy Markdown

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 29, 2026
@openshift-ci

openshift-ci Bot commented Jun 29, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bshaw7, jubittajohn

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 Jun 29, 2026
@stbenjam

Copy link
Copy Markdown
Member

/verified by CI

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

Copy link
Copy Markdown

@stbenjam: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@stbenjam

Copy link
Copy Markdown
Member

/remove-label backports/unvalidated-commits
/label backports/validated-commits

@openshift-ci openshift-ci Bot added backports/validated-commits Indicates that all commits come to merged upstream PRs. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Jun 30, 2026
@openshift-merge-bot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 7250fd5 and 2 for PR HEAD 89525b2 in total

@openshift-ci

openshift-ci Bot commented Jun 30, 2026

Copy link
Copy Markdown

@bshaw7: 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 03c5938 into openshift:release-4.22 Jun 30, 2026
23 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@bshaw7: Jira Issue Verification Checks: Jira Issue OCPBUGS-93787
✔️ 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-93787 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.22.

Cherry-pick of:

Combined into a single clean change since #2694 simplified the approach from #2682. The final implementation adds the suite with its own Conformance qualifier, without needing AddGlobalSuite or parent references.

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.

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

Testing

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

@openshift-merge-robot

Copy link
Copy Markdown

Fix included in release 4.22.0-0.nightly-2026-06-30-192322

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.

8 participants