Bug 191383 - loopback interface (lo) not configured during kickstart install from DVD
Summary: loopback interface (lo) not configured during kickstart install from DVD
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-11 14:35 UTC by Andreas Luik
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-15 18:44:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andreas Luik 2006-05-11 14:35:36 UTC
Description of problem:

I observed that the lookback network interface (lo) is not configured
while the %post scripts runs in a kickstart installation from DVD, whereas
it is properly configured if installing from an install server (via NFS).
This seems to be inconsistent to me.
(The resulting problem is that "cupsd" cannot be started and configured
in the %post installation script.)


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

anaconda-9.1.6.8-2.RHEL

How reproducible:

always

Steps to Reproduce:
1. run kickstart installation from DVD
2. in the %post script, check for lookback interface (lo), e.g. with ifconfig

Actual results:

"ifconfig lo" reports no inet address

Expected results:

"ifconfig lo" reports inet addr 127.0.0.1, "UP RUNNING"
(as it does when installing from an install server via network, e.g. NFS)


Additional info:

Comment 1 Jeremy Katz 2006-05-15 18:44:36 UTC
We only enable network interfaces on network installs.  Changing this in the
context of a Red Hat Enterprise Linux update is too risky for customers who are
dependent on existing behavior.  See bug 191424 to track discussion of changing
this for future releases


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