Red Hat Bugzilla – Bug 67260
new-kernel-pkg does not check mkinitrd success
Last modified: 2007-04-18 12:43:27 EDT
Description of Problem:
new-kernel-pkg does not check mkinitrd success and may leave system unbootable
if mkinitrd fails.
Steps to Reproduce:
1. mount /tmp on /dev/shm
/dev/shm /tmp tmpfs bind 0 0
2. install (do not upgrade) new kernel
3. ls /boot to check if there is new initrd
no new initrd created because losetup fails on /dev/shm
new-kernel-pkg a least reports an error to user....
good point... new-kernel-pkg will no longer run grubby if mkinitrd returns
More potential problems, please comment.
Should mkinitrd query temporary filesystem type before it runs losetup on it?
Since mkinitrd always (?) runs as root would be more appropriate to use $HOME or
~ for temporary files if losetup on /tmp or /var/tmp fails?
Another question: What will happen if new-kernel-pkg will not run grubby but
user typed rpm -U kernel-x.x.x ? Will new-kernel-pkg tell rpm that upgrade
failed and old package can not be erased?