Bug #24779
closed
Remote execution fails with EXCEPTION
Added by Steven Blair over 6 years ago.
Updated about 4 years ago.
Category:
Smart Proxy Dynflow
|
|
Description
Any remote execution fails (both result and indication) with the following error.
1: Error initializing command: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::SmartProxyDynflowCore
2: Did you mean? SmartProxyReference
3: Exit status: EXCEPTION
This system lives in a black environment. Log extraction is tedious, but not impossible. If specific logs are needed, please specify and we will replicate failure and capture logs. The system has 3.7.1 patches applied to "75-job_templates.rb" and "remote_execution_controller.b" that fixed another issue but exposed this one.
- Status changed from New to Need more information
We don't support custom-patched installations (for obvious reasons). Is there a specific unmodified release (foreman version + rex version needed) where this issue is reproducible?
Also, what's the value of `Settings -> RemoteExecution -> Fallback Without Proxy' in the settings page?
I restored the configuration to OOB Foreman 1.18 with Katello 3.7. It now exhibits the earlier fault, qdrouterd fails to load dispatch extension module 'qpid_dispatch_internal.dispatch' and exits. That problem was resolved by downgrading to two versions earlier of all qpid packages.
The setting 'Settings -> RemoteExecution -> Fallback Without Proxy' is "yes", as there is no external proxy for this standalone system.
- Is duplicate of Bug #22960: NameError uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::SmartProxyDynflowCore when running REX from Foreman added
Thanks Adam for pointing to the duplicate issue I've already forgot about. Anyway, I recommend not using Fallback Without Proxy, as most of the production users are using the installer driven setup, which is enforcing having separate proxy for the job and we're actually considering removing this option from the rex, to reduce the count of possible code-paths to achieve the same thing.
- Status changed from Need more information to Rejected
Running jobs directly from foreman (without going through proxy) is not supported anymore.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by