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
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.
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.
Nevermind. I'm pretty sure commit 8edaefd4d1726eab668106ec7fd3f3c7a63fd92d broke excludes by expanding them to their NVR instead of just using names.
This fixes it for me: https://github.com/rhinstaller/lorax/pull/303
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.
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.