Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1494475 - Anaconda thinpool volume size not calculate correctly when using --grow
Anaconda thinpool volume size not calculate correctly when using --grow
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-blivet (Show other bugs)
7.4
All Linux
high Severity high
: rc
: ---
Assigned To: David Lehman
Release Test Team
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-22 07:03 EDT by Paul Dwyer
Modified: 2018-04-10 14:24 EDT (History)
6 users (show)

See Also:
Fixed In Version: python-blivet-0.61.15.69-1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 14:23:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0982 None None None 2018-04-10 14:24 EDT

  None (edit)
Description Paul Dwyer 2017-09-22 07:03:36 EDT
Description of problem:
Anaconda when using --grow option for thinpool volume on RHEL 7.4 does not make calculation correctly, whereas RHEL 7.3 did 
Anaconda fails with traceback below when trying to create volume

Version-Release number of selected component (if applicable):
RHEL7.4
anaconda 21.48.22.121-1

How reproducible:
every time using attached kickstart file

Steps to Reproduce:
1. Created small vm with 40Gb space
2. install using attached kickstart
3. anaconda errors out

Actual results:
traceback

anaconda 21.48.22.121-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 488, in create
    raise errors.DeviceCreateError(str(e), self.name)
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 293, in execute
    self.device.create()
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 373, in processActions
    action.execute(callbacks)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 380, in doIt
    self.devicetree.processActions(callbacks)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 230, in turnOnFilesystems
    storage.doIt(callbacks)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 204, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg)
  File "/usr/lib64/python2.7/threading.py", line 765, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run
    threading.Thread.run(self, *args, **kwargs)
DeviceCreateError: ('lvcreate failed for vg_system/lv_system_thinpool: running /sbin/lvm lvcreate --thinpool vg_system/lv_system_thinpool --size 9244m --poolmetadatasize 16 --chunksize 64 --config  devices { preferred_names=["^/dev/mapper
/", "^/dev/md/", "^/dev/sd"] }  failed', 'vg_system-lv_system_thinpool')


Expected results:
Installation to succeed

Additional info:
This disk layout worked on RHEL7.3

Further testing shows that specifying exact size works but using --grow doesn't
e.g.
logvol none --fstype="None" --thinpool --name=lv_system_thinpool --vgname=vg_system --chunksize=64 --size=9212 --metadatasize=16
Comment 5 David Lehman 2017-12-20 14:15:47 EST
Logs from the successful 7.3 installation would be useful. Is it possible to get them?
Comment 9 David Lehman 2018-02-02 14:37:48 EST
I was able to reproduce the failure and the following patch solves the issue for me:

  https://github.com/storaged-project/blivet/pull/654
Comment 11 Jan Stodola 2018-02-22 08:03:23 EST
Reproduced on RHEL-7.4 GA
Verified with python-blivet-0.61.15.69-1.el7, compose RHEL-7.5-20180221.0

Moving to VERIFIED.
Comment 14 errata-xmlrpc 2018-04-10 14:23:13 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0982

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