Bug 1316630

Summary:	Satellite 5.6 s390x to 5.7 x86_64 upgrade fails
Product:	Red Hat Satellite 5	Reporter:	Ales Dujicek <adujicek>
Component:	Upgrades	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED ERRATA	QA Contact:	Ales Dujicek <adujicek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	570	CC:	tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-28 11:16:12 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:

Description Ales Dujicek 2016-03-10 16:11:24 UTC

Description of problem:

I cannot upgrade sat5.6@s390x to sat5.7@x86_64 both with emb. postgres

'Convert PostgreSQL data to new format' step fails with errors in
/var/lib/pgsql/pgstartup.log
2016-03-10 10:26:42.907 EST FATAL:  database files are incompatible with server
2016-03-10 10:26:42.907 EST DETAIL:  The database cluster was initialized with PG_CONTROL_VERSION 1258487808 (0x4b030000), but the server was compiled with PG_CONTROL_VERSION 843 (0x0000034b).
2016-03-10 10:26:42.907 EST HINT:  This could be a problem of mismatched byte ordering.  It looks like you need to initdb.

# /usr/bin/spacewalk-upgrade-postgresql
...
Installed:
  postgresql92-postgresql-upgrade.x86_64 0:9.2.10-2.el6    

 Dependency Installed:
  postgresql-server.x86_64 0:8.4.20-5.el6_7                                     

Dependency Updated:
  postgresql92-postgresql.x86_64 0:9.2.10-2.el6                                 
  postgresql92-postgresql-contrib.x86_64 0:9.2.10-2.el6                         
  postgresql92-postgresql-libs.x86_64 0:9.2.10-2.el6                            
  postgresql92-postgresql-pltcl.x86_64 0:9.2.10-2.el6                           
  postgresql92-postgresql-server.x86_64 0:9.2.10-2.el6                          

Complete!
Starting postgresql service: [  OK  ]
psql: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.

and second run
# /usr/bin/spacewalk-upgrade-postgresql --help
Loaded plugins: product-id, rhnplugin, security, subscription-manager
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Install Process
red-hat-satellite                                        | 2.1 kB     00:00 ... 
Package postgresql92-postgresql-upgrade-9.2.10-2.el6.x86_64 already installed and latest version
Nothing to do
Starting postgresql service: [FAILED]


Version-Release number of selected component (if applicable):
rhn-upgrade-5.7.0.26-1
spacewalk-dobby-2.0.3-23

How reproducible:
always

Steps to Reproduce:
follow /etc/sysconfig/rhn/satellite-upgrade/doc/satellite-and-os-upgrade-postgresql.txt upgrade instructions
1. db-control backup sat5.6@s390x
2. install sat 570 from iso on x86_64 machine
3. copy backup to the neew machine and db-control restore 
4. /usr/bin/spacewalk-upgrade-postgresql
at this step it fails to start postgresql service

Actual results:
upgrade step 'Convert PostgreSQL data to new format' fails with errors in
/var/lib/pgsql/pgstartup.log

Expected results:
No errors during upgrade

Additional info:
looks like issues with endianness in postgres backup

Comment 1 Tomáš Kašpárek 2016-03-21 10:22:35 UTC

As per discussion with PostgreSQL guys these upgrades are not possible due to way we do db-control backup (as we just pack all the binary data files), this would be possible if we'd been dumping the data.

So far adding documentation note in satellite.git(SATELLITE-5.7): 4f215fd196e653eb03c23ee6c0f19d1be1b4e357

Comment 5 errata-xmlrpc 2016-04-28 11:16:12 UTC

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, 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://rhn.redhat.com/errata/RHBA-2016-0698.html