Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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.
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
Comment 32Red Hat Bugzilla
2023-09-15 00:06:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
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.