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.
Some scenarios in rex involve need to disconnect from network and continue some work offline. While we have support for `async`, it still marks the job as failed when the managed hosts goes offline.
With this feature, we should be able to take control over the job status from the remote host, so that the job is marked as running even when the host goes down temporary as part of execution of the job.
Example of such a template:
<pre><code>$CONTROL_SCRIPT manual-mode
cat <<HELP | $CONTROL_SCRIPT update >/dev/null
The script has switched to manual-mode. It will be acting
as running after this script finishes.
The control script is available in \$CONTROL_SCRIPT
env varaible.
To send output data to the job, on can do something like this:
echo Hello world | $CONTROL_SCRIPT update
To mark the script as finished, one can do
$CONTROL_SCRIPT finish 0
there the second argument should be the exit code the
script ended with.
HELP
</code></pre>
After running this, one should be able to go to the remote host, reboot it and the job should still be running until @$CONTROL_SCRIPT finish 0@ is finished. Additional output can be sent to the job with @echo Hello world | $CONTROL_SCRIPT update@
Additional note:
the satellite needs to be installed with @--foreman-proxy-plugin-remote-execution-ssh-async-ssh=true@ in order for this to work.
Verified in sat 6.7 snap 10 using template '$CONTROL_SCRIPT manual-mode; <%= input("command") %>; $CONTROL_SCRIPT finish 0', for user input passing various sleeps and echos. Verified also that other rex functions are not affected by having --foreman-proxy-plugin-remote-execution-ssh-async-ssh enabled by default.
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-2020:1454
Some scenarios in rex involve need to disconnect from network and continue some work offline. While we have support for `async`, it still marks the job as failed when the managed hosts goes offline. With this feature, we should be able to take control over the job status from the remote host, so that the job is marked as running even when the host goes down temporary as part of execution of the job. Example of such a template: <pre><code>$CONTROL_SCRIPT manual-mode cat <<HELP | $CONTROL_SCRIPT update >/dev/null The script has switched to manual-mode. It will be acting as running after this script finishes. The control script is available in \$CONTROL_SCRIPT env varaible. To send output data to the job, on can do something like this: echo Hello world | $CONTROL_SCRIPT update To mark the script as finished, one can do $CONTROL_SCRIPT finish 0 there the second argument should be the exit code the script ended with. HELP </code></pre> After running this, one should be able to go to the remote host, reboot it and the job should still be running until @$CONTROL_SCRIPT finish 0@ is finished. Additional output can be sent to the job with @echo Hello world | $CONTROL_SCRIPT update@ Additional note: the satellite needs to be installed with @--foreman-proxy-plugin-remote-execution-ssh-async-ssh=true@ in order for this to work.