Actions
Bug #24794
closedChecks are ordered incorrectly
Difficulty:
Triaged:
No
Description
For some reason the paused tasks check is run earlier then check for running services.
When e.g. dynflowd is stopped we are not able to resume the tasks prior it is started:
# foreman-maintain health check Running ForemanMaintain::Scenario::FilteredScenario ================================================================================ Check for verifying syntax for ISP DHCP configurations: [SKIPPED] DHCP feature is not enabled -------------------------------------------------------------------------------- Check for paused tasks: [FAIL] There are currently 2 paused tasks in the system -------------------------------------------------------------------------------- There are multiple steps to proceed: 1) Resume paused tasks 2) Investigate the tasks via UI Select step to continue, [n(next), q(quit)] 1 Resume paused tasks: [OK] Total tasks found paused in error state: 2 Total tasks resumed: 2 Resumed tasks: 1) Task identifier: 6ccb2370-d012-47fc-a7d3-133fc6c63e4d Task action: Pulp disk space notification 2) Task identifier: 4c68eabe-76c7-4698-9b6b-061e5f2eceba Task action: Pulp disk space notification Total tasks failed to resume: 0 Failed tasks: Total tasks skipped: 0 Skipped tasks: -------------------------------------------------------------------------------- Rerunning the check after fix procedure Check for paused tasks: [FAIL] ...
Expected behavior:
paused tasks are check only when we are sure all the services are up and running.
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Assignee set to Martin Bacovsky
- Pull request https://github.com/theforeman/foreman_maintain/pull/217 added
Updated by Anonymous over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_maintain|a454ac80eb565b188d083d7e1bcc5d9ab56220f1.
Updated by Ivan Necas over 5 years ago
- Fixed in Releases foreman_maintain-0.2.10 added
Actions