Description of problem:- While updating the RHEVH host from RHEV-M GUI if its failed then error message in the imgbase logs is not clear. Imgbase logs are giving traceback error in the update logs but the error message is generic and not providing much detailed information about why update got failed. Version-Release number of selected component (if applicable): redhat-virtualization-host-update imgbased How reproducible: 100% Steps to Reproduce: 1. If RHVH upgrade get failed then 2. Reboot and login NGN #imgbase check 1. 2. 3. Actual results: subprocess.CalledProcessError: Command '['lvcreate', '--thin', '--virtualsize', '4367354880B', '--name', 'rhvh-4.0-0.20170307.0', u'rhvh/pool00']' returned non-zero exit status 5 Expected results: It should give a detailed error message in imgbase logs. Additional info:- None
imgbased already logs detailed information in /tmp/imgbased.log or /var/log/imgbased.log, depending on the version. Are you expecting this to appear in RHVM, or just the stderr in the logs? 'imgbase check' should not be creating LVs.
Verify Steps: from rhvh-4.1-0.20180126.0 upgrade to rhvh-4.2.3.1-0.20180531.0 Results: upgrade failed due to no enough space stderr be captured in `imgbased.log` ``` 2018-06-04 05:47:26,650 [ERROR] (MainThread) Failed to migrate etc Traceback (most recent call last): File "/tmp/tmp.oscuVNMJKQ/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py", line 118, in on_new_layer check_nist_layout(imgbase, new_lv) File "/tmp/tmp.oscuVNMJKQ/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py", line 209, in check_nist_layout v.create(t, paths[t]["size"], paths[t]["attach"]) File "/tmp/tmp.oscuVNMJKQ/usr/lib/python2.7/site-packages/imgbased/volume.py", line 55, in create vol = self.imgbase._thinpool().create_thinvol(volname, size) ```
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/RHSA-2018:1820
BZ<2>Jira Resync