Bug 1382501 - Differences in Install guide and install script
Summary: Differences in Install guide and install script
Keywords:
Status: CLOSED DUPLICATE of bug 1187085
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Dobes
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 20:12 UTC by Diogo Henrique
Modified: 2016-10-07 14:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-07 14:36:58 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Diogo Henrique 2016-10-06 20:12:19 UTC
Description of problem:

In Satellite 5.7 documentation (https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/pdf/Installation_Guide/Red_Hat_Satellite-5.7-Installation_Guide-en-US.pdf), it explains the embedded database path do database change from /var/lib/pgsql (Wich is default in Satellite 5.6) to /opt/rh/postgresql92/root/var/lib/pgsql/.

But during running the installation script, it validates if we had enough space in /var/lib/pgsql, considering 12 gib free to follow installation (Default for /opt/rh/postgresql92/root/var/lib/pgsql/). I've grow my / filesystem to accommodate 12 gib and install satellite. During satellite-sync, i've notice the database are growing in /opt/rh/postgresql92/root/var/lib/pgsql/, so is the installation script wrong ?


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


How reproducible:

Yes


Steps to Reproduce:
1. Just try to install Satellite, downloading ISO from RedHat Access Portal
2.
3.

Actual results:

It try to validate the /var/lib path with enough space, not opt one, but during Satellite operation, it uses /opt


Expected results:

Install script should validate the /opt path with enough free/available space


Additional info:

RedHat Case Open, number 01716918

Comment 1 Tomas Lestach 2016-10-07 14:36:58 UTC
Right, there's a problem. This sounds like a duplicate of Bug 1187085.

*** This bug has been marked as a duplicate of bug 1187085 ***


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