Bug 1140635 - Traceback when metadatasize is not passed alongside the thinpool option
Summary: Traceback when metadatasize is not passed alongside the thinpool option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ovirt-node-ng
TreeView+ depends on / blocked
 
Reported: 2014-09-11 11:51 UTC by Fabian Deutsch
Modified: 2014-10-20 23:01 UTC (History)
5 users (show)

Fixed In Version: anaconda-21.48.10-1.fc21
Clone Of:
Environment:
Last Closed: 2014-10-20 23:01:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fabian Deutsch 2014-09-11 11:51:35 UTC
Description of problem:
Anaconda fails with a traceback when the following storage configuration is used:

clearpart --all --initlabel
bootloader --append="console=ttyS0 quiet" --timeout=1

part biosboot --size=1
part /boot --size=512 --fstype ext4 --label=Boot --asprimary

part pv.01 --size 5000
volgroup HostVG pv.01
logvol /config --vgname=HostVG --size=64 --name=Config --fstype=ext4
logvol none --vgname=HostVG --size=4000 --name=ImagePool --thinpool --chunksize=128  # to fix append: --metadatasize=4
logvol / --vgname=HostVG --size=3000 --name=Image-0.0 --thin --poolname=ImagePool --fstype=ext4 --fsoptions=discard


It is solved when setting the --metadatasize option on the thinpool related line. Tho I do not know what a sane default value is ..

Version-Release number of selected component (if applicable):
anaconda 21.48.3-1 exception report

How reproducible:
always

Steps to Reproduce:
1. Run kickstart with storage configuration from above
2.
3.

Actual results:


Expected results:


Additional info:
anaconda 21.48.3-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 921, in execute
    pool_args = { "metadatasize": Size("%d MiB" % self.metadata_size),
  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 755, in execute
    l.execute(storage, ksdata, instClass)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1924, in doKickstartStorage
    ksdata.logvol.execute(storage, ksdata, instClass)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/spokes/storage.py", line 372, in execute
    doKickstartStorage(self.storage, self.data, self.instclass)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 53, in setup
    spoke.execute()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/__init__.py", line 170, in setup
    should_schedule = obj.setup(self.ENVIRONMENT)
  File "/sbin/anaconda", line 1358, in <module>
    anaconda._intf.setup(ksdata)
TypeError: %d format: a number is required, not NoneType

Comment 1 Fabian Deutsch 2014-09-11 12:04:47 UTC
IIUIC this does not need to be passed to lvm (at least lvcreate) at best the default value is calculated like lvm does.

Comment 2 Fedora Update System 2014-10-15 13:07:42 UTC
anaconda-21.48.10-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/anaconda-21.48.10-1.fc21

Comment 3 Fedora Update System 2014-10-16 17:18:26 UTC
Package anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-21.48.10-1.fc21 pykickstart-1.99.63-2.fc21 python-blivet-0.61.5-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12944/pykickstart-1.99.63-2.fc21,python-blivet-0.61.5-1.fc21,anaconda-21.48.10-1.fc21
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-10-20 23:01:46 UTC
anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.