Skip to content

[release-4.19] OCPBUGS-79503: Increase size of /var/ostreecontainer mount#10433

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-10365-to-release-4.19
Apr 1, 2026
Merged

[release-4.19] OCPBUGS-79503: Increase size of /var/ostreecontainer mount#10433
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-10365-to-release-4.19

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #10365

/assign zaneb

zaneb added 2 commits March 25, 2026 05:26
Evidently on PPC64LE we need about 200MiB more space than a 4GiB volume
can contain, despite the image we're pulling being only about 1.4GB.
It's not clear why the system repo is (presumably) taking up so much
space, but a 5GiB volume should be enough to contain it.

Since a tmpfs only allocates RAM for space that is actually used, it
should be safe to increase the allocation. If this causes us to actually
run out of RAM, we will encounter that problem later (it may, however,
be more difficult to debug).
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 25, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b6d0d051-7627-451a-b99a-b9fa8f4579e3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ 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 openshift-ci bot requested review from pawanpinjarkar and rwsu March 25, 2026 05:27
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-77896 has been cloned as Jira Issue OCPBUGS-79503. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-79503: Increase size of /var/ostreecontainer mount

Details

In response to this:

This is an automated cherry-pick of #10365

/assign zaneb

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 changed the title [release-4.19] OCPBUGS-77896: Increase size of /var/ostreecontainer mount [release-4.19] OCPBUGS-79503: Increase size of /var/ostreecontainer mount Mar 25, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 25, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-79503, which is invalid:

  • expected dependent Jira Issue OCPBUGS-77896 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #10365

/assign zaneb

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.

@zaneb
Copy link
Copy Markdown
Member

zaneb commented Mar 25, 2026

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 25, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 25, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zaneb

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 Mar 25, 2026
@zaneb
Copy link
Copy Markdown
Member

zaneb commented Mar 30, 2026

/cc @prb112

@openshift-ci openshift-ci bot requested a review from prb112 March 30, 2026 01:10
@prb112
Copy link
Copy Markdown
Contributor

prb112 commented Mar 30, 2026

Thanks @zaneb we're still working on it.

@prb112
Copy link
Copy Markdown
Contributor

prb112 commented Mar 30, 2026

/verified by @Hemali-Gujarathi4
/lgtm

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 30, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@prb112: This PR has been marked as verified by @Hemali-Gujarathi4.

Details

In response to this:

/verified by @Hemali-Gujarathi4
/lgtm

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 added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2026
@prb112
Copy link
Copy Markdown
Contributor

prb112 commented Mar 30, 2026

Hey @zaneb we're good to go. Thank you, Paul

@prb112
Copy link
Copy Markdown
Contributor

prb112 commented Mar 30, 2026

/jira-refresh

@zaneb
Copy link
Copy Markdown
Member

zaneb commented Mar 30, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 30, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@zaneb: This pull request references Jira Issue OCPBUGS-79503, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-77896 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-77896 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
  • bug has dependents

Requesting review from QA contact:
/cc @kasturinarra

Details

In response to this:

/jira refresh

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 a review from kasturinarra March 30, 2026 21:43
@prb112
Copy link
Copy Markdown
Contributor

prb112 commented Mar 30, 2026

/retest-required

1 similar comment
@zaneb
Copy link
Copy Markdown
Member

zaneb commented Mar 31, 2026

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD ff27b7f and 2 for PR HEAD f04062a in total

@prb112
Copy link
Copy Markdown
Contributor

prb112 commented Apr 1, 2026

/retest-required

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 1, 2026

@openshift-cherrypick-robot: 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 9cdc313 into openshift:release-4.19 Apr 1, 2026
15 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-79503
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-79503 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #10365

/assign zaneb

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants