Bug 1187523 - 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
Summary: when doing in-place upgrade from 5.6.0@EmbPostgreSQL to 5.7.0, rhn.conf in /e...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Upgrades
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat570-triage
TreeView+ depends on / blocked
 
Reported: 2015-01-30 10:50 UTC by Jan Hutař
Modified: 2018-04-09 12:25 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

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.


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