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 1377017[details]
content-host tracer page
Description of problem: Running the remote execution job with commands such as init6, reboot, init 0 always failed and shows Runner error: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::MAX_PROCESS_RETRIES
Exit status: EXCEPTION
Version-Release number of selected component (if applicable): Satellite 6.3 snap 30
How reproducible: always
Steps to Reproduce:
1. Try to run remote execution job on host with command 'reboot'
2.
3.
Actual results: Command run successfully on host but Job failed with Runner error: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::MAX_PROCESS_RETRIES
Exit status: EXCEPTION
Expected results: Job should be green (should not show failed)
Additional info: The remote execution job always failed when you click on restart selected on page Content Hosts -> select host -> Traces having kernel and helper column shows "You will have to reboot your computer" (see attachment)
Created attachment 1377017 [details] content-host tracer page Description of problem: Running the remote execution job with commands such as init6, reboot, init 0 always failed and shows Runner error: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::MAX_PROCESS_RETRIES Exit status: EXCEPTION Version-Release number of selected component (if applicable): Satellite 6.3 snap 30 How reproducible: always Steps to Reproduce: 1. Try to run remote execution job on host with command 'reboot' 2. 3. Actual results: Command run successfully on host but Job failed with Runner error: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::MAX_PROCESS_RETRIES Exit status: EXCEPTION Expected results: Job should be green (should not show failed) Additional info: The remote execution job always failed when you click on restart selected on page Content Hosts -> select host -> Traces having kernel and helper column shows "You will have to reboot your computer" (see attachment)