Red Hat Bugzilla – Bug 862006
NameError: global name 'size_func_kwargs' is not defined
Last modified: 2012-10-15 10:29:12 EDT
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
:The following was filed automatically by anaconda:
:anaconda 18.8 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 3241, in device_size
: return get_pv_space(self.size, len(self.disks), **size_func_kwargs)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1839, in setContainerMembers
: device_space = factory.device_size
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2025, in newDevice
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 647, in _replace_device
: self.__storage.newDevice(*args, **kwargs)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 748, in _save_right_side
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1123, in on_add_clicked
:NameError: global name 'size_func_kwargs' is not defined
Created attachment 619829 [details]
Created attachment 619830 [details]
Created attachment 619831 [details]
Created attachment 619832 [details]
Created attachment 619833 [details]
Created attachment 619834 [details]
Created attachment 619835 [details]
Created attachment 619836 [details]
Created attachment 619837 [details]
Created attachment 619838 [details]
Created attachment 619839 [details]
Created attachment 619840 [details]
Created attachment 619841 [details]
*** Bug 862632 has been marked as a duplicate of this bug. ***
(In reply to comment #14)
> *** Bug 862632 has been marked as a duplicate of this bug. ***
Please transfer Blocks field, thanks.
Discussed at 2012-10-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-03/f18-beta-blocker-review-2.2012-10-03-16.00.log.txt .
Per the dupe, the cause here seems to be simply 'try and set up an LVM configuration through custom part'. On that basis we agreed this is clearly at least a Final blocker, per criterion "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" (though we cannot formally mark the bug as such as it would create confusion about the Beta blocker status).
The status for Beta is less clear: during the discussions about what the criteria for Beta should be we have not yet clearly established whether we expect LVM to work at Beta or not. The current relevant criterion reads:
"The installer's custom partitioning mode must be capable of the following: Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types"
which leaves the question as 'is LVM a commonly-used filesystem type'. We agreed to delay decision on whether this is a blocker while we consider that with input from test@ and the anaconda team. The decision on this bug will set a broad precedent as to whether LVM is considered to block Beta or not, so we need to consider it carefully.
Switching an ext4 partition type from "standard" to LVM
OS Release: Fedora release 18-Beta-TC2
I got this doing the opposite, most likely a duplicate.(Bug 864113)
Discussed at 2012-10-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-10/f18beta-blocker-review-3.2012-10-10-16.05.log.txt . Unfortunately we didn't manage to discuss the status of LVM last week, so evaluation of this bug is delayed again. We will try and make sure it gets done this week.
Discussed further at 2012-10-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-10/f18beta-blocker-review-3.2012-10-10-16.05.log.txt . We continued bashing away at this and eventually decided that anaconda should be capable of creating partitions/filesystems/devices/whatever you want to call them of all the types it actually offers (through the GUI) at Beta stage. If some partition types are 'unsupported', they shouldn't be offered (the same way we hid btrfs in the last few oldUI releases) or should be hidden behind kernel parameters (as we did with btrfs before it was 'stable'). We will work up precise wording on the mailing list. But with that general principle accepted, this bug is accepted as a blocker, as LVM is on the list of offered Device Types.
Marking as ON_QA and fixed in 18.14 - this is actually fixed in 18.14 (TC3), anaconda team just forgot to update the bug and include it in the update description. This seems to be working for me in TC3, I was able to create an LV using custom part, but it'd be good if one of the original reporters can confirm before we set this to VERIFIED.
This is now fixed with F18 Beta TC4. I can set partition type to LVM and continue with the installation and it doesn't crash. Closing.