Bug 98157 - up2date crash leaving box in inconsistent state
up2date crash leaving box in inconsistent state
Status: CLOSED WORKSFORME
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
4.0
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Adrian Likins
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-06-26 23:28 EDT by Rob Gerth
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-04 14:38:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rob Gerth 2003-06-26 23:28:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
Ran up2date on a vanilla RH9 box. Download/repackaging ok, but when trying to 
update glibc, up2date got into a fatal error as it couldn't access (locked?) 
original glibc.
End result is an inoperable box due to version conflicts (specifically 
with /lib/i686/lptreadths...).

Dunno what else to tell you: I was using the graphical up2date under
kde; nothing 'else' running.

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


How reproducible:
Didn't try :-)


Expected Results:  Unless the box crashes, up2date should never ever leave the 
OS in an
inconsistent state. Seems that up2date blindly starts updating packages 
without checking it can follow through. Especially essential for core packages 
such as glibc and friends

Additional info:

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