Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#upgrading_a_disconnected_satellite
Section Number and Name:
Upgrade Disconnected Satellite Server
Describe the issue:
Since all Satellite services have been stopped in step 10, after that, some checks will be FAIL in "satellite-maintain upgrade check".
=========
10. Stop the satellite-maintain services.
# satellite-maintain service stop
=========
=========
4. Use the health check option to determine if the system is ready for upgrade. When prompted, enter the hammer admin user credentials to configure satellite-maintain with hammer credentials. These changes are applied to the /etc/foreman-maintain/foreman-maintain-hammer.yml file.
# satellite-maintain upgrade check --target-version 6.10 \
--whitelist="repositories-validate,repositories-setup"
=========
# satellite-maintain upgrade check --target-version 6.10 --whitelist="repositories-validate,repositories-setup"
Checking for new version of satellite-maintain...
Nothing to update, can't find new version of satellite-maintain.
Running preparation steps required to run the next scenarios
================================================================================
Setup hammer: [SKIPPED]
Satellite server is not running. Hammer can't be setup now.
--------------------------------------------------------------------------------
<snip>
--------------------------------------------------------------------------------
Check for HTTPS proxies from the database: [FAIL]
Please check whether database service is up & running state.
--------------------------------------------------------------------------------
Check number of fact names in database: [FAIL]
Please check whether database service is up & running state.
--------------------------------------------------------------------------------
Check whether all services are running: [FAIL]
Following services are not running: rh-mongodb34-mongod, rh-redis5-redis, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker, dynflow-sidekiq@worker-hosts-queue, foreman-proxy
<snip>
Scenario [Checks before upgrading to Satellite 6.10] failed.
The following steps ended up in failing state:
[warn-before-puppet-removal]
[https-proxies]
[foreman-fact-names]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="warn-before-puppet-removal,https-proxies,foreman-fact-names,repositories-validate"
Suggestions for improvement:
All services must be started before performing the upgrade check.
Additional information: