Skip to content

SUSTAINING-2248: cluster-capi-operator release-4.18: increase unit test memory limits#79696

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
rh-soboh:main
May 26, 2026
Merged

SUSTAINING-2248: cluster-capi-operator release-4.18: increase unit test memory limits#79696
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
rh-soboh:main

Conversation

@rh-soboh
Copy link
Copy Markdown
Contributor

@rh-soboh rh-soboh commented May 26, 2026

Summary

cc: @damdo

Summary by CodeRabbit

This PR updates the OpenShift CI configuration for the cluster-capi-operator release-4.18 pipeline (ci-operator config: ci-operator/config/openshift/cluster-capi-operator/openshift-cluster-capi-operator-release-4.18.yaml) to raise unit-test resources so tests no longer OOM when run with --race and --cover.

Practical changes:

  • Adds a unit-test-specific resource override for the unit job:
    • memory limit: 6 GiB
    • memory request: 3 GiB
    • CPU request: 1
  • This mirrors the same unit-test resource configuration already used on the 4.20 and 4.21 branches.

Rationale:

  • Unit tests began exiting with OOM (exit 137) after a grpc-go dependency bump (CVE-2026-33186) increased transitive dependency size, making the prior default 4 GiB limit insufficient when running with race/coverage flags.

Affected area:

  • openshift/release — CI configuration for the openshift/cluster-capi-operator release-4.18 job.

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

openshift-ci-robot commented May 26, 2026

@rh-soboh: This pull request references SUSTAINING-2248 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

cc: @damdo

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 26, 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: f508bbb4-7aff-4757-b0e8-03a2e10a47d9

📥 Commits

Reviewing files that changed from the base of the PR and between 5884852 and c8b9bf8.

📒 Files selected for processing (1)
  • ci-operator/config/openshift/cluster-capi-operator/openshift-cluster-capi-operator-release-4.18.yaml

Walkthrough

This PR updates the ci-operator config for cluster-capi-operator release 4.18, adding limits.memory: 6Gi to the unit test job while keeping existing requests (cpu: "1", memory: 3Gi).

Changes

CI Resource Configuration

Layer / File(s) Summary
Unit test resource limits
ci-operator/config/openshift/cluster-capi-operator/openshift-cluster-capi-operator-release-4.18.yaml
The unit test job gains explicit limits.memory: 6Gi while retaining requests with cpu: "1" and memory: 3Gi, establishing separate resource constraint boundaries for the unit test step.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

lgtm, approved, rehearsals-ack

Suggested reviewers

  • damdo
  • mdbooth
🚥 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 and specifically describes the main change: increasing unit test memory limits for cluster-capi-operator release-4.18, which is exactly what the changeset accomplishes.
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 No Ginkgo test code was modified in this PR; only CI configuration YAML was updated. The custom check does not apply to non-test code.
Test Structure And Quality ✅ Passed PR modifies CI pipeline configuration files only; custom check targets Ginkgo test code quality, which is not present in this PR.
Microshift Test Compatibility ✅ Passed PR modifies only CI job configuration (YAML resource limits), not Ginkgo test code. Custom check applies to new Ginkgo e2e tests only; no tests are added here.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only modifies CI pipeline resource configuration (YAML) for existing unit tests; no new Ginkgo e2e tests are added, so SNO compatibility check does not apply.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies CI configuration only, not deployment manifests or operator code. No topology-aware scheduling constraints introduced.
Ote Binary Stdout Contract ✅ Passed PR only modifies YAML CI configuration for resource limits; OTE Binary Stdout Contract check applies to executable code, not declarative configuration files.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR modifies only CI configuration (YAML) to increase memory limits for existing unit tests. No new Ginkgo e2e tests are added; custom check applies only to new test code.

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

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@rh-soboh
Copy link
Copy Markdown
Contributor Author

/ok-to-test

@openshift-ci openshift-ci Bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label May 26, 2026
@openshift-ci openshift-ci Bot requested review from mdbooth and racheljpg May 26, 2026 09:52
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.

Actionable comments posted: 1

🤖 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.

Inline comments:
In
`@ci-operator/config/openshift/cluster-capi-operator/openshift-cluster-capi-operator-release-4.18.yaml`:
- Around line 48-53: You modified the CI config resource for the CAPI operator
(the unit: limits/requests block in
openshift-cluster-capi-operator-release-4.18.yaml); run the downstream
regeneration by executing "make update" in the repo, capture and commit any
generated changes, and include the resulting generated diff in the PR (or
explicitly state that running "make update" produced no-op) so reviewers can
verify downstream artifacts were updated.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 3fdbdf01-5cd0-41ee-b3d6-562a3f14f36e

📥 Commits

Reviewing files that changed from the base of the PR and between 9ddde9d and 5884852.

📒 Files selected for processing (1)
  • ci-operator/config/openshift/cluster-capi-operator/openshift-cluster-capi-operator-release-4.18.yaml

…The grpc-go CVE-2026-33186 bump in PR openshift#566 increased transitive dependency size, causing unit tests to OOMKill (exit 137) under the default 4Gi memory limit with --race and --cover flags. Adds a unit-specific resource override (6Gi limit, 3Gi request, 1 CPU) matching the 4.20/4.21 branch configuration.
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@rh-soboh: 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
pull-ci-openshift-cluster-capi-operator-release-4.18-build openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-aws-capi-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-aws-ovn openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-aws-ovn-serial openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-aws-ovn-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-azure-capi-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-azure-ovn-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-gcp-capi-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-gcp-ovn-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-metal3-capi-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-openstack-capi-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-openstack-ovn-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-vsphere-capi-techpreview openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-images openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-lint openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-regression-clusterinfra-aws-ipi-techpreview-capi openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-security openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-unit openshift/cluster-capi-operator presubmit Ci-operator config changed
pull-ci-openshift-cluster-capi-operator-release-4.18-vendor openshift/cluster-capi-operator presubmit Ci-operator config changed
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
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 26, 2026
@damdo
Copy link
Copy Markdown
Member

damdo commented May 26, 2026

/pj-rehearse pull-ci-openshift-cluster-capi-operator-release-4.18-unit

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@damdo: 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 26, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo, rh-soboh

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

openshift-ci Bot commented May 26, 2026

@rh-soboh: 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.

@damdo
Copy link
Copy Markdown
Member

damdo commented May 26, 2026

/pj-rehearse ack

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@damdo: 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 26, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit d50e70d into openshift:main May 26, 2026
15 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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants