Skip to content

OCPEDGE-2484: TNA RHCOS10 CI validation and testing#79034

Open
kasturinarra wants to merge 1 commit intoopenshift:mainfrom
kasturinarra:OCPEDGE-2484
Open

OCPEDGE-2484: TNA RHCOS10 CI validation and testing#79034
kasturinarra wants to merge 1 commit intoopenshift:mainfrom
kasturinarra:OCPEDGE-2484

Conversation

@kasturinarra
Copy link
Copy Markdown
Contributor

@kasturinarra kasturinarra commented May 8, 2026

Summary

This PR adds CI validation and testing for RHCOS10 (Red Hat CoreOS 10) with Two-Node Arbiter (TNA) configurations in OpenShift 4.23 nightly builds.

Changes

Four new nightly test jobs are added to the OpenShift release CI pipeline:

  1. Metal OVN Two-Node Arbiter: Tests baremetal deployments with RHCOS10 in tech preview mode
  2. Agent OVN Two-Node Arbiter: Tests agent-based deployments with TNA and IPv4 configuration
  3. Metal OVN Two-Node Arbiter Upgrade: Tests upgrade scenarios for baremetal TNA deployments with RHCOS10
  4. Metal OVN Two-Node Arbiter Private Tests: Tests private test scenarios with RHCOS10 and TNA configurations

All jobs are configured with OSSTREAM: rhel-10 to use Red Hat CoreOS 10 and FEATURE_SET="TechPreviewNoUpgrade" since this is tech preview functionality.

Files Modified

  • CI operator configuration (openshift-release-main__nightly-4.23.yaml): Defines the four new test job specifications with their workflows and environment variables
  • Release controller configuration (both public and private versions of release-ocp-4.23.json): Registers these jobs as optional verification steps in the release process, with retry limits and Prow job bindings

The changes enable automated CI validation of RHCOS10 support for TNA configurations as part of the OpenShift 4.23 release pipeline.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 8, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 8, 2026

@kasturinarra: This pull request references OCPEDGE-2484 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "5.0.0" version, but no target version was set.

Details

In response to this:

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
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 5a9babea-9dd8-4bc7-a50c-74ce1b4b9f10

📥 Commits

Reviewing files that changed from the base of the PR and between 88e6273 and adb8bf1.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/release/openshift-release-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (3)
  • ci-operator/config/openshift/release/openshift-release-main__nightly-4.23.yaml
  • core-services/release-controller/_releases/priv/release-ocp-4.23.json
  • core-services/release-controller/_releases/release-ocp-4.23.json

Walkthrough

Four new nightly test job definitions are added for OpenShift 4.23 to test two-node arbiter cluster configurations with RHEL 10. The jobs are defined in the CI operator configuration and wired into both public and private release verification configurations.

Changes

Test Job Definitions and Release Verification Configuration

Layer / File(s) Summary
CI Job Definitions
ci-operator/config/openshift/release/openshift-release-main__nightly-4.23.yaml
Four new nightly test jobs are added: e2e-metal-ovn-two-node-arbiter-rhcos10-techpreview, e2e-agent-ovn-two-node-arbiter-rhcos10-techpreview, e2e-metal-ovn-two-node-arbiter-upgrade-rhcos10-techpreview, and e2e-metal-ovn-two-node-arbiter-private-tests-rhcos10-tp. Each configures OSSTREAM: rhel-10, tech preview feature set, specific DEVSCRIPTS_CONFIG, and corresponding workflows; interval jobs run weekly (168h).
Release Verification Configuration
core-services/release-controller/_releases/release-ocp-4.23.json, core-services/release-controller/_releases/priv/release-ocp-4.23.json
All four jobs are added as optional verify entries with maxRetries: 2. The upgrade job variant includes upgrade: true. Each entry references the corresponding prowJob.name for periodic CI execution. Public and private configs both receive identical job entries.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: adding TNA RHCOS10 CI validation and testing jobs for OpenShift 4.23, matching the four new test jobs added across the configuration files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The PR modifies only CI/CD configuration files (YAML and JSON), not Ginkgo test code. The custom check for stable test names applies to Ginkgo test titles in Go code, which are absent from this PR.
Test Structure And Quality ✅ Passed The custom check for Ginkgo test code quality is not applicable to this PR. The PR only modifies CI configuration files (YAML/JSON), not test code. No _test.go files are present.
Microshift Test Compatibility ✅ Passed PR adds CI job definitions in YAML/JSON config files, not new Ginkgo test code. The check applies only when new tests (It(), Describe(), etc.) are added, which is not the case.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR adds CI job definitions and release controller configuration, not new Ginkgo test source code. The SNO compatibility check targets test implementations, not CI infrastructure configuration.
Topology-Aware Scheduling Compatibility ✅ Passed PR adds CI test configurations for TNA topology validation. Files are CI infrastructure (ci-operator, release-controller), not production manifests or operator code. No scheduling constraints present.
Ote Binary Stdout Contract ✅ Passed PR modifies only CI/CD configuration (YAML/JSON files defining test jobs). No Go source code or test binaries added/modified. OTE stdout check applies to test source code, not configurations.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR adds only CI configuration files referencing test workflows, no new Ginkgo test code. Check is not applicable.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci openshift-ci Bot requested review from AlexNPavel and dgoodwin May 8, 2026 08:52
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@kasturinarra
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-rhcos10-techpreview periodic-ci-openshift-release-main-nightly-4.23-e2e-agent-ovn-two-node-arbiter-rhcos10-techpreview periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-upgrade-rhcos10-techpreview periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-private-tests-rhcos10-tp

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@kasturinarra: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

@kasturinarra: 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/rehearse/periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-rhcos10-techpreview adb8bf1 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-rhcos10-techpreview
ci/rehearse/periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-private-tests-rhcos10-tp adb8bf1 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-private-tests-rhcos10-tp
ci/rehearse/periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-upgrade-rhcos10-techpreview adb8bf1 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-4.23-e2e-metal-ovn-two-node-arbiter-upgrade-rhcos10-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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants