Description of problem:
This exception occurs before the installer displays anything.
I reproduced it twice in several trials by repeatedly starting and quitting the installer.
The following was filed automatically by anaconda:
anaconda 18.37.8 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/pyanaconda/iutil.py", line 434, in getSubdirSize
sinfo = os.lstat(curpath)
File "/usr/lib/python2.7/site-packages/pyanaconda/iutil.py", line 439, in getSubdirSize
dsize += getSubdirSize(curpath)
File "/usr/lib/python2.7/site-packages/pyanaconda/iutil.py", line 446, in getDirSize
File "/usr/lib/python2.7/site-packages/pyanaconda/packaging/livepayload.py", line 141, in spaceRequired
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/lib/space.py", line 50, in check
needed = self.payload.spaceRequired
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 221, in _handleCompleteness
if self._checker and not self._checker.check():
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 206, in _updateCompleteness
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 171, in _createBox
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 306, in refresh
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/__init__.py", line 121, in run
File "/sbin/anaconda", line 991, in <module>
OSError: [Errno 2] No such file or directory: '//etc/multipath.conf.anacbak'
cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-18-TC4-i686-Live-Desktop. rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0
other involved packages:
release: Fedora release 18 (Spherical Cow)
Created attachment 672240 [details]
Created attachment 672241 [details]
Created attachment 672242 [details]
Created attachment 672243 [details]
Created attachment 672244 [details]
Created attachment 672245 [details]
Created attachment 672246 [details]
$ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Final/TC4/Fedora-18-TC4-i686-Live-Desktop.iso -usb -vga qxl -boot menu=on -usbdevice mouse
The target disk was previously installed with the x86_64 installer and the default storage configuration.
[snippet from attached anaconda.log]
17:03:34,658 DEBUG anaconda: isys.py:mount()- going to mount /dev/mapper/fedora-root on /mnt/sysimage as ext4 with options defaults,ro
17:03:34,769 ERR anaconda: Error running arch: Exec format error
17:03:34,820 DEBUG anaconda: isys.py:umount()- going to unmount /mnt/sysimage, removeDir = False
 Command-line was:
$ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Final/TC4/Fedora-18-TC4-x86_64-Live-Desktop.iso -usb -vga qxl -boot menu=on -usbdevice mouse
Proposing as a blocker:
8. The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above
Fedora 18 Final Release Criteria
"I reproduced it twice in several trials by repeatedly starting and quitting the installer."
That's really not supported, anaconda has to poke disks when it starts up and by the time you do that several times, weird stuff (tm) can happen.
Failures produced by repeatedly quitting and restarting the installer aren't blockers, IMHO. You can always reboot and try again.
oh, hey, I hit this the first time I tried to run liveinst from TC4 in my normal test VM. no restarts required. so that does look more worrying.
Created attachment 672272 [details]
my traceback: first try hit it
1. space check thread calls os.listdir (returned list includes /etc/multipath.conf.bak) and begins to iterate over returned list
2. storage init thread removes /etc/multipath.conf.bak
3. space check thread tries to access /etc/multipath.conf.bak when it reaches that point in the returned list from step 1
is this new, or are we just getting unlucky?
(In reply to comment #15)
> is this new, or are we just getting unlucky?
Just getting unlucky AFAIK. This is something that can only happen on live media.
+1 NTH from me.
So I think the Welcome screen bug probably exposed this one by changing the timings of installer startup. But bcl and clumens think fixing it is still the right thing to do, and you could plausibly hit it some other way even with the Welcome screen fixed. So, +1 NTH. AcceptedNTH with this and the above votes.
anaconda-18.37.10-1.fc18 has been submitted as an update for Fedora 18.
couldn't trigger this after a dozen or so attempts with a custom 18.37.10 live image.
I was just beginning the install of Fedora 18 from the Fedora 18 Live CD Image.
OS Release: Fedora release 18
anaconda-18.37.11-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.37.11-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.