Bug 361351 - i686 kernel released for i86_64 bug
i686 kernel released for i86_64 bug
Status: CLOSED NOTABUG
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Rel-Eng (Show other bugs)
rhn500
All Linux
low Severity low
: ---
: ---
Assigned To: Todd Sanders
Brandon Perkins
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-01 04:30 EDT by Fred New
Modified: 2010-06-15 17:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-15 17:24:36 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 Fred New 2007-11-01 04:30:32 EDT
Description of problem:  Advisory RHSA-2007:0937 fixes a bug against the i86_64
kernel, but there is also a corresponding i686 kernel issued.  According to the
way I read this advisory, it doesn't affect the i686 kernel, but RHN suggests
that I should upgrade from kernel(-smp)-2.4.21-51.EL.i686 to
kernel(-smp)-2.4.21-52.EL.i686 and reboot my systems for something that doesn't
affect me.

Version-Release number of selected component (if applicable):
"Red Hat Network release 5.0.3"

How reproducible: Always (It appeared on every i686 system I administer.)


Steps to Reproduce:
1. On an RHN-registered i686 system, upgrade to kernel(-smp)-2.4.21-51.EL.i686
2. 
3.
  
Actual results:  RHN reports that I need to upgrade to kernel-smp-2.4.21-52.EL.i686.


Expected results:  If it ain't broke, don't make me fix it.


Additional info:
Comment 1 Grant Gainey 2010-06-15 17:24:36 EDT
RHN can only report what the RHEL group defines - if the errata in question is defined to require the update, then that's what RHN and yum and up2date are going to say.

Closing as NOTABUG - I can't comment on whether this particular errata *really* needed to update all the systems it claimed were affected, though.

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