Description of problem: anaconda 13.37.2 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/__init__.py", line 1744, in fsFreeSpace if os.statvfs(path)[statvfs.F_FLAG] & ST_RDONLY: File "/usr/lib/anaconda/storage/__init__.py", line 1152, in fsFreeSpace return self.fsset.fsFreeSpace() File "/usr/lib/anaconda/backend.py", line 158, in mountInstallImage free = anaconda.storage.fsFreeSpace File "/usr/lib/anaconda/yuminstall.py", line 904, in run if self.anaconda.backend.mountInstallImage(self.anaconda, stage2img): File "/usr/lib/anaconda/yuminstall.py", line 1703, in doInstall rc = self.ayum.run(self.instLog, cb, anaconda.intf, anaconda.id) File "/usr/lib/anaconda/backend.py", line 299, in doInstall return anaconda.backend.doInstall(anaconda) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1313, 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 1334, in handleRenderCallback self.currentWindow.renderCallback() OSError: [Errno 2] No such file or directory: '/mnt/sysimage//mnt/source' Version-Release number of selected component (if applicable): * anaconda 13.37.2 How reproducible: * 3 autofilled bugs incorrectly linked to bug#565879 Actual results: * see attachment#408966 [details] * see attachment#410292 [details] * see attachment#410112 [details] * see attachment#409010 [details] Expected results: * No exception Additional info:
Anne, Steve, Norm and cpg: this failure was reported against F-13-Beta. Can you confirm the steps to reproduce this bug using the latest F-13 install images? Live images, and CD/DVD/netinst.iso media is available at http://serverbeach1.fedoraproject.org/pub/alt/stage/13.TC1
Can anyone who is seeing this problem please try adding updates=http://clumens.fedorapeople.org/587662.img to their command line arguments?
(In reply to comment #2) > Can anyone who is seeing this problem please try adding > updates=http://clumens.fedorapeople.org/587662.img to their command line > arguments? Positive test results using the posted updates.img. Thanks clumens and steved. Anyone else, your feedback is still valuable. 11:12:37 steved: clumens: btw... that update you gave me worked! thanks! 11:13:03 clumens: steved: fantastic.
This fix in TC1 appears to work in VMware now. Also i can add extra repositories in the net (which I could not in the beta). All good!
Just to clarify: I did not add the updates=http://clumens.... img. Just the TC1 i386 iso tested.
FWIW, this happened again on a new install on that TC1 image, so the issue is still there. However, I did a number of things when it failed, and I cannot replicate it ... I don't know what combination of things I did, but i did click on "Fedora 13 - i386 - Test Updates" and unclicked it. Anyway, the point is that this issue appears to be not entirely gone.
Created attachment 410734 [details] Attached traceback automatically from anaconda.
(In reply to comment #7) > Created an attachment (id=410734) [details] > Attached traceback automatically from anaconda. To add to my automatic BZ entry: Attempting to install TC1 x86_64 in Virtualbox. I tried just checking "Testing Updates" and it could not satisfy all the dependencies. Went back and checked the main repo and then ran into the bug.
Clearly this is not yet fully fixed, re-assigning. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
> Clearly this is not yet fully fixed, re-assigning. Based on what? Did you look at the traceback in comment #7? I did, and it says: anaconda 13.39 exception report Then let's look at what version I had in the Fixed In: field: anaconda-13.40-1 Last I checked, 13.40 is newer than 13.39. Therefore you cannot say it's not fully fixed based on anything in comment #7. Putting back into MODIFIED until actual evidence that it's not yet fixed is attached.
it might've helped to add a comment noting that an updated fix had been pushed, but sorry. just the version field is a rather subtle hint. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
anaconda-13.40-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.40-1.fc13
anaconda-13.40-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update anaconda'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/anaconda-13.40-1.fc13
We should now be able to confirm that this bug is fixed using the images here: http://alt.fedoraproject.org/pub/alt/stage/13.0505/Fedora/i386/os/images/ if we have not yet confirmed the fix, can anyone able to reproduce this bug please test with one of those images and check that the bug is fixed? Thanks.
anaconda-13.40-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 590637 has been marked as a duplicate of this bug. ***