This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 88272 - up2date tries to update kernel that i already have
up2date tries to update kernel that i already have
Status: CLOSED DUPLICATE of bug 84757
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
4.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-08 10:45 EDT by Need Real Name
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:52:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2003-04-08 10:45:56 EDT
Description of problem:
every time up2date has reported that i have a problem, it says the kernel that i am running is one of the available updates.  it does not 
try to update it, and it does go away after updating packages, but i do not think it should be reporting that the kernel needs an update.

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

How reproducible:
1. run up2date when your machine needs updates
2. see that it is trying to update the kernel

Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:
Comment 1 Daniel Veillard 2003-04-08 12:11:11 EDT
Seems to be about up2date, not the rhn-applet-gui program,

Daniel
Comment 2 Tony Dunmore 2003-05-27 07:52:42 EDT
I suggest this is a dup of 84757 (and is rhn-applet-gui related, not up2date).
Comment 3 Adrian Likins 2004-09-02 15:02:17 EDT

*** This bug has been marked as a duplicate of 84757 ***
Comment 4 Red Hat Bugzilla 2006-02-21 13:52:34 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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