Skip to content

SPLAT-2888: Created vSphere 4.22 zones techpreview jobs - #83392

Open
vr4manta wants to merge 1 commit into
openshift:mainfrom
vr4manta:SPLAT-2888
Open

SPLAT-2888: Created vSphere 4.22 zones techpreview jobs#83392
vr4manta wants to merge 1 commit into
openshift:mainfrom
vr4manta:SPLAT-2888

Conversation

@vr4manta

@vr4manta vr4manta commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

SPLAT-2888

Changes

  • Added new vSphere 4.22 zones TP jobs

Summary by CodeRabbit

  • Added scheduled vSphere 4.22 TechPreview nightly jobs for parallel and serial zones testing.
  • Configured both jobs with the vsphere-elastic profile, vSphere alert reporting, and the openshift-e2e-vsphere-zones workflow.
  • Configured the serial job to run the conformance serial suite.
  • CI confirmed the Jira reference SPLAT-2888, but reported a target-version mismatch with the openshift-5.0.0.* branch requirement.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 13, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

@vr4manta: This pull request references SPLAT-2888 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 story to target either version "5.0.0." or "openshift-5.0.0.", but it targets "openshift-4.22.z" instead.

Details

In response to this:

SPLAT-2888

Changes

  • Added new vSphere 4.22 zones TP jobs

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 Aug 13, 2026

Copy link
Copy Markdown
Contributor

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: 3e48b519-fb2a-4352-9705-7420887150bc

📥 Commits

Reviewing files that changed from the base of the PR and between 80778f2 and 5600531.

⛔ 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 (1)
  • ci-operator/config/openshift/release/openshift-release-main__nightly-4.22.yaml

Walkthrough

The nightly 4.22 release configuration adds parallel and serial vSphere TechPreview zones jobs. The jobs run daily with the vsphere-elastic profile and report failures and errors to the vSphere alerts channel.

Changes

vSphere zones nightly testing

Layer / File(s) Summary
Scheduled zones job definitions
ci-operator/config/openshift/release/openshift-release-main__nightly-4.22.yaml
Adds parallel and serial daily vSphere TechPreview jobs. Both use the zones workflow and vSphere alert reporting. The serial job selects the conformance serial suite.

Estimated code review effort: 2 (Simple) | ~10 minutes

Mergeability Score: 🔵 Low · up to 56005

The PR adds vSphere 4.22 tech-preview jobs, but its Jira target/version metadata may not align with the target branch and should be confirmed before merge. The job definitions are already generated, so this is a bounded owner-awareness issue rather than a merge blocker.

Possibly related PRs

  • openshift/release#79310: Adds scheduled vSphere TechPreview periodic jobs for different workflows and YAML files.

Suggested reviewers: dustman9000, bfournie

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the addition of vSphere 4.22 zones TechPreview jobs.
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 commit changes only release YAML and generated Prow jobs; added identifiers are static, and no Ginkgo It, Describe, Context, or When titles were introduced.
Test Structure And Quality ✅ Passed The pull request changes only two YAML configuration files and adds no Ginkgo test code, so the listed test-structure requirements do not apply.
Microshift Test Compatibility ✅ Passed The commit changes only two YAML CI configuration files and adds no Ginkgo tests or test code, so the MicroShift compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR changes only two YAML CI job files and adds no Ginkgo declarations or test source, so the SNO test-compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The diff only adds CI job definitions and generated Prow jobs; it adds no workload affinity, spread, replica, PDB, node-role selector, or taint toleration constraints.
Ote Binary Stdout Contract ✅ Passed The PR changes only YAML job and generated Prow declarations; the diff adds no OTE binary source or process-level stdout writes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR diff adds only YAML CI job definitions and generated Prow metadata. It adds no Ginkgo tests or IPv4 and external-connectivity logic.
No-Weak-Crypto ✅ Passed The pull request adds CI job configuration only; no weak-crypto algorithm, custom crypto, or secret comparison is introduced.
Container-Privileges ✅ Passed The PR adds only vSphere job scheduling and test fields; the generated pods add no privileged, host namespace, SYS_ADMIN, allowPrivilegeEscalation, or root settings.
No-Sensitive-Data-In-Logs ✅ Passed The diff adds CI YAML and generated job definitions only; Slack templates contain job/status fields and a prow.ci.openshift.org link, with no passwords, tokens, PII, or customer data.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@vr4manta: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-zones-techpreview-serial N/A periodic Periodic changed
periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-zones-techpreview N/A periodic Periodic changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jcpowermac

Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@vr4manta: requesting more than one rehearsal in one comment is not supported. If you would like to rehearse multiple specific jobs, please separate the job names by a space in a single command.

@vr4manta

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-zones-techpreview-serial periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-zones-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@vr4manta

Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 13, 2026
@openshift-ci

openshift-ci Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

@vr4manta: 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/rehearse/periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-zones-techpreview-serial 5600531 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-vsphere-ovn-zones-techpreview-serial

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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants