Red Hat Bugzilla – Bug 255281
rpm falsely reports successfull install on read-only /boot
Last modified: 2014-01-21 17:59:28 EST
Description of problem:
Request for more robust kernel .rpm file.
Today, an upgrade of the kernel-package on a system with read-only /boot
partition, renders the system unbootable.
You can successfully (according to yum) install the kernel package on such a
read-only /boot. It will update the grub.conf and next boot it won't find the
non-installed kernel (when using the default grub choice) --> can't startup.
Version-Release number of selected component (if applicable):
always when kernel update available
Steps to Reproduce:
1. mount /boot as read-only
2. yum update kernel
$ yum update kernel
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Installing: kernel ######################### [1/1]
error: unpacking of archive failed on file
/boot/System.map-188.8.131.52-65.fc7;46cfe671: cpio: open
Installed: kernel.x86_64 0:184.108.40.206-65.fc7
I would expect the package to check if /boot is writable,
if no, a transaction check error and a failure of the package update.
> You can successfully (according to yum)
That would suggest a yum bug, not a kernel bug.
> install the kernel package on such a
> read-only /boot. It will update the grub.conf and next boot it won't find the
> non-installed kernel (when using the default grub choice) --> can't startup.
Erm, grub.conf is on /boot so how would it have been updated if /boot was read-only?
This is a dupe of bug 186945 except that's against devel and this for F7 - yum
can catch this error if it wants to and IIRC yum 3.2.3 already does.
*** This bug has been marked as a duplicate of 186945 ***