Automated - Update config ./config/openshift.yaml

[openshift-bot]

/cc @

Summary by CodeRabbit

• Tests
  • Removed assisted e2e test jobs from OKD releases 4.12–4.18
  • Added new disruptive long-running test coverage for 4.22 nightly AWS builds
  • Updated test job configurations with enhanced metadata and multi-part testing formats

[openshift-ci-robot]

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: automatic mode

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• OWNERS

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

[coderabbitai]

Walkthrough

Removed OKD e2e-assisted jobs for releases 4.12–4.18, added a nightly disruptive long-running AWS e2e job for 4.22, and updated many periodic job entries in the variant registry to 4.22 with renamed multi-part/techpreview variants and expanded metadata fields.

Changes

Cohort / File(s)	Summary
OpenShift Configuration config/openshift.yaml	Removed periodic-ci-openshift-release-main-okd-<version>-e2e-assisted job entries for OKD releases 4.12–4.18; added periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning: true under nightly jobs.
Variant Registry Snapshot pkg/variantregistry/snapshot.yaml	Updated many job identifiers from 4.21→4.22 and introduced multi-part (-1of2, -2of2) and techpreview variants; adjusted JobTier values; added expanded metadata fields (Release, ReleaseMajor/Minor, Platform, OS, ContainerRuntime, FeatureSet, Owner, Procedure, etc.); added hidden periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning entry.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 6 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is vague and generic, using an automated template format that doesn't convey meaningful information about the specific configuration changes being made.	Replace the generic title with a more descriptive one that explains what was actually updated, such as 'Update OKD release jobs and add 4.22 nightly disruptive test' or 'Remove e2e-assisted jobs and add 4.22 disruptive-longrunning job'.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Go Error Handling	✅ Passed	The custom check for Go error handling patterns is not applicable to this PR as it exclusively modifies YAML configuration files, not Go source code.
Sql Injection Prevention	✅ Passed	The PR modifies only YAML configuration files and does not introduce code changes that construct or execute SQL queries.
Excessive Css In React Should Use Styles	✅ Passed	This custom check is not applicable to the provided pull request. The PR exclusively modifies YAML configuration files, not React components.
Single Responsibility And Clear Naming	✅ Passed	This PR modifies only YAML configuration files and introduces no new Go code, packages, structs, or methods. The Single Responsibility and Clear Naming check applies only to code-level architectural concerns, which are not present in configuration-only changes.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

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

[ngopalak-redhat]

/retest-required

@cpmeadors / @neisw This add the periodic job from PR openshift/release#74043 to sippy

[openshift-ci-robot]

Scheduling required tests:
/test e2e

[ngopalak-redhat]

• Requires an override like the previous PR: NO-JIRA: Fix the All panel in the RegressedTestsModal #3263 for ci/prow/e2e.
  @neisw / @smg247 Please review

[openshift-ci-robot]

Scheduling required tests:
/test e2e

[openshift-ci]

@openshift-bot: 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	265c687	link	true	/test e2e

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.