Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
Verified.
Tested on Satellite 6.7.5 with version rubygem-foreman_maintain-0.8.7-1.el7sat.noarch (from Satellite 6.10.0 Snap 10.0)
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 6.10 Satellite Maintenance Release), 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:4697