Bug 650987

Summary:	Installer should not overwrite /etc/rhn/rhn.conf on upgrade
Product:	Red Hat Satellite 5	Reporter:	Luc de Louw <luc>
Component:	Installer	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	540	CC:	cperry, jpazdziora, msuchy
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-29 20:10:45 UTC	Type:	---
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:	462714

Description Luc de Louw 2010-11-08 15:31:17 UTC

Description of problem:
When upgrading a RHN Satellite from i.e 5.3 to 5.4, /etc/rhn/rhn.conf should not be overwritten.

Version-Release number of selected component (if applicable):
spacewalk-setup-1.2.6-5.el5sat

How reproducible:
Always

Steps to Reproduce:
1. /mnt/install.pl --upgrade
2. follow /etc/sysconfig/rhn/satellite-upgrade/satellite-upgrade.txt

Actual results:
/etc/rhn/rhn.conf got overwritten, ISS etc. must be configured again

Expected results:
having a /etc/rhn/rhn.conf.rpmnew

Additional info:

Comment 1 Clifford Perry 2010-11-17 19:49:09 UTC

The Satellite upgrade documentation does clearly state to review old rhn.conf and restore any previous custom settings that are no longer in the new rhn.conf file. 

satellite-and-os-upgrade.txt:17. Verify rhn.conf settings.
satellite-upgrade.txt:9. Verify rhn.conf settings.

As such, this is expected behavior and not a bug. If you wish to propose an enhancement to modify/improve the upgrade process to preserve settings over upgrade (vs manually doing it) - please do so. 

I'm willing to close as NOTABUG. But you may care to flip this into an enhancement request (RFE). Please let us know how you'd like to proceed?

Cliff

Comment 2 Luc de Louw 2010-11-17 22:06:41 UTC

Dear Cliff,

If there is a documentation about this, I've overseen it, I'm sorry for that. Nevertheless, best practice is to have a "config.rpmnew" if RPMs are upgrading stuff. 

The pseudo RPM "rhn-upgrade" also be integrated into http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.4/html/Installation_Guide/s2-upgrades-rhnup.html to have all doc in the same place.

At the end of the day it does not matter if you or I call this a bug or a RFE.

From a "RHEL Community" point of view I consider this as a bug, it is a bug of severity "medium" or even "low".

It is up to you, but I think it is good to have this "bug" or "non-bug" in mind when updating the documentation. 

Thanks,

Luc