Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1454884 - Disk space issues when running upgrade from 5.7 to 5.8
Disk space issues when running upgrade from 5.7 to 5.8
Status: CLOSED CURRENTRELEASE
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Build (Show other bugs)
5.8.0
Unspecified Unspecified
unspecified Severity high
: GA
: 5.9.0
Assigned To: Satoe Imaishi
luke couzens
black:upgrade:migration
: TestOnly, ZStream
Depends On:
Blocks: 1454889 1464203
  Show dependency treegraph
 
Reported: 2017-05-23 12:57 EDT by luke couzens
Modified: 2018-03-06 09:38 EST (History)
10 users (show)

See Also:
Fixed In Version: 5.9.0.1
Doc Type: Known Issue
Doc Text:
At current, upgrading from Red Hat CloudForms 4.1 or Red Hat CloudForms 4.2 to Red Hat CloudForms 4.5 might result in a disk space error when running 'yum update' after enabling the repositories for the Red Hat CloudForms 4.5 release. As a workaround, increase the size of the 'VG--CFME-lv_var' logical volume on the appliance by 1GB. This can be accomplished with the following commands: umount /dev/VG-CFME/lv_repo lvreduce --yes --size 1GB /dev/mapper/VG--CFME-lv_repo lvextend --resizefs --size +1GB /dev/mapper/VG--CFME-lv_var
Story Points: ---
Clone Of:
: 1464203 (view as bug list)
Environment:
Last Closed: 2018-03-06 09:38:29 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core


Attachments (Terms of Use)

  None (edit)
Description luke couzens 2017-05-23 12:57:19 EDT
Description of problem:When upgrading from 5.7 to 5.8 sometimes you receive disk space errors


Version-Release number of selected component (if applicable):5.8.0.16


How reproducible:33%


Steps to Reproduce:
1.provision 5.7
2.configure database
3.add provider
4.add latest repos
5.run yum update

Actual results:disk out of space


Expected results:update completes successfully without disk errors, or we need to add a section to the docs explaining how to resize the partition.


Additional info: My work around was as follows

umount /dev/VG-CFME/lv_repo
lvreduce --yes --size 1GB /dev/mapper/VG--CFME-lv_repo
lvextend --resizefs --size +1GB /dev/mapper/VG--CFME-lv_var
Comment 9 luke couzens 2017-10-11 10:51:25 EDT
Verified in 5.9.0.1

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