Trying to apply an update image to anaconda-19.11 doesn't work, mount doesn't call /usr/bin/mount it calls an internal dracut function instead. rd.debug output: 3195 dracut-pre-pivot[505]: ///lib/dracut/hooks/pre-pivot/20-apply-live-updates.sh@3(source): '[' -b /dev/mapper/live-rw ']'^M^M 3196 dracut-pre-pivot[505]: ///lib/dracut/hooks/pre-pivot/20-apply-live-updates.sh@3(source): '[' -d /updates ']'^M^M 3197 dracut-pre-pivot[505]: ///lib/dracut/hooks/pre-pivot/20-apply-live-updates.sh@4(source): info 'Applying updates to live image...'^M^M 3198 dracut-pre-pivot[505]: //lib/dracut-lib.sh@426(info): echo 'Applying updates to live image...'^M^M 3199 dracut-pre-pivot[505]: ///lib/dracut/hooks/pre-pivot/20-apply-live-updates.sh@5(source): mount -o bind /run /sysroot/run^M^M 3200 dracut-mount[506]: //lib/dracut-lib.sh@352(): hookdir=/lib/dracut/hooks^M^M 3201 dracut-mount[506]: //lib/dracut-lib.sh@353(): export hookdir^M^M 3202 dracut-mount[506]: //lib/dracut-lib.sh@404(): '[' -z 1 ']'^M^M 3203 dracut-mount[506]: //lib/dracut-lib.sh@509(): command -v findmnt^M^M 3204 dracut-mount[506]: //lib/dracut-lib.sh@1035(): setmemdebug^M^M 3205 dracut-mount[506]: //lib/dracut-lib.sh@1030(setmemdebug): '[' -z 0 ']'^M^M 3206 dracut-mount[506]: /bin/dracut-mount@10(): source_conf /etc/conf.d^M^M This can be fixed by calling /usr/bin/mount explicitly, but that doesn't seem like the best solution -- people writing hooks are going to expect the path to be searched for binaries and won't always know what dracut is naming things.
Proposing as an Alpha blocker. New-style criterion: "The installer must be able to download and use an installer update image from an HTTP server."
(In reply to comment #0) > Trying to apply an update image to anaconda-19.11 doesn't work, mount > doesn't call /usr/bin/mount it calls an internal dracut function instead. > > rd.debug output: > > 3195 dracut-pre-pivot[505]: > ///lib/dracut/hooks/pre-pivot/20-apply-live-updates.sh@3(source): '[' -b > /dev/mapper/live-rw ']'^M^M > 3196 dracut-pre-pivot[505]: > ///lib/dracut/hooks/pre-pivot/20-apply-live-updates.sh@3(source): '[' -d > /updates ']'^M^M > 3197 dracut-pre-pivot[505]: > ///lib/dracut/hooks/pre-pivot/20-apply-live-updates.sh@4(source): info > 'Applying updates to live image...'^M^M > 3198 dracut-pre-pivot[505]: //lib/dracut-lib.sh@426(info): echo 'Applying > updates to live image...'^M^M > 3199 dracut-pre-pivot[505]: > ///lib/dracut/hooks/pre-pivot/20-apply-live-updates.sh@5(source): mount -o > bind /run /sysroot/run^M^M > 3200 dracut-mount[506]: //lib/dracut-lib.sh@352(): > hookdir=/lib/dracut/hooks^M^M > 3201 dracut-mount[506]: //lib/dracut-lib.sh@353(): export hookdir^M^M > 3202 dracut-mount[506]: //lib/dracut-lib.sh@404(): '[' -z 1 ']'^M^M > 3203 dracut-mount[506]: //lib/dracut-lib.sh@509(): command -v findmnt^M^M > 3204 dracut-mount[506]: //lib/dracut-lib.sh@1035(): setmemdebug^M^M > 3205 dracut-mount[506]: //lib/dracut-lib.sh@1030(setmemdebug): '[' -z 0 > ']'^M^M > 3206 dracut-mount[506]: /bin/dracut-mount@10(): source_conf /etc/conf.d^M^M > > > This can be fixed by calling /usr/bin/mount explicitly, but that doesn't > seem like the best solution -- people writing hooks are going to expect the > path to be searched for binaries and won't always know what dracut is naming > things. mount does not call dracut-mount. That is just the output of another dracut service. Although the ordering was wrong, which is hopefully fixed in dracut-026-62.git20130319 Please use the output of # journalctl -ab -o short-monotonic or better # journalctl -ab -o short-monotonic -u dracut-pre-pivot.service to debug individual service outputs.
Discussed at 2013-03-20 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.log.txt . Accepted as a blocker per criterion cited in comment #1.
The fixed dracut is in the f19 repos now and I saw people in #anaconda using updates images, closing.