Bug 1434446

Summary:	It should be possible to upgrade Satellite while coming from any PotsgreSQL version
Product:	Red Hat Satellite 5	Reporter:	Tomáš Kašpárek <tkasparek>
Component:	Upgrades	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ales Dujicek <adujicek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	580	CC:	adujicek, tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-web-2.5.2-11-sat spacewalk-utils-2.5.1-18-sat spacewalk-setup-postgresql-2.5.0-25-sat	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-21 12:15:05 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:	1393921

Description Tomáš Kašpárek 2017-03-21 14:08:34 UTC

Description of problem:
Satellite 5.7 will have its PostgreSQL upgraded to 9.5 so we can no longer rely on set PostgreSQL versions thus it should be possible to upgrade Satellite while coming from any PotsgreSQL version

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

Steps to Reproduce:
1. Upgrade PostgreSQL to 9.5 using 5.8 version of spacewalk-upgrade-postgresql
2. Upgrade 5.7 with new PostrgeSQL to 5.8

Actual results:
Upgrade fails because of unexpected version of PostgreSQL.

Additional info:
It should not matter which PostgreSQL version we are upgrading from. If the version is higher or equal to 9.5 spacewalk-upgrade-postgresql should be skipped.