Feature #11377
open
fail early if no proxy provider is found
Description
when initially setting up, I was able to invoke a job even if there was no proxy feature.
later on, finding that error was not trivial to detect. we should detect obvious errors before planning the tasks.
Updated by Ivan Necas over 8 years ago
- Related to Bug #11553: Long-taking connection to remote host (usually when the host is not unreachable) block ssh calls to other hosts added
Updated by Ivan Necas over 8 years ago
- Related to Feature #11584: Possibility to rerun job invocation on failed hosts added
Updated by Ivan Necas over 8 years ago
Part of the problem you were seeing was related to http://projects.theforeman.org/issues/11553, where the whole task was blocked by waiting for connection timeouts. After the fix (smart_proxy_remote_execution_ssh 0.0.4), the user should see much sooner that something is not working for some hosts.
Another thing to improve the bahavior might be http://projects.theforeman.org/issues/11584, when one would be just rerun the job on the failed hosts.
While it seems the ping mechanism might be useful, I'm not sure how many people would actually use it, if #11553 and #11584 implemented