Skip to content

Update QE views for 4.21 GA and add 4.22 view#3246

Open
rioliu-rh wants to merge 2 commits intoopenshift:mainfrom
rioliu-rh:update-qe-views-4.21-ga
Open

Update QE views for 4.21 GA and add 4.22 view#3246
rioliu-rh wants to merge 2 commits intoopenshift:mainfrom
rioliu-rh:update-qe-views-4.21-ga

Conversation

@rioliu-rh
Copy link
Contributor

@rioliu-rh rioliu-rh commented Feb 6, 2026

Summary

Updates component readiness QE views configuration to reflect 4.21 GA release and prepare for 4.22 development cycle.

Changes

  • Add 4.21-qe-auto-release view: New view for tracking automated-release procedure tests in 4.21.z releases
  • Update 4.21-qe-main: Changed base_release from 4.20 to 4.21 (now that 4.21 is GA)
  • Add 4.22-qe-main view: New view for tracking 4.22 development using 4.21 GA as baseline

All views follow consistent patterns with existing release configurations, using:

  • Base release: ga-30d to ga
  • Sample release: now-7d to now
  • Standard variant options (amd64, default featureset, ipi/upi, ovn, ha topology)
  • Same advanced options (minimum_failure: 3, confidence: 95, pity_factor: 5)

Jira: OCPERT-322

Summary by CodeRabbit

  • Chores
    • Added a new 4.21 QE auto-release configuration.
    • Updated 4.21 release configuration to reference the newer base release.
    • Added a new 4.22 QE release configuration mirroring the updated schema.
    • Extended 4.21 configuration to include additional owner, platform, and topology variant options.

- Add 4.21-qe-auto-release view for z-stream tracking
- Update 4.21-qe-main base_release from 4.20 to 4.21 (now GA)
- Add 4.22-qe-main view using 4.21 as baseline

OCPERT-322
@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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 6, 2026

Walkthrough

Added new release configurations for versions 4.21-qe-auto-release and 4.22-qe-main in the QE views configuration file. Updated the existing 4.21-qe-main entry to use base release 4.21 instead of 4.20. Both new configurations include variant options, advanced options, metrics, and regression tracking settings.

Changes

Cohort / File(s) Summary
QE Release Configurations
config/qe-views.yaml
Added 4.21-qe-auto-release and 4.22-qe-main release configurations with variant options (Architecture, Network, Platform), include variants (Procedure, Architecture, FeatureSet, Installer, Network, Owner, Platform, Topology), advanced options (minimum_failure, confidence, pity_factor, ignore_missing, ignore_disruption), and metrics/regression tracking settings. Updated 4.21-qe-main base_release from 4.20 to 4.21.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 7
✅ Passed checks (7 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: updating QE views for 4.21 GA release and adding a new 4.22 view configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Go Error Handling ✅ Passed PR modifies only YAML configuration file (config/qe-views.yaml) with no Go source code changes, making the Go error handling check inapplicable.
Sql Injection Prevention ✅ Passed The SQL injection prevention check is not applicable to this pull request. The PR modifies YAML configuration files, documentation files, and CI/linting configuration files. None of these file types contain SQL query construction code.
Excessive Css In React Should Use Styles ✅ Passed The custom check for excessive CSS in React components is not applicable to this PR as it only modifies a YAML configuration file.
Single Responsibility And Clear Naming ✅ Passed PR modifies only YAML configuration file, not source code. Check for code-level concerns is not applicable to declarative configuration data.

✏️ 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

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 and usage tips.

@openshift-ci openshift-ci bot requested review from deepsm007 and dgoodwin February 6, 2026 02:45
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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 `@config/qe-views.yaml`:
- Around line 763-817: The Owner variant for the new views is missing
service-delivery; update the include_variants -> Owner list in the views
"4.21-qe-auto-release", "4.21-qe-main", and "4.22-qe-main" to include
"service-delivery" alongside "qe" so these views match the historical ones
(e.g., "4.19-qe-auto-release", "4.20-qe-auto-release") and continue tracking
service-delivery tests.

@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e

Add service-delivery owner to maintain consistency with 4.19 and 4.20 views
and continue tracking service-delivery tests in 4.21+ releases.
@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e

@rioliu-rh
Copy link
Contributor Author

/test e2e

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2026

@rioliu-rh: 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.

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.

2 participants