openshift/openstack-test: bump memory limit#78978
Conversation
|
@mandre, Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (15)
✅ Files skipped from review due to trivial changes (15)
WalkthroughThis PR updates OpenShift CI operator configs for the openstack-test pipelines, raising the wildcard ChangesMemory Resource Limit Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 12✅ Passed checks (12 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
From 4Gi to 8Gi to fix OOM during Go compilation, as seen in recent promotion jobs at [1] and [2]. [1] https://prow.ci.openshift.org/view/gs/test-platform-results/logs/branch-ci-openshift-openstack-test-main-images/2049105686775730176 [2] https://prow.ci.openshift.org/view/gs/test-platform-results/logs/branch-ci-openshift-openstack-test-release-4.21-images/2051201632682643456
cf278c6 to
170b8c0
Compare
|
[REHEARSALNOTIFIER]
A total of 96 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-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@mandre: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/pj-rehearse pull-ci-openshift-openstack-test-release-4.21-images |
|
@mandre: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mandre, stephenfin The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/pj-rehearse ack |
|
@mandre: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
From 4Gi to 8Gi to fix OOM during Go compilation, as seen in recent promotion jobs at [1] and [2].
[1] https://prow.ci.openshift.org/view/gs/test-platform-results/logs/branch-ci-openshift-openstack-test-main-images/2049105686775730176
[2] https://prow.ci.openshift.org/view/gs/test-platform-results/logs/branch-ci-openshift-openstack-test-release-4.21-images/2051201632682643456
Summary
This PR increases the memory limits used by the OpenShift CI jobs that run for the openshift/openstack-test repository: the wildcard container memory limit (
resources['*'].limits.memory) is changed from 4Gi to 8Gi across main and the release branches listed below. The change is intended to address out-of-memory (OOM) failures observed during Go compilation in recent promotion job runs (see referenced failing logs in the PR description).What changed in practical terms
'*') resource selector applies, instead of the previous 4Gi.Files / branches affected
Memory limits were increased in the ci-operator config for:
(All changes are the same: resources['*'].limits.memory: 4Gi → 8Gi.)
Impact