Skip to content

Automated - Update config ./config/openshift.yaml#3264

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
openshift-bot:automated---update-config-./config/openshift.yaml
Feb 13, 2026
Merged

Automated - Update config ./config/openshift.yaml#3264
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
openshift-bot:automated---update-config-./config/openshift.yaml

Conversation

@openshift-bot
Copy link
Contributor

@openshift-bot openshift-bot commented Feb 11, 2026

/cc @

Summary by CodeRabbit

  • Chores
    • Updated test job configurations and metadata across multiple releases (4.12–4.22)
    • Added new test variants and platform configurations for expanded testing coverage
    • Reorganized job classifications and release identifiers for improved test management

@openshift-ci-robot
Copy link

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 openshift-ci bot requested review from deads2k and neisw February 11, 2026 22:06
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

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

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 11, 2026

Walkthrough

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

Changes

Cohort / File(s) Summary
OpenShift Configuration
config/openshift.yaml
Removed periodic-ci-openshift-release-main-okd-<version>-e2e-assisted entries for 4.12–4.18; added periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning: true and added a periodic-ci-stackrox-...-4.21-...-aws declaration in aropre/aroproduction sections.
Variant Registry Snapshot
pkg/variantregistry/snapshot.yaml
Added many new periodic job entries and metadata; renamed/renumbered blocks from 4.21→4.22 (including -1of2/-2of2 and techpreview variants); updated Release/ReleaseMajor/ReleaseMinor, Platform, JobTier, and expanded fields (OS, Owner, Network*, ContainerRuntime, FeatureSet, Procedure, LayeredProduct); introduced hidden periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning and other disruptive/longrunning variants.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 7 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The PR title is vague and generic, using 'Automated - Update config' without specifying what configuration changes or improvements are being made. Replace with a more specific title that describes the main changes, such as 'Replace e2e-assisted jobs with disruptive-longrunning job in OpenShift config' or similar.
✅ Passed checks (7 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.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main
Go Error Handling ✅ Passed PR only modifies YAML configuration files; no Go source code changes present.
Sql Injection Prevention ✅ Passed The PR does not violate SQL injection prevention guidelines; the new database_query.py tool uses psycopg2 with parameterized queries and contains no dynamic SQL construction with user input.
Excessive Css In React Should Use Styles ✅ Passed The custom check for excessive inline CSS in React components is not applicable to this PR as only YAML configuration files are modified, not React/JavaScript files.
Single Responsibility And Clear Naming ✅ Passed This PR only modifies YAML configuration files and does not introduce or change any Go packages, structs, methods, or type definitions.

✏️ 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
Copy link
Contributor

/retest-required

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

@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e

@ngopalak-redhat
Copy link
Contributor

@openshift-bot openshift-bot force-pushed the automated---update-config-./config/openshift.yaml branch from d521ef2 to 265c687 Compare February 12, 2026 10:05
@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e

@openshift-bot openshift-bot force-pushed the automated---update-config-./config/openshift.yaml branch from 265c687 to 6ed0a83 Compare February 12, 2026 22:04
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@pkg/variantregistry/snapshot.yaml`:
- Around line 280238-280261: The Release fields for the job key
periodic-ci-stackrox-stackrox-release-4.9-ocp-4-21-lp-interop-cr-acs-tests-aws
are incorrect for OCP 4.21; update the Release, ReleaseMajor, and ReleaseMinor
values to reflect the OCP version used by the job (set Release to "4.21",
ReleaseMajor to "4", and ReleaseMinor to "21") so they match the OCP version in
the job name.

Comment on lines +280238 to +280261
periodic-ci-stackrox-stackrox-release-4.9-ocp-4-21-lp-interop-cr-acs-tests-aws:
Aggregation: none
Architecture: amd64
CGroupMode: v2
ContainerRuntime: runc
FeatureSet: default
Installer: ipi
JobTier: candidate
LayeredProduct: lp-interop-acs
Network: sdn
NetworkAccess: default
NetworkStack: ipv4
OS: rhcos9
Owner: mpiit
Platform: aws
Procedure: none
Release: "4.9"
ReleaseMajor: "4"
ReleaseMinor: "9"
Scheduler: default
SecurityMode: default
Suite: unknown
Topology: ha
Upgrade: none
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Release field appears inconsistent with OCP version in job name.

The job name periodic-ci-stackrox-stackrox-release-4.9-ocp-4-21-lp-interop-cr-acs-tests-aws indicates this runs StackRox release 4.9 on OCP 4.21. However, the Release, ReleaseMajor, and ReleaseMinor fields are set to "4.9", "4", and "9" respectively.

Comparing with similar layered product entries (e.g., konveyor at line 3428 which has Release: "4.21" for an OCP 4.21 job), the Release field should track the OCP version, not the product version.

🔧 Suggested fix to align Release with OCP version
     Platform: aws
     Procedure: none
-    Release: "4.9"
+    Release: "4.21"
     ReleaseMajor: "4"
-    ReleaseMinor: "9"
+    ReleaseMinor: "21"
     Scheduler: default
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
periodic-ci-stackrox-stackrox-release-4.9-ocp-4-21-lp-interop-cr-acs-tests-aws:
Aggregation: none
Architecture: amd64
CGroupMode: v2
ContainerRuntime: runc
FeatureSet: default
Installer: ipi
JobTier: candidate
LayeredProduct: lp-interop-acs
Network: sdn
NetworkAccess: default
NetworkStack: ipv4
OS: rhcos9
Owner: mpiit
Platform: aws
Procedure: none
Release: "4.9"
ReleaseMajor: "4"
ReleaseMinor: "9"
Scheduler: default
SecurityMode: default
Suite: unknown
Topology: ha
Upgrade: none
periodic-ci-stackrox-stackrox-release-4.9-ocp-4-21-lp-interop-cr-acs-tests-aws:
Aggregation: none
Architecture: amd64
CGroupMode: v2
ContainerRuntime: runc
FeatureSet: default
Installer: ipi
JobTier: candidate
LayeredProduct: lp-interop-acs
Network: sdn
NetworkAccess: default
NetworkStack: ipv4
OS: rhcos9
Owner: mpiit
Platform: aws
Procedure: none
Release: "4.21"
ReleaseMajor: "4"
ReleaseMinor: "21"
Scheduler: default
SecurityMode: default
Suite: unknown
Topology: ha
Upgrade: none
🤖 Prompt for AI Agents
In `@pkg/variantregistry/snapshot.yaml` around lines 280238 - 280261, The Release
fields for the job key
periodic-ci-stackrox-stackrox-release-4.9-ocp-4-21-lp-interop-cr-acs-tests-aws
are incorrect for OCP 4.21; update the Release, ReleaseMajor, and ReleaseMinor
values to reflect the OCP version used by the job (set Release to "4.21",
ReleaseMajor to "4", and ReleaseMinor to "21") so they match the OCP version in
the job name.

@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e

@stbenjam
Copy link
Member

/test e2e

@openshift-bot openshift-bot force-pushed the automated---update-config-./config/openshift.yaml branch from 6ed0a83 to 26e4bb2 Compare February 13, 2026 10:05
@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e

@ngopalak-redhat
Copy link
Contributor

A possible fix for e2e test failure: #3266

@neisw
Copy link
Contributor

neisw commented Feb 13, 2026

/test e2e

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 13, 2026

@openshift-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 411cf9a into openshift:main Feb 13, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants