Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1787506

Summary: "s2i build with a quota Building from a template" test is failing with wrong MEMORYSWAP value
Product: OpenShift Container Platform Reporter: wewang <wewang>
Component: BuildAssignee: Adam Kaplan <adam.kaplan>
Status: CLOSED WONTFIX QA Contact: wewang <wewang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, cewong, eparis, wzheng
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-03 21:56:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 wewang 2020-01-03 07:09:57 UTC
Related issues: https://github.com/containers/buildah/issues/1213

Comment 4 Adam Kaplan 2020-02-03 21:56:35 UTC
Per [1], I don't think restoring MEMORYSWAP settings will happen any time soon. My understanding is that this feature made sense when we used Docker, but is obsolete since we've moved to use buildah:

> The OpenShift builder uses buildah's chroot isolation, which doesn't implement setting control group settings.
> 
> Because the builder is run in a container, and the we can count on that container having its memory.limit_in_bytes limit set on its behalf by the runtime (CRI-O), so we don't have to do anything for that limit, and a couple of others.

@Cesar the issues you reported seem unrelated to this BZ - tests are failing because the binary source is timing out uploading to the build pod.

[1] https://github.com/containers/buildah/issues/1213#issuecomment-571277448