Skip to content

CNTRLPLANE-3206: add periodic e2e job for self-managed Azure v2#79876

Open
bryan-cox wants to merge 1 commit into
openshift:mainfrom
bryan-cox:CNTRLPLANE-3206
Open

CNTRLPLANE-3206: add periodic e2e job for self-managed Azure v2#79876
bryan-cox wants to merge 1 commit into
openshift:mainfrom
bryan-cox:CNTRLPLANE-3206

Conversation

@bryan-cox
Copy link
Copy Markdown
Member

@bryan-cox bryan-cox commented May 29, 2026

Summary

  • Adds a daily periodic e2e job (e2e-azure-v2-self-managed) for self-managed Azure HCP on the release-5.0 branch
  • Runs at 6am UTC using the hypershift-azure-e2e-v2-self-managed workflow with hypershift-azure cluster profile
  • Catches regressions outside of PR presubmit runs for the self-managed Azure v2 test suite
  • Adds n1minor release reference (OCP 4.22 ci stream) needed by the workflow for upgrade image dependencies

Test plan

  • Verify generated Prow job config is correct via make jobs WHAT=openshift/hypershift
  • Rehearse the periodic job with /pj-rehearse periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-azure-v2-self-managed

🤖 Generated with Claude Code

Summary by CodeRabbit

This PR updates the OpenShift CI configuration in the openshift/release repository to add a periodic e2e job for the HyperShift project targeting self-managed Azure v2 on the release-5.0 branch.

What changed in practical terms

  • Adds a new daily periodic e2e job named e2e-azure-v2-self-managed to the HyperShift release-5.0 periodic configuration. The job is scheduled to run at 06:00 UTC and executes the hypershift-azure-e2e-v2-self-managed workflow using the hypershift-azure cluster profile.
  • Introduces a releases.n1minor candidate pointing to OCP 4.22 on the CI stream (release:n1minor). This release reference is required by the new workflow for upgrade-image dependencies.
  • Configuration-only change: no source code or exported API changes.

Why this matters

  • Provides regular (daily) e2e validation of self-managed Azure v2 clusters outside of PR presubmits, increasing the chance to detect regressions for the 5.0 branch earlier in the release cycle.

Files affected (config)

  • ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml (new job + n1minor)
  • A matching n1minor entry was also added/updated in the 4.23 periodic config (ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml).

Notes

  • This is a config-only change; verification steps mentioned in the PR (make jobs and pj-rehearse) remain applicable.

@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 29, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 29, 2026

@bryan-cox: This pull request references CNTRLPLANE-3206 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 task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

  • Adds a daily periodic e2e job (e2e-azure-v2-self-managed) for self-managed Azure HCP on the release-5.0 branch
  • Runs at 6am UTC using the hypershift-azure-e2e-v2-self-managed workflow with hypershift-azure cluster profile
  • Catches regressions outside of PR presubmit runs for the self-managed Azure v2 test suite
  • Adds n1minor release reference (OCP 4.22 ci stream) needed by the workflow for upgrade image dependencies

Test plan

  • Verify generated Prow job config is correct via make jobs WHAT=openshift/hypershift
  • Rehearse the periodic job with /pj-rehearse periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-azure-v2-self-managed

🤖 Generated with Claude Code

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 29, 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: 1680dc6e-3134-4394-aa62-8d11883f9904

📥 Commits

Reviewing files that changed from the base of the PR and between c51a70e and 2daa697.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/openshift/hypershift/openshift-hypershift-release-4.23-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/hypershift/openshift-hypershift-release-5.0-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (2)
  • ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml
  • ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml

Walkthrough

Adds releases.n1minor (OCP 4.22 on ci) and a new periodic job e2e-azure-v2-self-managed (daily cron, hypershift-azure profile, OCP_IMAGE_N1: release:n1minor, env vars incl. HYPERSHIFT_AZURE_LOCATION: centralus) in HyperShift periodics for 4.23 and 5.0.

Changes

Hypershift Azure E2E Testing Configuration

Layer / File(s) Summary
Release candidate mapping
ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml, ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml
Defines releases.n1minor as a new OCP release candidate targeting version "4.22" on the ci stream.
Periodic Azure E2E test job
ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.23__periodics.yaml, ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml
Adds e2e-azure-v2-self-managed periodic job (cron), configured with hypershift-azure cluster profile, OCP_IMAGE_N1: release:n1minor, hypershift-azure-e2e-v2-self-managed workflow, and env vars including ENABLE_HYPERSHIFT_CERT_ROTATION_SCALE and HYPERSHIFT_AZURE_LOCATION: centralus.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested labels

lgtm, area/pipelines, rehearsals-ack

Suggested reviewers

  • enxebre
  • muraee
  • devguyio
🚥 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 specifically describes the main change: adding a periodic e2e job for self-managed Azure v2 testing, with a relevant JIRA ticket reference.
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 PR contains only YAML CI configuration files with no Ginkgo test definitions or test titles. The custom check for stable Ginkgo test names does not apply to configuration-only changes.
Test Structure And Quality ✅ Passed PR contains YAML CI configuration files only, not Ginkgo test code. Custom check for test code quality is not applicable to this PR.
Microshift Test Compatibility ✅ Passed PR only modifies CI configuration files (YAML); no new Ginkgo e2e tests are added. The custom check only applies to new test code, not CI job scheduling changes.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only adds CI configuration (YAML); no new Ginkgo e2e test code is added to this repository. Actual tests are from HyperShift project's hypershift-tests container image.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only Prow CI job configuration files, not deployment manifests, operator code, or controllers. Check applies to those entities only; no scheduling constraints introduced.
Ote Binary Stdout Contract ✅ Passed PR modifies only YAML CI configuration files (no executable code changes), making the OTE Binary Stdout Contract check not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR adds periodic CI job configuration and workflow definitions, not new Ginkgo test code. No test implementation files, test definitions, or IPv4/external connectivity assumptions were introduced.
No-Weak-Crypto ✅ Passed PR contains only YAML CI job configuration files with no weak crypto algorithms, custom crypto implementations, or non-constant-time secret comparisons.
Container-Privileges ✅ Passed PR modifies only ci-operator config files defining test jobs; no container manifests or privileged/security escalation settings found.
No-Sensitive-Data-In-Logs ✅ Passed PR adds only configuration for test jobs with no sensitive data: environment variables contain only boolean flags and public Azure region name, and release/workflow references are public identifiers.

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

openshift-ci Bot commented May 29, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox

The full list of commands accepted by this bot can be found here.

The pull request process is described 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-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 29, 2026
@openshift-ci openshift-ci Bot requested review from enxebre and muraee May 29, 2026 15:41
Add a daily periodic job (6am UTC) for the self-managed Azure v2 e2e
tests on the release-5.0 branch. This catches regressions outside of
PR presubmit runs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@bryan-cox: 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-hypershift-release-5.0-periodics-e2e-aws-external-oidc-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn-conformance-serial N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-openstack-aws-csi-cinder N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-external-oidc N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-kubevirt-metal-ovn N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-openstack-aws-csi-manila N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-conformance-cilium N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-conformance-cilium N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-v2-gke N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-azure-kubevirt-ovn N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-ibmcloud-ovn-iks N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-azure-v2-self-managed N/A periodic Periodic changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-kubevirt-azure N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-openstack-aws-nfv N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-kubevirt-metal-ovn N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-azure-v2-self-managed N/A periodic Periodic changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-azure-kubevirt-ovn N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-kubevirt-metal-ovn-disconnected N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-ibmcloud-ovn-roks N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aks-multi-x-ax N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-upgrade N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-aws-upgrade N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-powervs-ovn N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.23-periodics-e2e-azure-aks-ovn-conformance N/A periodic Ci-operator config changed

A total of 61 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here

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

openshift-ci Bot commented May 29, 2026

@bryan-cox: 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/ci-operator-config-metadata 2daa697 link true /test ci-operator-config-metadata

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

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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