Description of problem: Version-Release number of selected component: anaconda-20.25.15-1 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 812, in execute "chunksize": self.chunk_size / 1024.0 } File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 666, in execute l.execute(storage, ksdata, instClass) File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1750, in doKickstartStorage ksdata.logvol.execute(storage, ksdata, instClass) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/spokes/storage.py", line 260, in execute doKickstartStorage(self.storage, self.data, self.instclass) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 51, in setup spoke.execute() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/__init__.py", line 166, in setup should_schedule = obj.setup(self.ENVIRONMENT) File "/sbin/anaconda", line 1118, in <module> anaconda._intf.setup(ksdata) TypeError: unsupported operand type(s) for /: 'NoneType' and 'float' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: method=http://formosa.mobile.wg42.ch/fedora/20/ inst.text inst.sshd ks=http://formosa.mobile.wg42.ch/ks/anaconda-ks.cfg executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20
Created attachment 917176 [details] File: anaconda-tb
Created attachment 917177 [details] File: anaconda.log
Created attachment 917178 [details] File: environ
Created attachment 917179 [details] File: ks.cfg
Created attachment 917180 [details] File: lsblk_output
Created attachment 917181 [details] File: nmcli_dev_list
Created attachment 917182 [details] File: os_info
Created attachment 917183 [details] File: program.log
Created attachment 917184 [details] File: storage.log
Created attachment 917185 [details] File: syslog
Created attachment 917186 [details] File: ifcfg.log
Created attachment 917187 [details] File: packaging.log
Hi I tried to kickstart a system which has its root LV stored on a LVM thin pool volume. I just found [1], so I'm not sure if the feature is already expected to work yet or not. Unfortunately there is no update on the progress of this since half a year. Furthermore the LVM thin pool kickstart options are mentioned in the Fedora 20 as well as the RHEL 7 and CentOS 7 installation docs. [1]: https://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport Actually I first found the bug when trying to kickstart a CentOS 7 system with a kickstart file which was generated when interactively configuring the desired setup during a manual installation. Therefore the problem also exists with anaconda-19.31.79-1. The kickstart file which was used to generate this bug report is the adapted anaconda-ks.cfg from the CentOS 7 installation. It might be as well, that it has some flaws. But none that were obvious to me when consulting the documentation. Also the ksvalidator didn't complain about it. Cheers, Reto
Created attachment 917251 [details] Fedora 20 kickstart file Ah... my bad. I used a CentOS 7 installation kickstart config when uploading this bug. Here's my adapted version for installing a Fedora 20 system which also fails with the same error.
The error doesn't happen anymore, if I explicitly specify the '--chunksize' argument on the thinpool logical volume: logvol None --fstype="None" --size=7168 --name=p_system --vgname=vg_system --thinpool --chunksize=64 Cheers, Reto