+++ This bug was initially created as a clone of Bug #1898108 +++ Description of problem: Upgrade can fail when not enough space is available to complete the upgrade to rh-postgresql12-postgresql-server. /var/lib/pgsql -> /var/opt/rh/rh-postgresql12/lib/pgsql Version-Release number of selected component (if applicable): Satellite 6.7 -> Satellite 6.8 How reproducible: 100% Steps to Reproduce: 1. Have not enough space available under /var/opt/rh/rh-postgresql12/lib/pgsql 2. Try upgrade 3. Actual results: No errors or warnings Expected results: Warning that not enough space is available before performing the upgrade Additional info: --- Additional comment from on 2021-04-06T12:10:35Z Upstream bug assigned to aupadhye --- Additional comment from on 2021-05-20T20:04:38Z Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32253 has been resolved.
Verified. Tested on Satellite 6.7.5 with version rubygem-foreman_maintain-0.7.11-1.el7sat.noarch (from Satellite 6.9.4 Snap1) Setup: 1. Have some data under /var/lib/pgsql (upgrade templates have ~565Mib data) 2. Create dir /var/opt/rh/rh-postgresql12/ and mount a partition of ~300Mib to this dir (less than /var/lib/pgsql) Steps: 1. # foreman-maintain upgrade check --target-version 6.8 OR 1. # foreman-maintain health check --label available-space-for-postgresql12 Observations: This check is only applicable for the pre-upgrade check of 6.7, which shows warnings if /var/opt/rh/rh-postgresql12/ available space is less than consumed space of /var/lib/pgsql, like -------------------------------------------------------------------------------- Check to make sure PostgreSQL 12 work directory has enough space for upgrade: [WARNING] Satellite 6.7 uses PostgreSQL 12. This changes PostgreSQL work directory to /var/opt/rh/rh-postgresql12/ The new work directory requires at least 565MiB free space for upgrade! --------------------------------------------------------------------------------
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 (Satellite Maintenance 6.9.4 Async Bug Fix Update), 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-2021:2947