time="2019-11-08T17:35:19Z" level=warning msg="pkg/chroot: error unmounting \"/tmp/buildah790569738/mnt/rootfs\": error checking if \"/tmp/buildah790569738/mnt/rootfs/sys/fs/cgroup/hugetlb\" is mounted: no such file or directory"
time="2019-11-08T17:35:19Z" level=warning msg="pkg/bind: error unmounting \"/tmp/buildah790569738/mnt/rootfs\": error checking if \"/tmp/buildah790569738/mnt/rootfs/sys/fs/cgroup/hugetlb\" is mounted: no such file or directory"
This is coming up very often in output of builds, it appears to be a race condition or always happening, and fills up logs.
Needs to be fixed because it makes builds look like they are broken.
[Feature:Builds][Conformance] build can reference a cluster service with a build being created from new-build should be able to run a build that references a cluster service [Suite:openshift/conformance/parallel/minima
(In reply to Tom Sweeney from comment #2)
> Nalin wasn't this in another BZ that you've been working? Any updates?
It looks like we can actually skip a lot of the work that we were trying to do here (and by doing so, avoiding the errors we encountered while trying to do it). buildah #1996 has a proposed fix.
I'm going to put this back to assign. The PR with the fix is not yet passing tests (https://github.com/containers/buildah/pull/1996). Once merged we can close this out.
buildah is now updated to buildah-1.11.6-2.el8 + PR 1996 to fix this.
Pretty sure we need to vendor this into openshift/builder, which uses buildah as a library, to have this take effect there.
Moving this to builds, will be the "master" 4.4 issue. Will clone for 4.3 - note that given where we are in the release process this may be released in a z-stream.
Checked version as below, which include the pr, no Unmount error info
Jobs for: [Feature:Builds][Conformance] build can reference a cluster service with a build being created from new-build should be able to run a build that references a cluster service [Suite:openshift/conformance/parallel/minima
*** Bug 1755670 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.