Skip to content

[release-4.20] OCPBUGS-77896: Increase size of /var/ostreecontainer mount#10365

Open
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.20from
openshift-cherrypick-robot:cherry-pick-10346-to-release-4.20
Open

[release-4.20] OCPBUGS-77896: Increase size of /var/ostreecontainer mount#10365
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.20from
openshift-cherrypick-robot:cherry-pick-10346-to-release-4.20

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #10346

/assign zaneb

zaneb added 2 commits March 6, 2026 01:12
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).
@openshift-ci-robot
Copy link
Contributor

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

Details

In response to this:

This is an automated cherry-pick of #10346

/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.20] OCPBUGS-77551: Increase size of /var/ostreecontainer mount [release-4.20] OCPBUGS-77896: Increase size of /var/ostreecontainer mount Mar 6, 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 6, 2026
@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-77551 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 #10346

/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 requested review from jhixson74 and rwsu March 6, 2026 01:13
@zaneb
Copy link
Member

zaneb commented Mar 6, 2026

/retest
/cherry-pick release-4.19

@openshift-cherrypick-robot
Copy link
Author

@zaneb: once the present PR merges, I will cherry-pick it on top of release-4.19 in a new PR and assign it to you.

Details

In response to this:

/retest
/cherry-pick release-4.19

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.

@zaneb
Copy link
Member

zaneb commented Mar 6, 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 6, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 6, 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 6, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 6, 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.

@prb112
Copy link
Contributor

prb112 commented Mar 6, 2026

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@prb112: This pull request references Jira Issue OCPBUGS-77896, which is invalid:

  • expected dependent Jira Issue OCPBUGS-77551 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

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.

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants