Description of problem: I setup a hostname, then went directly to storage and selected "lvm thin provisioning" and set it do delete existing partitions, then anaconda crashes. Only network and then storage spokes were used. 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/kickstart.py", line 244, in execute doAutoPartition(storage, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1677, in doKickstartStorage ksdata.autopart.execute(storage, ksdata, instClass) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 419, in _doExecute doKickstartStorage(self.storage, self.data, self.instclass) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 168, in run threading.Thread.run(self, *args, **kwargs) TypeError: unsupported operand type(s) for +: 'long' and 'NoneType' Additional info: 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 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 795174 [details] File: anaconda-tb
Created attachment 795175 [details] File: anaconda.log
Created attachment 795176 [details] File: environ
Created attachment 795177 [details] File: lsblk_output
Created attachment 795178 [details] File: nmcli_dev_list
Created attachment 795179 [details] File: os_info
Created attachment 795180 [details] File: program.log
Created attachment 795181 [details] File: storage.log
Created attachment 795182 [details] File: syslog
Created attachment 795183 [details] File: ifcfg.log
Created attachment 795184 [details] File: packaging.log
*** Bug 1004874 has been marked as a duplicate of this bug. ***
Proposed as a Blocker for 20-beta by Fedora user martix using the blocker tracking app because: Guided partitioning: "Complete an installation using any combination of disk configuration options it allows the user to select." Read comment #12: https://bugzilla.redhat.com/show_bug.cgi?id=1004874#c12
*** Bug 1010489 has been marked as a duplicate of this bug. ***
I attempted to install a Fedora 20 Alpha VM, using the x86_64 Alpha DVD ISO as the install media. The VM was KVM on a Fedora 19 x86_64 host with 1024MB RAM and 2 processors. I selected LVM Thin Provisioning as the filesystem type and was met with the error this BZ reports. I also tried previously to use LVM Thin Provisioning with encryption, which also failed. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Alpha\x20x86_64 quiet BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.18-1 product: Fedora reason: TypeError: unsupported operand type(s) for +: 'long' and 'NoneType' release: Cannot get release name. version: 20-Alpha
I tried installing Fedora Alpha via BFO. The Guest has 8 GB of HDD and I tried a minimal install using Btrfs. It didn't work; it claimed I lacked ~940 MB of HDD space; which amounted to the full installation. Then, I switched to LVM Thin Provisioned and this happened. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: repo=http://download.fedoraproject.org/pub/fedora/linux/development/20/x86_64/os/ initrd=http://download.fedoraproject.org/pub/fedora/linux/releases/test/20-Alpha/Fedora/x86_64/os/images/pxeboot/initrd.img BOOT_IMAGE=http://download.fedoraproject.org/pub/fedora/linux/releases/test/20-Alpha/Fedora/x86_64/os/images/pxeboot/vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.18-1 product: Fedora reason: TypeError: unsupported operand type(s) for +: 'long' and 'NoneType' release: Cannot get release name. version: 20
Discussed during 2013-09-25 Blocker Review Meeting [1] - AcceptedBlocker - Violates the following F20 beta release criterion: "Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions" [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-09-25/ [2] https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria#Custom_partitioning
blivet 0.22 went stable already; closing for now, re-open if it's still valid with Beta TC1.