The following was filed automatically by anaconda: anaconda None exception report Traceback (most recent call first): File "/usr/lib/anaconda/iutil.py", line 566, in writeRpmPlatform os.mkdir("%s/etc/rpm" %(root,)) File "/usr/lib/anaconda/livecd.py", line 340, in doPostInstall iutil.writeRpmPlatform(anaconda.rootPath) File "/usr/lib/anaconda/backend.py", line 284, in doPostInstall anaconda.backend.doPostInstall(anaconda) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1317, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1338, in handleRenderCallback self.currentWindow.renderCallback() OSError: [Errno 2] No such file or directory: '/mnt/sysimage/etc/rpm'
Created attachment 337453 [details] Attached traceback automatically from anaconda.
Can we also get /tmp/syslog (/var/log/anaconda.syslog on the installed system)? This has all the makings of filesystem errors.
We finally have a handle on this one. It appears what's going on is that the Next button is still able to be clicked even when a progress bar is on the screen during livecd installs. So if you're too fast or accidentally double click the Next button, we skip steps and end up in some really weird situations. This will be fixed in anaconda after F11. For F11, just be slower on clicking the next button. See bug 498553 for more information. Thanks for the report.
*** Bug 500834 has been marked as a duplicate of this bug. ***
Created attachment 348848 [details] Attached traceback automatically from anaconda.