RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1815139 - fuse-overlayfs: could not find file with easybuild
Summary: fuse-overlayfs: could not find file with easybuild
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: fuse-overlayfs
Version: 8.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: David Darrah/Red Hat QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-19 15:12 UTC by Alex Jia
Modified: 2020-04-08 10:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-08 10:42:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alex Jia 2020-03-19 15:12:50 UTC
Description of problem:
To build and run container images in rootless environment w/ the following guideline.

please see https://bugzilla.redhat.com/show_bug.cgi?id=1804849#c0

Version-Release number of selected component (if applicable):
fuse-overlayfs-0.7.2-4.module+el8.2.0+5949+6277b64f.x86_64
podman-1.6.4-9.module+el8.2.0+5952+e75b58bb.x86_64

How reproducible:
always

Steps to Reproduce:
1. https://bugzilla.redhat.com/show_bug.cgi?id=1804849#c0

Actual results:

[ajia@hp-dl360g9-03 test]$ podman run --log-level=debug ohpc-gnu9-easybuild:1.9.9 'eb --robot lz4-1.9.2-GCCcore-8.3.0.eb'
DEBU[0000] Reading configuration file "/home/ajia/.config/containers/libpod.conf" 
DEBU[0000] Merged system config "/home/ajia/.config/containers/libpod.conf": &{{false false false true true true} 0 {   [] [] []} /home/ajia/.local/share/containers/storage/volumes docker://  runc map[crun:[/usr/bin/crun /usr/local/bin/crun] runc:[/usr/bin/runc /usr/sbin/runc /usr/local/bin/runc /usr/local/sbin/runc /sbin/runc /bin/runc /usr/lib/cri-o-runc/sbin/runc /run/current-system/sw/bin/runc]] [crun runc] [crun] [] [/usr/libexec/podman/conmon /usr/local/libexec/podman/conmon /usr/local/lib/podman/conmon /usr/bin/conmon /usr/sbin/conmon /usr/local/bin/conmon /usr/local/sbin/conmon /run/current-system/sw/bin/conmon] [PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin] cgroupfs  /home/ajia/.local/share/containers/storage/libpod /run/user/1001/libpod/tmp -1 false /etc/cni/net.d/ [/usr/libexec/cni /usr/lib/cni /usr/local/lib/cni /opt/cni/bin]  []   k8s.gcr.io/pause:3.1 /pause true true  2048 shm journald  ctrl-p,ctrl-q false} 
DEBU[0000] Using conmon: "/usr/bin/conmon"              
DEBU[0000] Initializing boltdb state at /home/ajia/.local/share/containers/storage/libpod/bolt_state.db 
DEBU[0000] Using graph driver overlay                   
DEBU[0000] Using graph root /home/ajia/.local/share/containers/storage 

...ignore...

DEBU[0000] running conmon: /usr/bin/conmon               args="[--api-version 1 -c d42ee40ba0aa1650517e64ff9545cd92fcf5c28f7ca68506c0a0b2279acd9e87 -u d42ee40ba0aa1650517e64ff9545cd92fcf5c28f7ca68506c0a0b2279acd9e87 -r /usr/bin/runc -b /home/ajia/.local/share/containers/storage/overlay-containers/d42ee40ba0aa1650517e64ff9545cd92fcf5c28f7ca68506c0a0b2279acd9e87/userdata -p /run/user/1001/overlay-containers/d42ee40ba0aa1650517e64ff9545cd92fcf5c28f7ca68506c0a0b2279acd9e87/userdata/pidfile -l k8s-file:/home/ajia/.local/share/containers/storage/overlay-containers/d42ee40ba0aa1650517e64ff9545cd92fcf5c28f7ca68506c0a0b2279acd9e87/userdata/ctr.log --exit-dir /run/user/1001/libpod/tmp/exits --socket-dir-path /run/user/1001/libpod/tmp/socket --log-level debug --syslog --conmon-pidfile /run/user/1001/overlay-containers/d42ee40ba0aa1650517e64ff9545cd92fcf5c28f7ca68506c0a0b2279acd9e87/userdata/conmon.pid --exit-command /usr/bin/podman --exit-command-arg --root --exit-command-arg /home/ajia/.local/share/containers/storage --exit-command-arg --runroot --exit-command-arg /run/user/1001 --exit-command-arg --log-level --exit-command-arg debug --exit-command-arg --cgroup-manager --exit-command-arg cgroupfs --exit-command-arg --tmpdir --exit-command-arg /run/user/1001/libpod/tmp --exit-command-arg --runtime --exit-command-arg runc --exit-command-arg --storage-driver --exit-command-arg overlay --exit-command-arg --storage-opt --exit-command-arg overlay.mount_program=/usr/bin/fuse-overlayfs --exit-command-arg --events-backend --exit-command-arg journald --exit-command-arg container --exit-command-arg cleanup --exit-command-arg d42ee40ba0aa1650517e64ff9545cd92fcf5c28f7ca68506c0a0b2279acd9e87]"
[conmon:d]: failed to write to /proc/self/oom_score_adj: Permission denied

...ignore...

DEBU[0000] Started container d42ee40ba0aa1650517e64ff9545cd92fcf5c28f7ca68506c0a0b2279acd9e87 
DEBU[0000] Enabling signal proxying                     
ERROR: Build of /opt/ohpc/pub/libs/easybuild/4.1.1/software/EasyBuild/4.1.1/easybuild/easyconfigs/f/flex/flex-2.6.4.eb failed (err: "build failed (first 300 chars): Couldn't find file flex-2.6.4.tar.gz anywhere, and downloading it didn't work either... Paths attempted (in order): /opt/ohpc/pub/libs/easybuild/4.1.1/software/EasyBuild/4.1.1/easybuild/easyconfigs/f/flex/f/flex/flex-2.6.4.tar.gz, /opt/ohpc/pub/libs/easybuild/4.1.1/software/EasyBuild/4.1.1/easybuild")
== temporary log file in case of crash /tmp/eb-f33qzi1_/easybuild-y9_n9ub1.log
== resolving dependencies ...
== processing EasyBuild easyconfig /opt/ohpc/pub/libs/easybuild/4.1.1/software/EasyBuild/4.1.1/easybuild/easyconfigs/m/M4/M4-1.4.18.eb
== building and installing M4/1.4.18...

...ignore...

== building and installing flex/2.6.4...
== fetching files...
== FAILED: Installation ended unsuccessfully (build directory: /home/openhpc/.local/easybuild/build/flex/2.6.4/system-system): build failed (first 300 chars): Couldn't find file flex-2.6.4.tar.gz anywhere, and downloading it didn't work either... Paths attempted (in order): /opt/ohpc/pub/libs/easybuild/4.1.1/software/EasyBuild/4.1.1/easybuild/easyconfigs/f/flex/f/flex/flex-2.6.4.tar.gz, /opt/ohpc/pub/libs/easybuild/4.1.1/software/EasyBuild/4.1.1/easybuild (took 30 sec)
== Results of the build can be found in the log file(s) /tmp/eb-f33qzi1_/easybuild-flex-2.6.4-20200319.143638.laQZS.log



Expected results:


Additional info:

Comment 3 Tom Sweeney 2020-03-19 19:52:04 UTC
Assigning to Jindrich to handle packaging.


Note You need to log in before you can comment on or make changes to this bug.