-
Bug
-
Resolution: Done-Errata
-
Normal
-
6.15.z
-
False
-
-
False
-
foreman_maintain-1.7.3
-
0
-
-
-
Moderate
-
None
Description of problem:
Currently, `foreman-maintain health check` runs the following checks:
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check number of fact names in database: [OK]
--------------------------------------------------------------------------------
Check whether all services are running: [OK]
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [OK]
--------------------------------------------------------------------------------
Check for paused tasks: [OK]
--------------------------------------------------------------------------------
Check whether system is self-registered or not: [OK]
--------------------------------------------------------------------------------
however, when the db is down, it shows:
Setup hammer: Configuring Hammer CLI...
This is kind of misleading and people have no clue what went wrong. Same thing when doing the upgrade check.
How reproducible:
Easy
Is this issue a regression from an earlier version:
no
Steps to Reproduce:
1. stop the PostgreSQL service
2. run `foreman-maintain health check` or `satellite-maintain upgrade check --target-version 6.x.z`
Actual behavior:
The command stops at configuring hammer. An error message appears, such as:
Setup hammer: [SKIPPED] Satellite server is not running. Hammer can't be setup now.
Expected behavior:
'Check whether all services are running: ' should be checked first.
"Business Impact / Additional info:
- links to
-
RHBA-2024:140284
Important: Satellite 6.16.0 release
