Red Hat Bugzilla – Bug 928228
global name 'ROOT_PATH' is not defined
Last modified: 2013-04-03 05:50:55 EDT
Created attachment 716932 [details]
Description of problem:
an exception is raised during 'Creating ext4 on /dev/mapper/fedora-root'
This happens only on bare-metal (tested on two desktops). In virtual machines everything seems to work.
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/blivet/util.py", line 268, in copy_to_system
target = ROOT_PATH + source
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 2599, in write
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1612, in write
File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 123, in doInstall
File "/usr/lib64/python2.7/threading.py", line 504, in run
File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run
threading.Thread.run(self, *args, **kwargs)
NameError: global name 'ROOT_PATH' is not defined
Version-Release number of selected component (if applicable):
on bare metal
Steps to Reproduce:
1. Start anaconda
2. Choose default and use all disk(automatic partitioning)
3. Begin installation
Exception is raised while performing 'Creating ext4 on /dev/mapper/fedora-root'
Installation should continue
Created attachment 716938 [details]
Created attachment 716939 [details]
Created attachment 716940 [details]
Have seen this on ASUS laptop trying to install x86_64 TC2 from USB stick.
Discussed at 2013-03-27 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-blocker-review-3.2013-03-27-16.01.log.txt . Accepted as a blocker per criterion "The installer must be able to complete an installation to a single disk using automatic partitioning." for multiple bare metal cases. bcl says it will be fixed in the next python-blivet build.
I have seen this also on virtual machines (qemu-kvm) when I set controller to SCSI. On virtual machines with IDE or Virito disks everything seems to work.
python-blivet 0.9 was included in TC3. Can someone confirm that this is fixed in TC3? Thanks.
Verified on Fedora 19 TC3.
then we can close it.