Bug 502936

Summary: kickstart doesn't bring up loopback network device
Product: Red Hat Enterprise Linux 5 Reporter: Jonathan Kamens <jik>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-27 17:22:00 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:

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.