Bug 165730

Summary:	current disklessrc cannot be used to boot 2.6.9-12.2.EL kernel
Product:	Red Hat Enterprise Linux 4	Reporter:	Jason Vas Dias <jvdias>
Component:	system-config-netboot	Assignee:	Jason Vas Dias <jvdias>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	Keywords:	Regression
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2005-484	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-05 13:49:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	156322, 165784

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