The 'satellite-maintain upgrade list-versions' command does not show next upgradable version in Red Hat Satellite 6

Environment

• Red Hat Satellite 6

Issue

• When attempting to update Red Hat Satellite to the latest minor version, say Red Hat Satellite 6.10 to Red Hat Satellite 6.10.z, satellite-maintain exits with the following warning:

Can't set target version 6.10.z, 6.10 already in progress

• When attempting to upgrade Red Hat Satellite to the next major release, say from Red Hat Satellite 6.10, can not see the Red Hat Satellite 6.11 version available :

# satellite-maintain upgrade list-versions
6.10

Resolution

It is important to understand the cause of this situation and the current system state to determine the proper resolution steps.

• If the problem is upgrading from version 6.10 to 6.11, then refer to this solution article.

• If the problem is upgrading from version 6.11 to 6.12, then refer to this solution article.

When none of the above helps then,

• Verify the following:

  • The last execution of satellite-maintain upgrade run was not completed successfully, additional troubleshooting was required and then re-execution of satellite-installer completed the upgrade.

  • The last failed satellite-maintain upgrade run was never successfully re-executed.

  • The content of /var/lib/foreman-maintain/data.yml shows the progress status of the last failed upgrade.

  • The latest version of the satellite-maintain and rubygem-foreman_maintain packages are installed on the system from the expected satellite-maintenance repository.

• If all of the above are true, then perform the following steps:

  # mv /var/lib/foreman-maintain/data.yml{,.bakup}
  # satellite-maintain upgrade list-versions
  

If further investigation is required, Open a new This content is not included.support case and proactively upload the following files from the affected Red Hat Satellite server :

• The SOS Report
• The /var/lib/foreman-maintain/data.yml file

For more KB articles/solutions related to Red Hat Satellite 6.x Installation/Upgrade/Update Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Installation/Upgrade/Update Issues.

Root Cause

Some of the scenarios that can result in this situation explained below:

• Most likely, a previous execution of the satellite-maintain upgrade run was not completed successfully and failed on some unexpected step. When the underlying problem was manually fixed and the upgrade was completed without re-executing the satellite-maintain upgrade run command, then the /var/lib/foreman-maintain/data.yml file will have incomplete information about the previous upgrade attempt, tricking the tool to think that the upgrade is still in progress.

• End-users would sometimes miss updating the rubygem-foreman_maintain package from the expected repository leaving the satellite-maintain tool unaware of the next upgradable version.

There could be some other possible scenarios as well and the root cause may vary, thus the importance of investigating them further to address the underlying issue rather than applying any workarounds.

Diagnostic Steps

• In Satellite 6, the data.yml file should look something like this i.e.

    $ cat /var/lib/foreman-maintain/data.yml
    ---
    :default: {}
  

  However, in the problematic Red Hat Satellite 6.10 server, we get to see this :

   $ cat /var/lib/foreman-maintain/data.yml
    ---
  upgrade_6.10:
   :serialized:
     :phase: :migrations
       :scenarios:
         :pre_upgrade_checks:
           :label: :satellite_6_10_pre_upgrade_check
         :steps:
           - :label: :foreman_proxy_verify_dhcp_config_syntax
            :param_values: {}
            :status: :skipped
     ....

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.