Red Hat Bugzilla – Bug 432011
stage1 is unable to proceed after returing back from manual IPv6 address selection
Last modified: 2008-05-21 11:33:04 EDT
Version-Release number of selected component (if applicable):
anaconda-220.127.116.11-1 / RHEL5.2-Client-20080207.0
Steps to Reproduce:
1. Boot RHEL5.2-Client-20080207.0 installer (manual installation)
2. Select keyboard and language
3. In "Configure TCP/IP" select IPv4 DHCP configuration and Manual IPv6
4. Hit "OK" button
5. When "Manual TCP/IP Configuration" dialog appears, do not put anything in,
just hit "Back" button
6. "Configure TCP/IP" dialog appears with "Enable IPv6 Support" option set
to "Automatic neighbor discovery (RFC 2461)" <- do not change anything
7. Hit "OK" button
8. "Sending request for IP information for eth0" dialog appears
9. Installer stays at " Configure TCP/IP" screen (no matter how many times
you hit the "OK" button) while tty3 screen repeats:
"WARNING: no network link detected on eth0"
10. Moreover, if you hit "Back" button from here and select some installation
method from the screen that appears and hit "OK" button, loader segfaults
(most likely unrelated to previous problem):
loader received SIGSEGV! Backtrace:
install exited abnormally [1/1]
sending termination signals...done
sending kill signals...done
you may safely reboot your system
There are a lot of bugs in this one report and they are all related. After
working on this one for a couple of days, I have found the following that needs
Item 10 in the report above is caused by initLoopback() in anaconda's loader
code. I have a patch for this problem, so when you select back and get to the
method screen, choose a different method, it no longer causes a traceback.
Item 9 is caused by problems in both anaconda and libdhcp. In anaconda, the
problem lies with clearInterface(), which does not work right for this scenario
because it cannot get a netlink handle (only one open netlink handle per process
allowed). That's where I found the problem in libdhcp. libdhcp is not
releasing the netlink handle it opens when initially configuring an interface.
This only happens when you go Back in stage1 and have to reconfigure an
interface for whatever reason. I am working on a fix for this issue.
Item 6 describes a problem where you return to the TCP/IP configuration screen
and your previous selections have been reset. This is a problem in loader's
main() function losing flags stepping forward and backward. I am also working
on a fix for this issue.
Created attachment 295865 [details]
Makes sure we return libnl objects to the cache we created.
Created attachment 295866 [details]
Fix network device reconfigurations in stage 1 (i.e., going back to reconfig
the interface). Also fix the segfault caused when going back and selecting a
new install method.
I was able to fix these issues without needing to patch libdhcp.
This patch fixes all but item #6, patch for that is coming up.
Created attachment 295888 [details]
This is the last patch that fixes problem #10. When you go back to the network
configuration screen in loader, your original selections are preserved and not
reset to the defaults each time.
I meant item #6. Either way, your selections are preserved in the UI when you
go back now.
These issues will be fixed in anaconda-18.104.22.168-1.
- I'm able to go back and forth and TCP/IP settings are preserved.
- I'm able to proceed to stage 2 after eth0 gets the DHCP lease.
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.