Red Hat Bugzilla – Bug 1464203
Disk space issues when running upgrade from 5.7 to 5.8
Last modified: 2017-08-02 13:33:18 EDT
What exactly am I verifying here?
I mean I can confirm that the new 5.8.1 image has the new partition configuration, but that does not solve the current disk space issue during upgrades.
Do I either need to confirm the additional commands to changing the disk partitions manually, (these commands still need to be added to the upgrade docs)
or is it a case of performing the upgrades with backup and restore options so we get the new partition configuration? (this would need to be done on all upgrades and updates i.e 5.6-5.8.1, 5.7-5.8.1 and 220.127.116.11 to 5.8.1)
As far as I know, no code change is expected for the existing appliances.
Not sure if we have a doc BZ or not - if we don't, it's probably a good idea to use this BZ to confirm the doc change as well so we cover both new and existing deployments.
Andrew - can you please provide the status for the doc change?
Just to clarify the steps listed in that 'Known_issues' link were just a quick work around and not the official steps we should add to the upgrade documentation.
Here are the revised ones.
yum -y install xfsdump
xfsdump -F -f /tmp/repo /repo
lvremove -f /dev/VG-CFME/lv_repo
lvcreate --yes -L 1GB -n lv_repo VG-CFME
mount /dev/VG-CFME/lv_repo /repo
xfsrestore -f /tmp/repo /repo
lvextend --resizefs --size +9GB /dev/VG-CFME/lv_var
Marking this as verified.
The above steps have been added to the documentation and tracked in #1467461, I have also tried and tested them and confirmed they work.
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.