Project

General

Profile

Actions

Bug #12220

closed

Undecipherable failure when Dynflow proxy is not available

Added by Daniel Lobato Garcia over 9 years ago. Updated over 6 years ago.

Status:
Duplicate
Priority:
Normal
Category:
-
Difficulty:
trivial
Triaged:
Fixed in Releases:
Found in Releases:

Description

If you try to run a job invocation but there is no Smart Proxy with the Dynflow feature, the task will fail. Debugging the task from the user point of view is basically impossible as it doesn't contain any meaningful information. From the foreman administrator point of view, there's a log "Could not use any proxy. Consider configuring remote_execution_global_proxy or remote_execution_fallback_proxy in settings (RuntimeError)" with the error.

Verifying there's a proxy with these characteristics before running the job would be more user-friendly.


Related issues 1 (0 open1 closed)

Is duplicate of Foreman Remote Execution - Bug #12288: Getting ugly error if no proxy can be usedClosedIvan Necas10/23/2015Actions
Actions

Also available in: Atom PDF