Skip to content

AGENT-1429: Add HA Dualstack periodic job for ISO_NO_REGISTRY#79360

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
pawanpinjarkar:add-HA-jobs-4-iso-no-registry
May 19, 2026
Merged

AGENT-1429: Add HA Dualstack periodic job for ISO_NO_REGISTRY#79360
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
pawanpinjarkar:add-HA-jobs-4-iso-no-registry

Conversation

@pawanpinjarkar
Copy link
Copy Markdown
Contributor

@pawanpinjarkar pawanpinjarkar commented May 15, 2026

  • Add a new job e2e-agent-ha-dualstack-iso-no-registry-techpreview to run HA Dualstack for ISO_NO_REGISTRY.
  • Increase job frequency to every 8 hours.

This PR updates the OpenShift Release nightly 5.0 CI configuration to enhance testing of the Assisted Installer component with baremetal deployments.

Changes to the release configuration:

  1. Increased test frequency: The existing e2e-agent-compact-iso-no-registry-techpreview periodic job's execution frequency was increased from every 12 hours (0 */12 * * *) to every 8 hours (0 */8 * * *), enabling more frequent validation of compact cluster deployments with ISO_NO_REGISTRY boot mode.

  2. New HA Dualstack test job: Added a new periodic job e2e-agent-ha-dualstack-iso-no-registry-techpreview that validates High Availability cluster deployments with dual-stack IPv4/IPv6 networking using ISO_NO_REGISTRY boot mode. The job runs every 8 hours on the equinix-ocp-metal cluster profile with TechPreviewNoUpgrade feature set enabled.

Both jobs test the Assisted Installer agent's ability to deploy OpenShift clusters using ISO images without an external container registry, addressing an important deployment scenario. The increased test frequency for compact deployments and the addition of HA dualstack testing improve validation coverage for different cluster topologies and network configurations.

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

openshift-ci-robot commented May 15, 2026

@pawanpinjarkar: This pull request references AGENT-1429 which is a valid jira issue.

Details

In response to this:

  • Add a new job e2e-agent-ha-dualstack-iso-no-registry-techpreview to run HA Dualstack for ISO_NO_REGISTRY.
  • Increase job frequency to every 8 hours.

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.

@openshift-ci openshift-ci Bot requested review from smg247 and xueqzhan May 15, 2026 21:12
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 15, 2026

Walkthrough

This PR updates CI job configuration for nightly OpenShift release testing. The existing compact ISO test runs more frequently (every 8 hours instead of 12), and a new HA dualstack ISO test job is added with identical schedule and TechPreview feature set configuration on the equinix-ocp-metal cluster profile.

Changes

CI Test Job Configuration Updates

Layer / File(s) Summary
Compact ISO test job schedule frequency increase
ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml
The existing e2e-agent-compact-iso-no-registry-techpreview job cron schedule changed from every 12 hours to every 8 hours for more frequent test execution.
New HA dualstack ISO test job definition
ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml
New e2e-agent-ha-dualstack-iso-no-registry-techpreview job configured with HA IPv4v6 scenario, ISO NO_REGISTRY boot mode, ISO builder cache cleanup, TechPreviewNoUpgrade feature set, equinix-ocp-metal cluster profile, and 8-hour recurring schedule.

🎯 2 (Simple) | ⏱️ ~8 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 'AGENT-1429: Add HA Dualstack periodic job for ISO_NO_REGISTRY' clearly summarizes the main change: adding a new HA Dualstack periodic job for ISO_NO_REGISTRY testing, which directly matches the changeset.
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 modifies only YAML CI configuration files, not Ginkgo test code. The custom check for stable test names does not apply to CI job definitions.
Test Structure And Quality ✅ Passed This PR modifies only CI/CD configuration YAML files for job scheduling. It contains no Ginkgo test code, so the custom check for test quality requirements is not applicable.
Microshift Test Compatibility ✅ Passed This PR only modifies CI configuration (YAML files). No new Ginkgo e2e tests are added. The check applies only when new tests are added, which is not the case.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR modifies only CI configuration files (YAML). No Ginkgo e2e test code is added. SNO compatibility check only applies to new test code, not CI configuration changes.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only ci-operator job configuration (not deployment manifests), containing no Kubernetes manifests, pod specs, or scheduling constraints. Check not applicable.
Ote Binary Stdout Contract ✅ Passed PR only modifies CI/CD job configuration YAML. OTE Binary Stdout Contract applies to test binary code, not CI definitions. No executable code or binaries modified.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR modifies only CI job configuration (YAML), not test source code. The custom check applies to Ginkgo e2e tests (Go code), which this PR does not add.

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

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

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/cc @bfournie

@openshift-ci openshift-ci Bot requested a review from bfournie May 15, 2026 21:14
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@pawanpinjarkar: 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-5.0-e2e-agent-ha-dualstack-iso-no-registry-techpreview N/A periodic Periodic changed
periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-compact-iso-no-registry-techpreview N/A periodic Ci-operator config 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.

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

🧹 Nitpick comments (1)
ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml (1)

2148-2160: 💤 Low value

Consider staggering the cron schedule to avoid potential resource contention on equinix-ocp-metal.

The new job e2e-agent-ha-dualstack-iso-no-registry-techpreview runs on the same schedule (0 */8 * * *) and cluster profile as e2e-agent-compact-iso-no-registry-techpreview, both triggering at 00:00, 08:00, and 16:00 UTC. If concurrent execution is not required, consider offsetting one to distribute load.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml`
around lines 2148 - 2160, The job
e2e-agent-ha-dualstack-iso-no-registry-techpreview is scheduled at the same cron
(0 */8 * * *) as e2e-agent-compact-iso-no-registry-techpreview causing potential
concurrent runs; update the cron value for one of these jobs (the cron field
under the job block) to an offset schedule (for example shift to 2 */8 * * * or
4 */8 * * *) to stagger execution on equinix-ocp-metal, then save the updated
cron string so the two jobs no longer run at the same UTC times.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In
`@ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml`:
- Around line 2148-2160: The job
e2e-agent-ha-dualstack-iso-no-registry-techpreview is scheduled at the same cron
(0 */8 * * *) as e2e-agent-compact-iso-no-registry-techpreview causing potential
concurrent runs; update the cron value for one of these jobs (the cron field
under the job block) to an offset schedule (for example shift to 2 */8 * * * or
4 */8 * * *) to stagger execution on equinix-ocp-metal, then save the updated
cron string so the two jobs no longer run at the same UTC times.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 53967671-cdd0-4b71-a474-5929a06b4202

📥 Commits

Reviewing files that changed from the base of the PR and between 6e6d3a8 and b234171.

⛔ 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-5.0.yaml

@bfournie
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 15, 2026
@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-ha-dualstack-iso-no-registry-techpreview

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-ha-dualstack-iso-no-registry-techpreview

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-ha-dualstack-iso-no-registry-techpreview

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

agent-gather is failing due to connectivity issue

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-agent-ha-dualstack-iso-no-registry-techpreview

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@pawanpinjarkar: 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 May 19, 2026
@andfasano
Copy link
Copy Markdown
Contributor

/approve

@andfasano
Copy link
Copy Markdown
Contributor

/approved

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/cc @smg247 please approve

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/assign @@smg247

@pawanpinjarkar
Copy link
Copy Markdown
Contributor Author

/assign @smg247

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

@pawanpinjarkar: GitHub didn't allow me to request PR reviews from the following users: approve, please.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @smg247 please approve

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.

@smg247
Copy link
Copy Markdown
Member

smg247 commented May 19, 2026

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, bfournie, pawanpinjarkar, smg247

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

openshift-ci Bot commented May 19, 2026

@pawanpinjarkar: 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 04fd8e6 into openshift:main May 19, 2026
18 checks passed
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. 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.

5 participants