Skip to content

NO-ISSUE: remove periodic jobs from release-ocm-2.11#81422

Draft
andrej1991 wants to merge 1 commit into
openshift:mainfrom
andrej1991:remove-release-ocm-2.11-periodics
Draft

NO-ISSUE: remove periodic jobs from release-ocm-2.11#81422
andrej1991 wants to merge 1 commit into
openshift:mainfrom
andrej1991:remove-release-ocm-2.11-periodics

Conversation

@andrej1991

@andrej1991 andrej1991 commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

on release-ocm-2.11 only CVE fixes are happening.

Summary by CodeRabbit

This PR trims periodic CI coverage from the release-ocm-2.11 OpenShift CI configuration, reflecting that this branch is intended to receive only CVE-related fixes.

Practically, it removes several cron-driven jobs from the assisted-installer-agent, assisted-service, and assisted-test-infra pipelines, and in a few cases replaces them with non-periodic or optional equivalents so the relevant checks can still run without scheduled maintenance load. This reduces recurring CI usage while keeping the important validation paths available for release-ocm-2.11.

on release-ocm-2.11 only CVE fixes are happening.
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@andrej1991: This pull request explicitly references no jira issue.

Details

In response to this:

on release-ocm-2.11 only CVE fixes are happening.

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 2, 2026
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 2, 2026
@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai

coderabbitai Bot commented Jul 2, 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: 1b32f964-1916-49d5-987b-881bba759834

📥 Commits

Reviewing files that changed from the base of the PR and between 6d12dd2 and 6137f82.

📒 Files selected for processing (3)
  • ci-operator/config/openshift/assisted-installer-agent/openshift-assisted-installer-agent-release-ocm-2.11.yaml
  • ci-operator/config/openshift/assisted-service/openshift-assisted-service-release-ocm-2.11.yaml
  • ci-operator/config/openshift/assisted-test-infra/openshift-assisted-test-infra-release-ocm-2.11.yaml
💤 Files with no reviewable changes (3)
  • ci-operator/config/openshift/assisted-test-infra/openshift-assisted-test-infra-release-ocm-2.11.yaml
  • ci-operator/config/openshift/assisted-installer-agent/openshift-assisted-installer-agent-release-ocm-2.11.yaml
  • ci-operator/config/openshift/assisted-service/openshift-assisted-service-release-ocm-2.11.yaml

Walkthrough

This PR removes cron-based periodic job definitions from three CI configuration files for openshift-assisted release-ocm-2.11 pipelines (installer-agent, service, test-infra), and replaces two test-infra periodic HA kube-api jobs with non-periodic/optional variants retaining the same environment settings.

Changes

Periodic CI Job Cleanup

Layer / File(s) Summary
Installer-agent subsystem test cleanup
ci-operator/config/openshift/assisted-installer-agent/openshift-assisted-installer-agent-release-ocm-2.11.yaml
Adds steps (cluster_profile, workflow) to subsystem-test and removes the cron-scheduled subsystem-test-periodic job.
Assisted-service periodic ZTP/CAPI job removal
ci-operator/config/openshift/assisted-service/openshift-assisted-service-release-ocm-2.11.yaml
Removes cron-based periodic variants of subsystem-aws, multiple e2e-ai-operator-ztp scenarios, CAPI, disconnected-CAPI, and remove-node jobs, keeping only non-periodic counterparts.
Test-infra HA kube-api job replacement
ci-operator/config/openshift/assisted-test-infra/openshift-assisted-test-infra-release-ocm-2.11.yaml
Replaces periodic IPv4/IPv6 HA kube-api metal jobs with non-periodic (IPv4, with skip_if_only_changed) and optional (IPv6) job variants, removing cron schedule and CLUSTERTYPE.

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

🚥 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 main change: removing periodic jobs from release-ocm-2.11.
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 only edits ci-operator YAML; no Ginkgo It/Describe/Context/When titles were added or modified, so there are no unstable test names.
Test Structure And Quality ✅ Passed This PR only edits ci-operator YAML job definitions; no Ginkgo test code, assertions, or waits were changed, so the test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests were added; the patch only removes periodic CI job definitions and adjusts YAML job wiring.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only deletes periodic CI YAML jobs; no new Ginkgo tests or SNO-sensitive test code were added.
Topology-Aware Scheduling Compatibility ✅ Passed Only ci-operator test configs changed; no deployment manifests, operator code, or topology-related scheduling fields were introduced.
Ote Binary Stdout Contract ✅ Passed Only ci-operator YAML job configs changed; no OTE binary or TestMain/init/suite setup code was touched, so stdout contract risk is absent.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR only edits CI job YAML; no new Ginkgo test code was added, and the IPv6 job already uses IPv6-only assisted configs with no public internet dependency.
No-Weak-Crypto ✅ Passed Touched CI YAMLs only add/remove job definitions; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons found.
Container-Privileges ✅ Passed The changed ci-operator YAMLs only adjust test scheduling; they contain no privileged, hostPID/hostNetwork/hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root settings.
No-Sensitive-Data-In-Logs ✅ Passed The PR only reworks/removes CI job definitions; no new logging or secret/PII-bearing output was added in the touched YAML.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: andrej1991
Once this PR has been reviewed and has the lgtm label, please assign yoavsc0302 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 openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 2, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@andrej1991: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants