The following was filed automatically by anaconda: anaconda 11.5.0.38 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/__init__.py", line 1346, in parseFSTab raise Exception("fstab entry %s is malformed: %s" % (devspec, e)) File "/usr/lib/anaconda/storage/__init__.py", line 958, in mountExistingSystem fsset.parseFSTab(chroot=rootPath) File "/usr/lib/anaconda/upgrade.py", line 236, in upgradeMountFilesystems allowDirty = 0) 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/dispatch.py", line 227, in currentStep self.gotoNext() File "/usr/lib/anaconda/gui.py", line 1350, in setScreen (step, anaconda) = self.anaconda.dispatch.currentStep() File "/usr/lib/anaconda/gui.py", line 1513, in setup_window self.setScreen() File "/usr/lib/anaconda/gui.py", line 1523, in run self.setup_window(runres) File "/usr/lib/anaconda/gui.py", line 1270, in run self.icw.run (self.runres) File "/usr/bin/anaconda", line 1029, in <module> anaconda.intf.run(anaconda) Exception: fstab entry none is malformed: 'Device' object has no attribute 'path'
Created attachment 337848 [details] Attached traceback automatically from anaconda.
This should be fixed in anaconda-11.5.0.40-1.
Created attachment 338185 [details] Attached traceback automatically from anaconda.
Mine appears to be from anaconda 11.5.0.40 so no, it's not fixed.
This is a completely different failure, and has nothing to do with xenfs. Please open a separate bug.
Created attachment 338819 [details] Attached traceback automatically from anaconda.
Well the auto submit thingy is sure insistent on putting it here.
Cloned as bug #494992
Created attachment 354846 [details] Attached traceback automatically from anaconda.
Created attachment 355141 [details] Attached traceback automatically from anaconda.
Created attachment 355182 [details] Attached traceback automatically from anaconda.
(In reply to comment #11) > Created an attachment (id=355182) [details] > Attached traceback automatically from anaconda. This was added by the automatic report of anaconda. The problem seems to be treated in Bug#496406 with a fix available in anaconda-12.0-1
Created attachment 355197 [details] Attached traceback automatically from anaconda.
(In reply to comment #13) > Created an attachment (id=355197) [details] > Attached traceback automatically from anaconda. This system is a VMWare guest. I don't know if that has anything to do with it.
(In reply to comment #10) > Created an attachment (id=355141) [details] > Attached traceback automatically from anaconda. Like last comment this system also is virtual. Running in VirtualBox 3.0.2.
Created attachment 355240 [details] Attached traceback automatically from anaconda.
Created attachment 355624 [details] Attached traceback automatically from anaconda.
Created attachment 355949 [details] Attached traceback automatically from anaconda.
Created attachment 356392 [details] Attached traceback automatically from anaconda.
Created attachment 356457 [details] Attached traceback automatically from anaconda.
Created attachment 363619 [details] Attached traceback automatically from anaconda.
Comment on attachment 363619 [details] Attached traceback automatically from anaconda. I am running Fedora under VMware 6.5.3 build 185404
Created attachment 364520 [details] Attached traceback automatically from anaconda.
Created attachment 365984 [details] Attached traceback automatically from anaconda.
Created attachment 375349 [details] Attached traceback automatically from anaconda.