Hide Forgot
Created attachment 1381950 [details] logs from Satellite Description of problem: Reboot ReX (content host details -> Traces -> check kernel -> Restart Selected) fails with "Runner error: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::MAX_PROCESS_RETRIES" Version-Release number of selected component (if applicable): satellite-6.3.0-23.0.el7sat.noarch How reproducible: always Steps to Reproduce: 1. Have system registered with remote execution SSH key deployed and with updated kernel 2. Go to Content host details -> Traces -> check "kernel" -> Restart Selected Actual results: System is restarted, but ReX job fails with "Runner error: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::MAX_PROCESS_RETRIES" Trace record for a "kernel" which needs to be restarted remains there. Expected results: Job should pass if restart worked (it worked for me) and trace item should go away. Additional info: Might not be related, but the client system I'm using have locale set to cs_CZ.UTF-8 in /etc/locale.conf.
I also ran into this problem. The Host reboots, which clears all of the traces, but the job status is "failed". I believe this happens because the job template "Restart Services - Katello SSH Default" runs a script that first executes a "reboot" then executes "katello-tracer-upload". The problem seems obvious, the script never finishes because the Host reboots. The "katello-tracer-upload" should probably be run on or shortly after boot. This looks like a template issue. The "Restart Services - Katello SSH Default" dynamically selects what action to take based on what services need to be restarted. If a service just requires a restart, then something like... systemctl restart service katello-tracer-upload ...would be performed. In the case of the Kernel, the template resolves to "reboot". reboot katello-tracer-upload The actual template is: <%= input(:helper).split(",").map {|split| "#{split}" }.join("\n") %> katello-tracer-upload Satellite version: $ rpm -q satellite satellite-6.3.0-23.0.el7sat.noarch Thanks Matt
Would like to know is there any update on this bug..
The issue remains in 6.3.1 This seems to ONLY effect RHEL 7 systems. 1: Runner error: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::MAX_PROCESS_RETRIES 2: Exit status: EXCEPTION ^ that is from a RHEL 7.4 system.
The issue remains in 6.3.3 Please let us know the FIX
Created redmine issue https://projects.theforeman.org/issues/26185 from this bug
Upstream bug assigned to inecas@redhat.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26185 has been resolved.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222