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-us/red_hat_satellite/6.3/html-single/upgrading_and_updating_red_hat_satellite/#updating_satellite_server_to_next_minor_version


Section Number and Name: 
4.1. Updating Satellite Server


Describe the issue: 
It is mentioned to use the satellite-installer command after doing the yum update:
"# satellite-installer --scenario satellite --upgrade"

And foreman-maintain is not mentioned.


Suggestions for improvement: 
Confirm if satellite-installer or foreman-maintain should be use for update and which was is fully tested and supported.


Additional information: 
If it is intentional to use satellite-installer for now, are we looking forward to use foreman-maintain so we can leverage the sanity check to make the process easier and less prone to error.

We show 6.2.z as an upgrade option even if we are in latest Satellite version which is great and will take care of aysnc errata upgrades too!  So I don't think we need any action from foreman-maintain at this point.  So just update the documentation to use foreman-maintain for *all* satellite upgrade processes. 


# rpm -q satellite
satellite-6.2.14-4.0.el7sat.noarch

# foreman-maintain upgrade list-versions
6.2.z
6.3

Hello

Thank you for raising this bug.

Hello

These changes are now live on the Customer Portal

4.1. Updating Satellite Server

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/upgrading_and_updating_red_hat_satellite/updating_satellite_server_capsule_server_and_content_hosts#updating_satellite_server_to_next_minor_version