Bug 874614 - Upgrade from Satellite 5.4.1 to 5.5.0 on RHEL 6 clobbers /etc/rhn/rhn.conf
Summary: Upgrade from Satellite 5.4.1 to 5.5.0 on RHEL 6 clobbers /etc/rhn/rhn.conf
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer
Version: 550
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 819027
TreeView+ depends on / blocked
 
Reported: 2012-11-08 14:29 UTC by Gary Titchmarsh
Modified: 2013-10-24 17:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-04 15:25:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1020667 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1020667

Description Gary Titchmarsh 2012-11-08 14:29:15 UTC
Description of problem:
Satellite upgrade re-creates /etc/rhn/rhn.conf with default values, moves old rhn.conf file to /etc/rhn/rhn.conf.orig

rpm upgrades would typically create .rpmnew instead of .orig.


Version-Release number of selected component (if applicable):


How reproducible:
Unknown, only have one Satellite box to upgrade. 

Steps to Reproduce:
1.Install RHEL 6.3
2.Install Satellite 5.4.1
3.Change mount points in /etc/rhn/rhn.conf away from default
4.Upgrade to Satellite 5.5.0 using upgrade option on script.
  
Actual results:

/etc/rhn/rhn.conf returned to RPM version with only Email carried across 

Expected results:

Upgrade script should honour all changes to /etc/rhn/rhn.conf as mount_point is not always default.


Additional info:

Comment 1 Clifford Perry 2013-07-04 15:25:15 UTC
Not a bug - as per this is expected behaviour. Within the rhn-upgrade RPM's text documentation for doing an upgrade we state to back everything up. We then have a step to say - review rhn.conf and restore custom settings. 

Cliff


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