Hide Forgot
Document URL: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server Section Number and Name: 6.2 Describe the issue: Our current installation guide rightly states: """ Supported upgrade paths for Satellite 6.2: * Satellite 6.1.9 GA or later to 6.2.X GA or later. """ What we do *not* require is that customers who are at 6.1.9 upgrade to 6.1.10, 6.1.11 or later. This adds an unnecessary step that adds additional risk to the upgrade as well as 2-4 hours of additional time required to get up to 6.2 Suggestions for improvement: We should make step 9.a/b/c optional: """ If you have new packages after updating: Ensure your Satellite Server is at the latest version. # katello-installer --upgrade If you have a new kernel after updating, reboot the system. If no reboot was required, ensure the Katello services are now running. # katello-service start """ and instead state: "If your Satellite is fully upgraded to 6.1.9 you do not need to update to a later version in 6.1.X and run katello-installer --upgrade, this step 9 can be skipped". Additional information:
Created MR: https://gitlab.cee.redhat.com/satellite-6-documentation/installation-guide/merge_requests/138
I think there should be a check provided to confirm the satellite they are running is on Sat v 6.1.9 GA. This will avoid any chances of upgrading satellite from 6.1.8 or previous versions to 6.2.x.
(In reply to Ashish Humbe from comment #2) > I think there should be a check provided to confirm the satellite they are > running is on Sat v 6.1.9 GA. This will avoid any chances of upgrading > satellite from 6.1.8 or previous versions to 6.2.x. As we do not know of an easy way to do that the extra steps which asks you to attempt to upgrade one last time using "katello-installer --upgrade" were added. Those are the steps "Update all packages" followed by "If you have new packages after updating" "katello-installer --upgrade". However, that step was added before 6.1.10 was released, then later updated to say it was optional by adding "If you have new packages after updating".
This content is live on the Customer Portal. Closing.