Hide Forgot
Created attachment 482024 [details] Screenshot of an error window appearing during installation Description of problem: When using "bootif" or "ibft" value in network --device in kickstart anaconda crashes in stage2 while processing it. Problem is that it only tries to find a device of a given name or MAC address but it has a "ibft" or "bootif" string which is neither of these. Version-Release number of selected component (if applicable): 13.21.100 How reproducible: every time when using "ibft" or "bootif" in network --device Steps to Reproduce: 1. use a kickstart file with a network --device="ibft" or network --device="bootif" line 2. go through the installation to stage2 Actual results: Anaconda crashes Expected results: Anaconda continues in installation with correctly configured network according to value in kickstart file
Created attachment 482027 [details] anaconda.log
Created attachment 482028 [details] ifcfg.log
Created attachment 482029 [details] syslog
Created attachment 482049 [details] proposed patch fixing "bootif" value processing (NOT TESTED)
Created attachment 482259 [details] proposed patch fixing "bootif" value processing (tested and seems to be working)
The "ibft" issue has been fixed in rhel 6.1 as part of bug #638131 (see https://bugzilla.redhat.com/show_bug.cgi?id=638131#c22), I'll keep this bug open to track the "bootif" issue.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
This should be fixed in anaconda-13.21.121-1.
During testing I hit bug #729266
*** Bug 729266 has been marked as a duplicate of this bug. ***
Hi Radek, with updates.img from bug #729266 here's what I found: 1) If I create a KVM guest which boots from network (PXE) and append my ks.cfg file to the boot command line everything works fine. PXE supplies the BOOTIF= parameter. This works with or without the updates.img. 2) If I create a regular virt guest not booting from PXE without updates.img then I get the traceback reported in bug 729266. 3) If I create a regular virt guest not booting from PXE with updates.img. The BOOTIF parameter wasn't present on the command line. There was no traceback but I get an error message: The provided network interface bootif doesn't exist.
If the error in 3) is expected we should probably update the message text so that the user knows BOOTIF was not present.
(In reply to comment #15) > If the error in 3) is expected we should probably update the message text so > that the user knows BOOTIF was not present. Sounds reasonable, I've updated the updates.img: http://rvykydal.fedorapeople.org/updates.729266.img to say: "Using --device=bootif without BOOTIF= boot option supplied" in case 3) Posting for a-d-l review.
(In reply to comment #16) > (In reply to comment #15) > > If the error in 3) is expected we should probably update the message text so > > that the user knows BOOTIF was not present. This should go to anaconda-13.21.127-1.
Tested with anaconda-13.21.128. Both scenarios w/w/o BOOTIF= parameter and network --device bootif work as expected.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1565.html