[release-4.20] OCPBUGS-77896: Increase size of /var/ostreecontainer mount#10365
Conversation
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-cherrypick-robot: Jira Issue OCPBUGS-77551 has been cloned as Jira Issue OCPBUGS-77896. Will retitle bug to link to clone. DetailsIn response to this:
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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-77896, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
/retest |
|
@zaneb: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
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. |
|
/approve |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@openshift-cherrypick-robot: 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. |
|
/jira refresh |
|
@prb112: This pull request references Jira Issue OCPBUGS-77896, which is invalid:
Comment DetailsIn response to this:
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. |
|
/jira refresh |
|
@prb112: This pull request references Jira Issue OCPBUGS-77896, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
@kasturinarra let us know if you need the IBM QE team to verify. |
@prb112 hello, i am not very sure why my name was added as a QA Contact, i see bug in different version has been verified by Sajauddin Mohammad adding him |
|
@kasturinarra you were mentioned in #10365 (comment) @sajauddin is on the same team as I am. If you need verification from our team, we can work on it. |
|
@prb112 I think the QA contact in Jira is automatically assigned based on the Component (in this case SNO). But since the issue is platform-specific, it will need QE from your team (presumably @Hemali-Gujarathi4) to verify it. |
|
@zaneb no worries - didn't want to over step - thus the question to @kasturinarra |
|
This is an automated cherry-pick of #10346
/assign zaneb