Description of Problem: When you perform an nfs install (kickstart or interactive) and the nfs install device is on eth1 for a two nic system, anaconda-ks.cfg does not capture the network information. Version-Release number of selected component (if applicable): How Reproducible: everytime Steps to Reproduce: 1. nfs install on eth1 of two nic system 2. 3. Actual Results: no network line Expected Results: network line for eth1 Additional Information:
Jeremy this is a dupe right?
Not a dupe, but dependent on bug 64108
Actually, I was able to configure and use eth1 (ksdevice=eth1) in kickstart ... it just not save any of the eth1 info in anaconda-ks.cfg
Fixed in CVS
Time tracking values updated
I'm going through Bugzilla closing some bugs that have been marked as Modified for some period of time. I believe that most of these issues have been fixed, so I'm resolving these bugs as Rawhide. If the bug you are seeing still exists, please reopen this report and mark it as Reopened.