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:
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
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.
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@
the satellite needs to be installed with @--foreman-proxy-plugin-remote-execution-ssh-async-ssh=true@ in order for this to work.
Created from redmine issue https://projects.theforeman.org/issues/26428
Upstream bug assigned to None
*** Bug 1691418 has been marked as a duplicate of this bug. ***
Upstream bug assigned to email@example.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26428 has been resolved.
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.