Bug 1187523

Summary:	when doing in-place upgrade from 5.6.0@EmbPostgreSQL to 5.7.0, rhn.conf in /etc/sysconfig/rhn/backup-<datetime> contains db connection setup only
Product:	Red Hat Satellite 5	Reporter:	Jan Hutař <jhutar>
Component:	Upgrades	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	570	CC:	greartes, 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:	2018-04-09 12:25:25 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:	1127217

Description Jan Hutař 2015-01-30 10:50:49 UTC

Description of problem:
When doing in-place upgrade from 5.6.0@EmbPostgreSQL to 5.7.0, rhn.conf in /etc/sysconfig/rhn/backup-<datetime> contains db connection setup only.


Version-Release number of selected component (if applicable):
Satellite-5.7.0-RHEL6-re20150108.2-x86_64
rhn-upgrade-5.7.0.25-1.el6sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Upgrade from 5.6.0@EmbPostgreSQL@RHEL6 to 5.7.0, no OS upgrade involved
2. Check content of backed-up rhn.conf:
   # cat /etc/sysconfig/rhn/backup-2015-01-30-08:49/etc/rhn/rhn.conf


Actual results:
# cat /etc/sysconfig/rhn/backup-2015-01-30-08:49/etc/rhn/rhn.conf
db_backend = postgresql
db_host = 
db_port = 
db_name = rhnschema
db_user = rhnuser
db_password = rhnpw


Expected results:
That file should much longer.


Additional info:
Initially mentioned in bug 1181763 comment #4 by François Cami - thanks

Comment 1 Tomas Lestach 2018-04-09 12:25:25 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.