Description of problem: 1. select "LVM thin provisioning" option 2. enable full disk encryption 3. select manual partitioning mode 4. click on "create partitions automatically" Version-Release number of selected component: anaconda-20.10-1 The following was filed automatically by anaconda: anaconda 20.10-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2615, in vgSpaceUsed + self.logSize + self.metaDataSize) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2847, in vgSpaceUsed space = super(LVMThinPoolDevice, self).vgSpaceUsed File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2409, in <genexpr> used = sum(lv.vgSpaceUsed for lv in self.lvs) + self.snapshotSpace File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2409, in freeSpace used = sum(lv.vgSpaceUsed for lv in self.lvs) + self.snapshotSpace File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2296, in _addLogVol lv.size > self.freeSpace: File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2564, in __init__ self.parents[0]._addLogVol(self) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1144, in newLV return device_class(name, *args, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/partitioning.py", line 282, in _scheduleVolumes dev = new_volume(**kwargs) File "/usr/lib/python2.7/site-packages/blivet/partitioning.py", line 321, in doAutoPartition _scheduleVolumes(storage, devs) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2497, in _do_autopart doAutoPartition(self.__storage, self.data) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2530, in on_create_clicked self._do_autopart() TypeError: unsupported operand type(s) for +: 'long' and 'NoneType' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: inst.repo=nfs:nfs.englab.brq.redhat.com:/pub/fedora/fedora-alt/stage/20-Alpha-TC4/Fedora/x86_64/iso/Fedora-20-Alpha-TC4-x86_64-DVD.iso initrd=F20/Alpha-TC4/x86_64/initrd.img BOOT_IMAGE=F20/Alpha-TC4/x86_64/vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.0-3.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20-Alpha-TC4
Created attachment 794330 [details] File: anaconda-tb
Created attachment 794332 [details] File: anaconda.log
Created attachment 794334 [details] File: environ
Created attachment 794337 [details] File: lsblk_output
Created attachment 794339 [details] File: nmcli_dev_list
Created attachment 794341 [details] File: os_info
Created attachment 794343 [details] File: program.log
Created attachment 794344 [details] File: storage.log
Created attachment 794346 [details] File: syslog
Created attachment 794347 [details] File: ifcfg.log
Created attachment 794348 [details] File: packaging.log
I can reproduce this also without steps 2-4.
I selected lvm thin provisioning, but instead of automatic partitioning i did custom partititioning, manually deleting existing partitions prior to use the guided partitioning, at which point anaconda crashed. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Alpha-TC4\x20x86_64 quiet BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-3.fc20.x86_64 package: anaconda-20.10-1 product: Fedora reason: TypeError: unsupported operand type(s) for +: 'long' and 'NoneType' release: Cannot get release name. version: 20-Alpha-TC4
Bug 1005506 might be a dup of this one.
Using LVM thin provision, then manually setup partitions. Clicking the + to automatically add caused this issue. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Alpha\x20x86_64 rd.live.check quiet BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.15-1 product: Fedora reason: TypeError: unsupported operand type(s) for +: 'long' and 'NoneType' release: Cannot get release name. version: 20-Alpha
*** This bug has been marked as a duplicate of bug 1005506 ***