Bug 1162737 - Installer --clear-db does not correctly default to postgres 92 if old postgres is installed
Summary: Installer --clear-db does not correctly default to postgres 92 if old postgre...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer
Version: 570
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat570-postga
TreeView+ depends on / blocked
 
Reported: 2014-11-11 15:29 UTC by Stephen Herr
Modified: 2018-04-09 11:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-09 11:33:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stephen Herr 2014-11-11 15:29:53 UTC
Description of problem:
I'm trying to re-install Sat 5.7 on a machine that was originally an upgrade from Sat 5.6 (so postgresql 8 is installed).

Actual results:
# ./install.pl --clear-db
* Starting Red Hat Satellite installer.
* Performing pre-install checks.
* Pre-install checks complete.  Beginning installation.
* RHN Registration.
** Registration: System is already registered with RHN.  Not re-registering.
* Checking for uninstalled prerequisites.
* Installing RHN packages.
* Now running spacewalk-setup.
* Setting up SELinux..
** Database: Setting up database connection for PostgreSQL backend.
** Database: Embedded database installation SKIPPED.
** Database: Populating database.
** Database: --clear-db option used.  Clearing database.
** Database: Shutting down spacewalk services that may be using DB.
** Database: Services stopped.  Clearing DB.
*** Progress: #
Could not populate database.

Investigation reveals that the "postgresql" service was running, not "postgresql92-postgresql" as expected. If I:
service postgresql stop
rm -rf /opt/rh/postgresql92/root/var/lib/pgsql/data
service postgresql92-postgresql initd
service postgresql92-postgresql start

then the install (without --clear-db) can proceed as normal.

Comment 2 Tomas Lestach 2018-04-09 11:33:56 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.


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