Bug 502936 - kickstart doesn't bring up loopback network device
Summary: kickstart doesn't bring up loopback network device
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-27 20:20 UTC by Jonathan Kamens
Modified: 2011-07-27 17:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-27 17:22:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2009-05-27 20:20:45 UTC
The loopback network device isn't active by default during kickstart installations.  It can be activated easily enough by doing "ifconfig lo up" in the %pre script of the ks.cfg file, but there's no reason why it shouldn't be activated by default.  Leaving it down can prevent stuff from working, e.g., during our kickstart we install and start the postgresql server and then try to connect to it on 127.0.0.1.

Comment 1 Chris Lumens 2009-08-07 15:48:44 UTC
It definitely should be getting brought up via the initLoopback function in loader2/net.c.  Can you boot with loglevel=debug and attach the logs to this bug report?  Maybe there's something odd going on here.


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