Bug 255281

Summary:	rpm falsely reports successfull install on read-only /boot
Product:	[Fedora] Fedora	Reporter:	Dean Mander <knolderpoor>
Component:	yum	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7	CC:	james.antill, pmatilai, pnasrat, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-09-13 19:10:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dean Mander 2007-08-26 19:01:29 UTC

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):
kernel (all)

How reproducible:
always when kernel update available


Steps to Reproduce:
1. mount /boot as read-only
2. yum update kernel
3.
  
Actual results:
$ yum update kernel
<snip>
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: kernel                       ######################### [1/1]
error: unpacking of archive failed on file
/boot/System.map-2.6.22.4-65.fc7;46cfe671: cpio: open

Installed: kernel.x86_64 0:2.6.22.4-65.fc7
Complete!

Expected results:
I would expect the package to check if /boot is writable, 
if no, a transaction check error and a failure of the package update.

Additional info:

Comment 1 Jarod Wilson 2007-08-27 02:52:05 UTC

> 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?

Comment 2 Panu Matilainen 2007-08-27 17:27:25 UTC

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.

Comment 3 Jeremy Katz 2007-09-13 19:10:59 UTC


*** This bug has been marked as a duplicate of 186945 ***