Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: 

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/

Section Number and Name: 

Chapter 6. Upgrading Satellite Server and Capsule Server
6.2. Upgrading a Connected Satellite Server

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server

Describe the issue: step 2 is a critical part of the upgrade process, its an awesome checker for stuck tasks. What I find odd is that its step 2, and the actual upgrade starts on step 13.

There are multiple steps in between step2 and 13 that can cause the upgrade check script to be needed to run again.

ie step 10/11 asks you to sync repos, step 12 wants you to update any content views. 

Suggestions for improvement: run the upgrade check again before step 13

# foreman-rake katello:upgrade_check

Steps 3 through 12 can take a lot of time, things can happen like hosts check ins, sync tasks, ect.. we need to run that right before the upgrade so we can have a better chance of no stuck tasks during upgrade.

Additional information:

Assigning to Zac for review.

This content is live on the Customer Portal.

Closing.