Project

General

Profile

Actions

Bug #24790

closed

Instructions for paused tasks remediation are unclear

Added by Martin Bacovsky almost 6 years ago. Updated 4 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Check
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

During a health check I had some paused tasks. f-m was asking for my input to remediate the problem
but the possible choices are not obvious from what it printed.
On a first try I used the 'n' option and expected it to resume the tasks but it skipped the step (see below).
On a second attempt I tried '1' which worked, but was not listed in the available options.
I didn't tried '2' but now I'm curious ;)

# 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)] n
Check whether all services are running using hammer ping:             [OK]      
--------------------------------------------------------------------------------
Scenario [ForemanMaintain::Scenario::FilteredScenario] failed.

The following steps ended up in failing state:

  [foreman-tasks-not-paused]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="foreman-tasks-not-paused" 

Expected behavior would be to get list of reasonable options with clear description to remediate the unwanted situation.

Actions #1

Updated by Ivan Necas almost 6 years ago

Both 1 and 2 should work. I agree that listing them also in [] would help to better understand the options. Using s(skip) instead of n(next) might be better probably

Actions #2

Updated by Eric Helms 4 months ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF