Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1534178 - generating LiveOS/rootfs.img is failing due to size issues
Summary: generating LiveOS/rootfs.img is failing due to size issues
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lorax
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F28BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2018-01-13 21:01 UTC by Dennis Gilmore
Modified: 2018-02-08 18:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-08 18:04:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
logfile from running lorax (1.20 MB, text/plain)
2018-01-13 21:01 UTC, Dennis Gilmore 		no flags Details
View All

Description Dennis Gilmore 2018-01-13 21:01:53 UTC 
Created attachment 1380828 [details]
logfile from running lorax

Description of problem:
lorax is failing to create an install tree. The failure occurs when copying the files to the rootfs.img

Running... cp -a /var/tmp/lorax.p3_ylcsk/installtree/. /var/tmp/lorax.imgutils.lse0mvdk
cp: error writing '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/docker/docker-containerd-current': No space left on device
cp: error writing '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/docker/docker-containerd-shim-current': No space left on device
cp: error writing '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/docker/docker-ctr-current': No space left on device
cp: error writing '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/docker/docker-init-current': No space left on device
cp: error writing '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/docker/docker-proxy-current': No space left on device
cp: error writing '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/docker/docker-runc-current': No space left on device
cp: cannot create directory '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/coreutils': No space left on device
cp: cannot create directory '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/utempter': No space left on device
cp: cannot create directory '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/udisks2': No space left on device
cp: cannot create directory '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/anaconda': No space left on device
cp: cannot create directory '/var/tmp/lorax.imgutils.lse0mvdk/./usr/libexec/nfs-utils': No space left on device
cp: cannot create directory '/var/tmp/lorax.imgutils.lse0mvdk/./usr/src': No space left on device
Return code: 1

We need to figure out what extra things can be removed in runtime-cleanup.tmpl or we need to increate the size of the image.

This is occurring on all images on all arches, preventing the composition of all release blocking artifacts, so I am marking this bug as an accepted blocker bug for Fedora 28 Beta
Comment 1 Dennis Gilmore 2018-01-13 22:31:13 UTC 
after some digging it seems to be caused by a lulzbot-marlin-firmware pulling in a newer cura-lulzbot which pulls in a ton of new packages including the entire qt5 stack. 

runtime-install.tmpl contains 
    installpkg --optional *-firmware --except alsa* --except midisport-firmware \
                           --except crystalhd-firmware --except ivtv-firmware \
                           --except cx18-firmware --except iscan-firmware \
                           --except uhd-firmware --except lulzbot-marlin-firmware

it seems that --except is not working as expected.
Comment 2 Brian Lane 2018-01-15 16:14:05 UTC 
The --except only excludes it from the glob expansion of that command, it can still be pulled in by something else requiring it. Check the logs, they will hopefully provide more info on what actually pulled it in.
Comment 3 Brian Lane 2018-01-15 16:31:56 UTC 
Nevermind. I'm pretty sure commit 8edaefd4d1726eab668106ec7fd3f3c7a63fd92d broke excludes by expanding them to their NVR instead of just using names.
Comment 4 Brian Lane 2018-01-15 17:17:57 UTC 
This fixes it for me:
https://github.com/rhinstaller/lorax/pull/303
Comment 5 Dennis Gilmore 2018-01-18 16:17:16 UTC 
Brian as a FYI dnf provides no logs to tell you why a package was pulled in. That functionality has been lost with the move to dnf from yum. We have had bug #1303978 open for 2 years requesting the feature.
Comment 6 Adam Williamson 2018-02-08 18:04:09 UTC 
I believe this can be closed, as it was merged and built, and we got a successful compose as recently as 20180204. The bug(s) now blocking compose are different.
Note You need to log in before you can comment on or make changes to this bug.