Bug 157221 - yum scriptlet failed
yum scriptlet failed
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2005-05-09 11:34 EDT by Doug Henderson
Modified: 2014-01-21 17:52 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-26 22:55:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Doug Henderson 2005-05-09 11:34:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Description of problem:
running kernel-2.6.11-1.1286_FC4 and ignoring the presence of some selinux message during reboot.

Here are the last few lines of the yum update output:

Downloading Packages:
(1/1): kernel-2.6.11-1.12 100% |=========================|  14 MB    00:51
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
error: %pre(kernel-2.6.11-1.1287_FC4.i686) scriptlet failed, exit status 255
error:   install: %pre scriptlet failed (2), skipping kernel-2.6.11-1.1287_FC4

Installed: kernel.i686 0:2.6.11-1.1287_FC4

It last two messages suggest success, however the 1287 kernel is not installed.

I rebooted, adding selinux=0 to boot parameters, and the yum update really successfully installed kernel-2.6.11-1.1287_FC4

I think there are two errors here. One with yum - for reporting success when it in fact failed. The other with selinux. This bug report is for yum.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. boot kernel-2.6.11-1.1286_FC4
2. yum remove kernel-2.6.11-1.1287_FC4
3. yum update

Additional info:
Comment 1 Seth Vidal 2005-05-09 13:28:26 EDT
rpm/selinux bug - not yum.

Comment 2 Doug Henderson 2005-05-24 19:13:54 EDT
This problem has not occured with FC4test3.

I suspect this problem is no longer reproducable. I have no objection to seeing
it closed on that account.

Comment 3 John Hodrien 2005-07-08 06:42:44 EDT
Sadly I've just had this problem on an FC4 final box during a full update a week
ago.  Having tracked it down to this bug.  It was completely repeatable. 
Disabled selinux and all was well.  Did a full upgrade to today's packages,
restarted with selinux enabled and I can't repeat it anymore...
Comment 4 Jeff Johnson 2005-08-26 22:55:03 EDT
This problem appears unreproducible, and related to selinux behavior. Reopen and assign to selinux if you 
want it fixed.

Note You need to log in before you can comment on or make changes to this bug.