From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.4 i686)
Description of problem:
During a kickstart install, anaconda correctly configures eth0 for use in
install phase, but doesn't correctly setup the loopback (lo) device. Some
that try to access the loopback device then hang for 3 minutes (per access)
timeout, making the post install very slow (if using commands that access
We've implemented a work-around by making the first thing in our
/sbin/ifconfig lo 127.0.0.1
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install redhat 7.2 with a kickstart script
2. In the %post section use a command the requires lo (such as
Actual Results: Any program which requires access to lo hangs for 3
minutes, then times
out and continues (or whatever, depending on the program). No other ill
effects seen other
than very slow install times.
Expected Results: Up until 7.2, the lo device was configured for the %post
Don't see any documentation for a change, so I'd expect it to be there in
We do use a custom-cdrom made from the RH7.2 cdrom with all the released
rpms on it (including kernels). But I believe this happens even with the
as well. Does not happen with any releases before 7.2. We have a rather
work around of configuring the interface manually during the %pre and/or
stages of the kickstart.
I don't see any network devices set up in the post-install phase on a CDROM
install, and it looks right (both eth0 and lo0 up) on a network install.
Are you sure that you're not bringing up eth0 in the ?post also as that's the
only way I can think of that it would be up.
Closing due to inactivity. Please reopen if you have more information.