Project

General

Profile

Actions
Copy link

Bug #12220

closed

Undecipherable failure when Dynflow proxy is not available

Added by Daniel Lobato Garcia over 8 years ago. Updated almost 6 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Stephen Benjamin
Category:
-
Target version:
foreman_remote_execution 0.0.7
Difficulty:
trivial
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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 open — 1 closed)

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

Updated by Stephen Benjamin over 8 years ago

  • Assignee set to Stephen Benjamin
  • Target version set to 87
  • Difficulty set to trivial
Actions
Copy link
 #2

Updated by Stephen Benjamin over 8 years ago

  • Status changed from New to Duplicate

Actually the same issue as #12288, it's just because that bug is hiding the error. Once that's fixed you do actually get feedback in the UI that no proxy was available for that host. Marking this one dupe since #12288 includes the traceback.

Actions
Copy link
 #3

Updated by Stephen Benjamin over 8 years ago

  • Is duplicate of Bug #12288: Getting ugly error if no proxy can be used added
Actions
Copy link

Also available in: Atom PDF