Bug 1173899

Summary: 5.6.0 with external PostgreSQL to 5.7.0 with external PostgreSQL in-place upgrade fails: Could not connect to the database.
Product: Red Hat Satellite 5 Reporter: Jan Hutař <jhutar>
Component: UpgradesAssignee: Jan Dobes <jdobes>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Hutař <jhutar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 570CC: tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-setup-2.3.0-12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-13 10:25:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1128174    

Description Jan Hutař 2014-12-13 20:56:24 UTC
Description of problem:
When i attempt to upgrade from 5.6.0 with external PostgreSQL to 5.7.0 with external PostgreSQL (in-place, no OS upgrade) both `./install.pl --upgrade --run-updater` and `./install.pl --upgrade --run-updater --external-postgresql` fails: Could not connect to the database.


Version-Release number of selected component (if applicable):
Satellite-5.7.0-RHEL6-re20141212.0-x86_64
rhn-upgrade-5.7.0.15-1.el6sat.noarch


How reproducible:
2 of 2 attempts


Steps to Reproduce:
1. Have Satellite 5.6.0 with external PostgreSQL on RHEL6
2. Run either `./install.pl --upgrade --run-updater` or `./install.pl --upgrade --run-updater --external-postgresql`


Actual results:
# grep db_ /etc/rhn/rhn.conf 
db_backend = postgresql
db_user = spacesatuser
db_password = spacesatpw
db_name = spacesatschema
db_host = guest
db_port = 5433
# /mnt/tmp/install.pl --upgrade --run-updater
* 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.
* Upgrade flag passed.  Stopping necessary services.
* Purging conflicting packages.
* Checking for uninstalled prerequisites.
* Installing RHN packages.
* Now running spacewalk-setup.
* Setting up SELinux..
** Database: Setting up database connection for PostgreSQL backend.
Could not connect to the database.  Your connection information may be incorrect.  Error: DBI connect('dbname=rhnschema','rhnuser',...) failed: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/tmp/.s.PGSQL.5432"? at /usr/share/perl5/vendor_perl/Spacewalk/Setup.pm line 1742

Hostname (leave empty for local)? ^C   
# /mnt/tmp/install.pl --upgrade --run-updater --external-postgresql
* 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.
* Upgrade flag passed.  Stopping necessary services.
* Purging conflicting packages.
* Checking for uninstalled prerequisites.
* Installing RHN packages.
* Now running spacewalk-setup.
* Setting up SELinux..
** Database: Setting up database connection for PostgreSQL backend.
Could not connect to the database.  Your connection information may be incorrect.  Error: DBI connect('dbname=rhnschema','rhnuser',...) failed: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/tmp/.s.PGSQL.5432"? at /usr/share/perl5/vendor_perl/Spacewalk/Setup.pm line 1742

Hostname (leave empty for local)? ^C


Expected results:
When I (based on resolution of bug 1173837) run `./install.pl --upgrade --run-updater` or `./install.pl --upgrade --run-updater --external-postgresql`, DB should be discovered automatically by install.pl


Additional info:
When I have entered DB connection info, upgrade continued as expected.

Comment 5 Clifford Perry 2015-01-13 10:25:57 UTC
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is
being moved to a Closed Current Release state. 

The Satellite 5.7 GA Errata:
 - https://rhn.redhat.com/errata/RHSA-2015-0033.html 

Satellite 5.7 Release Notes:
 -
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html

Satellite Customer Portal Blog announcement for release:
 - https://access.redhat.com/blogs/1169563/posts/1315743 

Cliff

NOTE: This bug has not been re-verified (moved to RELEASE_PENDING) prior to release. We assume that the bug has indeed been fixed and not regressed since we initially verified it. Please re-open in the future if needed.