Red Hat Bugzilla – Bug 492186
ext4 migration fails
Last modified: 2009-06-25 13:49:34 EDT
The following was filed automatically by anaconda:
anaconda 126.96.36.199 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/iw/upgrade_migratefs_gui.py", line 45, in getNext
newfs = getFormat(entry.format.migrationTarget)
File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked
rc = self.currentWindow.getNext ()
NameError: global name 'getFormat' is not defined
Created attachment 336694 [details]
Attached traceback automatically from anaconda.
Doubt it's relevant based on the traceback (seems like a wrong/missing import), but in case it is:
This is a fresh F10 install from today + updates, today's boot.iso, with ext4migrate, click, click, click on the defaults (and checking the filesystem to do the migration).
Should be fixed in anaconda-188.8.131.52-1.
Cool. Is this something that I can drop in an updates.img for or would I need a new boot.iso?
(In reply to comment #4)
> Cool. Is this something that I can drop in an updates.img for or would I need
> a new boot.iso?
Its by far the easiest the get a new boot.iso, or you could use your existing and
add method=ask on the cmdline, and then point it to the network for stage2 (install.img).
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Used ext4migration option in anaconda for F10 > F11 upgrade using X64 ISO and migration doesn't appear to have happened. After upgrade, fstab still shows EXT3 and mount command shows partitions mounted as ext3.
(In reply to comment #7)
> Used ext4migration option in anaconda for F10 > F11 upgrade using X64 ISO and
> migration doesn't appear to have happened. After upgrade, fstab still shows
> EXT3 and mount command shows partitions mounted as ext3.
This is not the same bug as the one reported earlier. Please open a separate report on your problem.