Description of problem: When running through the normal procedure to upgrade the RHN Satellite product without the OS, the upgrade script does not keep the non-default 'mount_point' and the 'kickstart_mount_point' parameters in /etc/rhn/rhn.conf In my test case, if both paths had been changed to /opt/satellite instead of /var/satellite the rhn.conf shows /var/satellite once the upgrade is complete. Version-Release number of selected component (if applicable): 5.4.1 and prior How reproducible: always
The issue described in this bug report will be resolved in the Satellite upgrades by instructing customers to: 1. create an answer file containing correct mount point (preparations.txt) 2. use the answer file in the Satellite upgrade (add --answer-file=... option when running install.pl --upgrade). satellite.git: 2ffe456a92cc32be2d74dbfbf5b3b09ef58eac20
This issue is resolved with the release of RHN Satellite 5.5. As of September 20th 2012, RHN Satellite 5.5 has been generally available. Release Notes and other 5.5 documentation can be found here: https://access.redhat.com/knowledge/docs/Red_Hat_Network_Satellite/ The associated Errata for the 5.5 release are: 5.5 Satellite GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1296.html 5.5 Upgrade Errata - http://rhn.redhat.com/errata/RHEA-2012-1298.html 5.5 RHN Proxy GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1297.html 5.5 RHN Tools GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1299.html Regards, Clifford - Engineering Manager, Satellite