Booting rescue mode from the TC7 x86_64 DVD results in traceback right after asking if network interfaces are to be enabled or not. I've not seen this on every system - my VMs seem to be not affected but a bare metal machine with 2 NICs is affected every time. I haven't tested with much other hardware to see how many machines are affected by this.
Created attachment 639600 [details] anaconda.log
Created attachment 639601 [details] anaconda-tb-b0Ll7z
Created attachment 639602 [details] console.log
Created attachment 639603 [details] packaging.log
Created attachment 639604 [details] program.log
Created attachment 639605 [details] storage.log
Created attachment 639606 [details] syslog
anaconda 18.24 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/textw/netconfig_text.py", line 75, in run for devname in devnames: File "/usr/lib64/python2.7/site-packages/pyanaconda/rescue.py", line 99, in enableNetwork ret = w.run() File "/usr/lib64/python2.7/site-packages/pyanaconda/rescue.py", line 221, in doRescue if not intf.enableNetwork(): File "/sbin/anaconda", line 973, in <module> doRescue(anaconda.rescue_mount, ksdata, anaconda.platform) TypeError: 'NoneType' object is not iterable
anaconda-18.28-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.28-1.fc18
Package anaconda-18.28-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.28-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.28-1.fc18 then log in and leave karma (feedback).
hum, the 'fix' for this appears to involve not offering to bring up the network interfaces at all (tested Beta RC1). not sure that's what was intended? The 'bring up interfaces' dialog never shows, and when I get to the shell, the network is indeed not up.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.