Hide Forgot
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