Red Hat Bugzilla – Bug 851362
anaconda-generator fails to source in dracut-lib.sh, missing from /run/initramfs/
Last modified: 2013-01-09 22:36:08 EST
anaconda-generator runs after the pivot, but uses some dracut functionality. It tries to source in /run/initramfs/usr/lib/dracut-lib.sh but that doesn't exist, so the call to getargbool fails.
Not sure why that part of the initramfs went away, maybe cleanup for memory.
This bug manifests itself in no longer being able to cause the ssh server to start.
Ah hah. It's the anaconda-cleanup-initramfs service that does it.
mkdir -p /boot
find /run/initramfs/usr | cpio -co 2>/dev/null | $gzip -c > $initramfs
rm -rf /run/initramfs/usr
Maybe if we run this service /after/ the generator?
Incorrect assumption. The clean up script doesn't whack it, the file doesn't exist in the first place. Dracut images are no longer being ran with a --prefix, so all the content is directly in /, so there is nothing for anaconda to find in /run/initramfs/ any more.
Not sure what is going to need to be changed here to make this work again.
In F17 we ran dracut with '--prefix /run/initramfs' to make the initramfs available after switch_root. This is disallowed by dracut in F18.
So: is there a way to make the initramfs available after switch-root in F18 dracut? Or should we move anything that we want to persist after switch-root to /run/initramfs/state? Or some other location?
(In reply to comment #3)
> In F17 we ran dracut with '--prefix /run/initramfs' to make the initramfs
> available after switch_root. This is disallowed by dracut in F18.
> So: is there a way to make the initramfs available after switch-root in F18
> dracut? Or should we move anything that we want to persist after switch-root
> to /run/initramfs/state? Or some other location?
Do you need the initramfs version? Or can you just install the dracut package in the anaconda image and have /usr/lib/dracut/... ?
Of course you can still copy files to /run/initramfs as you need them.
We decided to add the dracut-lib.sh file back into stage2 and make use of it from there. Lorax and anaconda patches sent.
lorax-18.18-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lorax-18.18-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
[anaconda root@sharpie /]# ls /run/initramfs/usr/lib/dracut-lib.sh
ls: cannot access /run/initramfs/usr/lib/dracut-lib.sh: No such file or directory
(In reply to comment #8)
> [anaconda root@sharpie /]# ls /run/initramfs/usr/lib/dracut-lib.sh
> ls: cannot access /run/initramfs/usr/lib/dracut-lib.sh: No such file or
The lorax update has to go with an anaconda update to use it from the new location. That's on master, so it'll be post-alpha for this issue to be fixed.
Use of an updates.img containing commit e8ff240f953963a8b6cbc2d0c54a5b7b1493c29f from master should work though.
[root@bluebill anaconda]# git cherry-pick e8ff240f953963a8b6cbc2d0c54a5b7b1493c29f
[detached HEAD 5771646] Use the real path to dracut-lib.sh (#851362)
Author: Jesse Keating <firstname.lastname@example.org>
1 file changed, 1 insertion(+), 1 deletion(-)
[root@bluebill anaconda]# make updates && scp updates.img email@example.com:/var/www/html/updates-newui.img
Using tag: anaconda-18.6.6-1
boot: linux vnc ip=220.127.116.11::18.104.22.168:255.255.255.0:sharpie.rchland.ibm.com:eth0:none ip=22.214.171.124::126.96.36.199:255.255.255.0::eth1:none nameserver=188.8.131.52 bootdev=eth0 sshd=1 live.updates=http://chukar.rchland.ibm.com/updates-newui.img
[hamzy@hamzy-tp-w510 ~]$ ssh firstname.lastname@example.org
ssh: connect to host sharpie.rchland.ibm.com port 22: Connection refused
Hrm, can you run /updates/lib/systemd/system-generators/anaconda-generator (with sh -x) and post the output here?
It should be looking for /usr/lib/dracut/modules.d/99base/dracut-lib.sh
Never mind, I ran this myself. The lorax version needed to make this work is still in updates-testing. I'm not sure if it was used to create RC2 or not. Probably not as this isn't a blocker bug.
lorax-18.19-1.fc18 has been submitted as an update for Fedora 18.
lorax-18.20-1.fc18 has been submitted as an update for Fedora 18.