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.
Bug 1531127 - Remote execution job with reboot/init commands always failed
Summary: Remote execution job with reboot/init commands always failed
Keywords:
Status: CLOSED DUPLICATE of bug 1500536
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1509033
TreeView+ depends on / blocked
 
Reported: 2018-01-04 16:04 UTC by Nikhil Kathole
Modified: 2018-01-22 12:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-09 15:22:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
content-host tracer page (42.52 KB, image/png)
2018-01-04 16:04 UTC, Nikhil Kathole 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1534967 0 high CLOSED reboot ReX fails with "Runner error: NameError - uninitialized constant ForemanRemoteExecutionCore::ScriptRunner::MAX_PR... 2023-09-15 00:06:07 UTC

Internal Links: 1534967

Description Nikhil Kathole 2018-01-04 16:04:03 UTC 
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)
Comment 4 Ivan Necas 2018-01-09 15:22:47 UTC 
There is a bug https://bugzilla.redhat.com/show_bug.cgi?id=1500536 that is supposed to get to ON_QA soon, I suggest closing this one as a duplicate + making sure to use the Poser Action template for rebooting to avoid the interruptions, as suggested in https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/host_configuration_guide/sect-Host_Configuration_Guide-Configuring_and_Running_Remote_Commands#exam-Host_Configuration_Guide-Including_Power_Actions_in_Templates

*** This bug has been marked as a duplicate of bug 1500536 ***
Note You need to log in before you can comment on or make changes to this bug.