Version-Release number of selected component: anaconda-18.8 Additional info: libreport version: 2.0.12 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.0-0.rc6.git0.2.fc18.i686
Created attachment 617679 [details] File: ifcfg.log
Created attachment 617680 [details] File: anaconda-tb
Created attachment 617681 [details] File: product
Created attachment 617682 [details] File: type
Created attachment 617683 [details] File: environ
Created attachment 617684 [details] File: storage.log
Created attachment 617685 [details] File: version
Created attachment 617686 [details] File: program.log
Created attachment 617687 [details] File: anaconda.log
Created attachment 617688 [details] File: syslog
Created attachment 617689 [details] File: hashmarkername
Created attachment 617690 [details] File: packaging.log
Created attachment 617691 [details] File: cmdline_file
Created attachment 617692 [details] File: release
Created attachment 617693 [details] File: description
In Live install after installing bootloader this backtrace happened Package: anaconda-18.10-1.fc18.x86_64 Architecture: x86_64 OS Release: Fedora release 18
I just started installation (from PXE) with previous F17 installation on the disk. Package: anaconda-18.8 OS Release: Fedora release 18
Correction, this happens after the installation is complete, in the "Configuring installed system" step.
Patch posted for review. You can check updates image with fix: http://rvykydal.fedorapeople.org/updates.860791.img
(Just for the record the system does boot after this backtrace.)
Discussed at 2012-10-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-03/f18-beta-blocker-review-2.2012-10-03-16.00.log.txt . We agreed this looks like a serious issue - even though the installed system boots, crashes during the install process are always bad and it means some late system configuration steps probably didn't happen - but we don't have enough data on exactly what the circumstances are that trigger this bug to make a decision on blocker status. If people can isolate the triggering circumstances more precisely we will re-evaluate this at the next meeting, if it has not already been closed by then.
install from live ,DVD;netinstall to HD occurs at end of install Package: anaconda-18.11-1.fc18.x86_64 OS Release: Fedora release 18
anaconda-18.12-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.12-1.fc18
install sugar-desktop DE from F18-Beta-TC1 DVD x86_64 occurs in configuring system Package: anaconda-18.11 OS Release: Fedora release 18-Beta-TC1
Package anaconda-18.12-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.12-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15378/anaconda-18.12-1.fc18 then log in and leave karma (feedback).
f18-Beta-TC2-x86_64 Netinstall hangs on final step "Configuring Installed System" no error message but seems to be same error seen on TC1 Netinstall Wish anaconda would allow deleting the autodetected wlan0 (wireless entry) as I suspect that this is the cause of the error
(In reply to comment #26) > f18-Beta-TC2-x86_64 Netinstall hangs on final step > "Configuring Installed System" > no error message but seems to be same error seen on TC1 Netinstall > > Wish anaconda would allow deleting the autodetected wlan0 (wireless entry) > as I suspect that this is the cause of the error Did you have an existing partition on the HD? I found with current anaconda installs only start/succeed if I delete any existing partition before booting to install. Anyway I can confirm that with anaconda-18.12 install no longer hangs or crashes for me because of wlan0.
I no longer see this issue, but now, with anaconda 18.12, the wired network is disabled by default after installation (I used LiveCD). It is very likely related to the recent fix. Should I report a new bug or will we handle it here?
(In reply to comment #28) > I no longer see this issue, but now, with anaconda 18.12, the wired network > is disabled by default after installation (I used LiveCD). It is very likely > related to the recent fix. Should I report a new bug or will we handle it > here? Please report a new bug. Thanks.
(In reply to comment #29) > Please report a new bug. Thanks. OK, bug 864087. This one is fixed and pushed stable (and part of F18 Beta TC2), closing.
Same thing with anaconda 18.29.2 kickstart install and noipv6 boot option : anaconda 18.29.2 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/simpleconfig.py", line 77, in read with open(filename) as f: File "/usr/lib64/python2.7/site-packages/pyanaconda/simpleconfig.py", line 187, in read SimpleConfigFile.read(self, self.path) File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 285, in loadIfcfgFile IfcfgFile.read(self) File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 769, in get_ifcfg_value dev.loadIfcfgFile() File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 811, in <genexpr> for dev in getDevices())): File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 811, in disableIPV6 for dev in getDevices())): File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 877, in writeNetworkConf disableIPV6(ROOT_PATH) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 71, in doConfiguration writeNetworkConf(storage, ksdata, instClass) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run threading.Thread.run(self, *args, **kwargs) IOError: [Errno 2] No such file or directory: '/etc/sysconfig/network-scripts/ifcfg-wlan0' Local variables in innermost frame: self: filename: /etc/sysconfig/network-scripts/ifcfg-wlan0