I'm trying to build a live image from F19/Rawhide (basically the same thing ATM) for today's KDE Test Day, but it keeps failing, and I think the problem is Rawhide. The compose usually succeeds, but right after package install, I see these errors: E: dracut module 'dmsquash-live' cannot be found or installed. E: dracut module 'dmsquash-live' cannot be found or installed. then trying to boot the built image, it explodes messily very early in the boot process. There's a ton of errors, including a whole bunch of: systemd-udevd[XXX]: worker [XXX] did not accept message -1 (Connection refused), kill it and: Failed to mount moving /sysroot to /: Invalid argument Failed to switch root, ignoring: Invalid argument Notably, the 2013-03-10 nightly live desktop compose does not show these issues. It boots (hits a GDM problem, but boots much further at least), and the compose log - http://kojipkgs.fedoraproject.org//work/tasks/4225/5104225/mock_output.log - does not show the same error messages. That image was built with dracut-026-1.fc19.x86_64 , so either a bug showed up between 026-1 and 026-15.gitblahblah, or there's some difference between my build host and Koji that's causing this. Nominating as an Alpha blocker, but we shouldn't accept it as such until we confirm builders other than me (particularly the 'official' builders) hit it.
Seems like the composer should set "--no-hostonly" or in their config hostonly="no"
ah, I guessed that might be it. dunno why I didn't just try it, actually. sigh.
livecd-creator doesn't recreate the initrd. We didn't used to have to do this, what changed?
We've discussed on IRC, but the change was that upstream changed default to 'hostonly' on Fedora. 'hostonly' only includes drivers for the host system in the initramfs, which is obviously not what we want for a generic initramfs like that in the live images (or on the install images, for that matter, so we should check pungi/lorax.) should we set this back to livecd-tools? I think we agree the fix is in python-imgcreate, don't we?
ok, figured it out. dracut switched the default to hostonly so we now need to add this to the config file: - f.write('add_dracutmodules+=" dmsquash-live pollcdrom "') + f.write('add_dracutmodules+=" dmsquash-live pollcdrom "\n') + f.write('hostonly="no"\n') + f.write('dracut_rescue_image="no"\n')
Created attachment 710440 [details] Proposed patch I would even patch lorax, so that no config file can overwrite the behaviour.
We don't use lorax for live images. The livecd-creator and lorax cases are two separate bugs, please don't reassign this one. I believe Will already wrote a patch for lorax.
(In reply to comment #7) > We don't use lorax for live images. The livecd-creator and lorax cases are > two separate bugs, please don't reassign this one. I believe Will already > wrote a patch for lorax. ok, sorry...
We might be able to close this specific bug now? Though my last live compose still exploded on boot.
Adjusting topic to be clearer, and closing the bug, as I'm pretty sure it's fixed now.