Bug 165730 - current disklessrc cannot be used to boot 2.6.9-12.2.EL kernel
Summary: current disklessrc cannot be used to boot 2.6.9-12.2.EL kernel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: system-config-netboot
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jason Vas Dias
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 156322 165784
TreeView+ depends on / blocked
 
Reported: 2005-08-11 16:34 UTC by Jason Vas Dias
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version: RHBA-2005-484
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-10-05 13:49:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:484 0 qe-ready SHIPPED_LIVE Updated system-config-netboot package 2005-10-05 04:00:00 UTC

Description Jason Vas Dias 2005-08-11 16:34:58 UTC
Description of problem:

disklessrc had always brought up the boot interface (eg. eth0) and
did a 'host' lookup before bringing up the loopback device.

The 'host' lookup could cause the ipv6 module to be loaded before
the loopback device is brought up which causes kernel-2.6.9-12.2.EL
(the current RHEL-4-U2 kernel) to get an Oops and panic ( bug 165669 ).

The workaround is to bring up the loopback device before the boot interface.


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

All system-config-netboot versions prior to 0.1.26-1_EL4 with 
kernel-2.6.9-12.2-EL 

How reproducible:
100% 

Steps to Reproduce:
Use system-config-netboot to create a diskless client with kernel-2.6.9-12.2-EL 
  
Actual results:
Diskless client never boots - kernel panics


Expected results:
Diskless client should boot up fine

Additional info:

Comment 1 Jason Vas Dias 2005-08-12 01:43:01 UTC
This is now fixed with system-config-netboot-0.1.26 .
The disklessrc will now bring up the loopback interface before configuring
the boot interface or doing DNS lookups.


Comment 5 Red Hat Bugzilla 2005-10-05 13:49:13 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-484.html



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