Description of problem: There various issues in managed-db-upgrade.txt document with various importance. IMO nothing too important. Version-Release number of selected component (if applicable): rhn-upgrade-5.7.0.16-1.el6sat.noarch How reproducible: always Steps to Reproduce: 1. # less /etc/sysconfig/rhn/satellite-upgrade/doc/managed-db-upgrade.txt Actual results: * the file is not linked from anywhere: # grep -r managed-db-upgrade.txt /etc/sysconfig/rhn/satellite-upgrade <no output> * there should be step ensuring the system is in correct channel (noted that when I have seen bug 1027708) * "you will need: ... 2. A separate machine running managed DB instance." - when I'm upgrading, I already have that machine. Most probably I need just and root access to the machine * "Overview" says "1. Upgrade the stand-alone Red Hat Satellite database.", text below says "1. Install the stand-alone Red Hat Satellite database." * text in step 1 talks about "To install the stand-alone..." but I guess "To upgrade the stand-alone..." was meant * maybe some warning that Satellite services should be stopped should be included? Expected results: Mostly that file is cross-linked with rest of documentation (README at least) and I guess the other comments above (at least some of them) should be fixed as well
OK, doc/preparations.txt do not consider upgrade scenario of Managed -> Managed. There is: 6. Install managed PostgreSQL database. If for your Satellite 5.7, you have chosen a multi-server installation option (managed PostgreSQL database on a separate system), you need to install the managed database first. If your upgraded Satellite will be using embedded PostgreSQL, external PostgreSQL or external Oracle database, you may safely skip this step. To install the managed PostgreSQL database, please follow the instructions in: doc/managed-db.txt There should be some "if" there for new installs vs. upgrades.
satellite.git(SATELLITE-5.7): 848bae8b471e867afcbcfbf9912cc02304cbe1f2
in regard to comment 1 satellite.git(SATELLITE-5.7): 2c564a3d8e78de5327765de05791f7efe9e94118
in regard of: there should be step ensuring the system is in correct channel (noted that when I have seen bug 1027708) in comment 0 this looks like docs bug to me, we don't mention that in any part of upgrade documentation
(In reply to Tomáš Kašpárek from comment #4) > in regard of: there should be step ensuring the system is in correct channel > (noted that when I have seen bug 1027708) in comment 0 > this looks like docs bug to me, we don't mention that in any part of upgrade > documentation Well, we do activate Satellite using rhn-satellite-activate in all scenarios and also have step there to deactivate OLD satellite in case of OS upgrade scenarios. I'm fully fine with just linking to different documentation with generic statement like "Make sure you are in correct Managed DB channel.", but I consider it important (because of possible updates going into the channel).
Reverified with rhn-upgrade-5.7.0.22-1.el6sat.noarch.rpm
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state. The Satellite 5.7 GA Errata: - https://rhn.redhat.com/errata/RHSA-2015-0033.html Satellite 5.7 Release Notes: - https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html Satellite Customer Portal Blog announcement for release: - https://access.redhat.com/blogs/1169563/posts/1315743 Cliff