Red Hat Bugzilla – Bug 1002373
anaconda crash writing network configuration installing from live CD, when network is configured manually
Last modified: 2013-09-18 22:42:04 EDT
Description of problem:Installing from Fedora Live XFCE i686-19-1 CD.
Version-Release number of selected component (if applicable):anaconda 19.30.13-1.fc19.i686
How reproducible:(almost) always
Steps to Reproduce:
1.Boot live CD
3.Install to hard drive
Actual results: When it gets to the stage where it writes the network
configuration at end of installation, it stays in that state for a long long
time and then gives the Unknown Error failure
Expected results: Should install and finish normally
Additional info: This is on a system where I configure the network manually,
not using DHCP. I can install by not configuring the network first, just
let it install and then configure the network after booting up the working
Here are first two lines of the traceback
File "/usr/lib/python2.7/site-packages/pyanaconda/simpleconfig.py", line 77,
in read with open filename as f:
File "/usr/lib/python2.7/site-packages/pyanaconda/simpleconfig.py", line 187,
in read SimpleConfigFile read (self, self.path)
Can you please attach the full traceback file, along with any other log files in /tmp, to this bug? How are configuring your network interface?
I would like to have got more trace, but the system froze up while I was
trying to do something with the bug. Now that I have the system
successfully installed I'm reluctant to go through that time-consuming
I booted the Xfce Live CD, left clicked on the little network icon in the
upper right corner, got into the screen where you set the network configuration
and set it. In my case I use manual configuration, not DHCP, so I selected
manual configuration and put in the IP address, netmask, gateway address
and DNS address. Then it reported the network wa up and running.
Then I executed the install to hard drive, went through the usual agonizing/
confusing process of setting up the hard drive partitions, got the installer
running. After it did the installation and the post-install stuff it said
it was saving the network configuration. It sat in that state for a long
time, many minutes, while I waited for something to happen. Finally it
opened the window saying an unknown error has occurred.
How do I get to log files in /tmp when I'm in the middle of anaconda with
the error window?
If the option to report a bug from the traceback window isn't working, you can switch to a shell by hitting Ctrl+Alt+F2.
Created attachment 793903 [details]
Created attachment 793904 [details]
Created attachment 793908 [details]
Created attachment 793909 [details]
Created attachment 793910 [details]
Created attachment 793911 [details]
Then I repeated the installation but without configuring the network first,
and as usual it worked correctly.
This happens alos with F20 Alpha TC3, Live DVD.
The case is configuring a network device before starting installation, having no more than one wired device.
After talking to Radek, this is the simplest reproducer:
1. Boot Live image
2. Before running Anaconda, changed wired configuration. Anything that dumps a new config file should be sufficient, probably a change in profile name or disabling ipv6 should be enough. Or you can reconfigure your IP/netmask/dhcp to be sure.
3. Start Anaconda, start installation
4. At the end of the installation, there will be a traceback. Some parts of the system will stay unconfigured, probably a bootloader won't be installed either.
If you need to configure your wired network, do it after you start Anaconda. That shouldn't crash it.
Wireless network should not be affected by this bug.
Proposing as Final Blocker. This is a violation of "The installer must run when launched normally from the release-blocking images."  for cases where you need to configure your connection manually, but I don't feel this is common enough to block Alpha or Beta.
Radek also requested to propose this as Alpha Freeze Exception, he'd like to have it fixed in Alpha, even though the fix will probably not be fully contained and might affect other areas.
anaconda-20.12-1.fc20 has been submitted as an update for Fedora 20.
(In reply to Kamil Páral from comment #12)
> Radek also requested to propose this as Alpha Freeze Exception, he'd like to
> have it fixed in Alpha, even though the fix will probably not be fully
> contained and might affect other areas.
+1 Alpha Freeze Exception
+1 for Alpha FE
+1 for AFE
That makes +3 for alpha FE, moving to accepted
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-20.12-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-20.13-1.fc20 has been submitted as an update for Fedora 20.
anaconda-20.14-1.fc20 has been submitted as an update for Fedora 20.
anaconda-20.15-1.fc20 has been submitted as an update for Fedora 20.
anaconda-20.16-1.fc20 has been submitted as an update for Fedora 20.
anaconda-20.17-1.fc20 has been submitted as an update for Fedora 20.
I have tested with F20 Alpha RC3 using reproducer in comment 12. The problem is gone, no crashed, installed system is configured properly.
anaconda-20.17-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.