Project

General

Profile

Actions

Feature #26428

closed

Ability to restart the machine while the remote execution job is still acting as running - backend

Added by Ivan Necas about 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Found in Releases:

Description

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:

$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

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.


Related issues 2 (0 open2 closed)

Blocked by foreman-tasks - Feature #26691: Allow sending partial updates via smart_proxy_dynflowClosedIvan NecasActions
Blocked by foreman-tasks - Feature #26692: Allow sending partial updates from smart_proxy_dynflow to runnerClosedIvan NecasActions
Actions #1

Updated by Ivan Necas about 5 years ago

  • Description updated (diff)
Actions #2

Updated by Bryan Kearney about 5 years ago

  • Bugzilla link set to 1691453
Actions #3

Updated by Ivan Necas about 5 years ago

  • Blocked by Feature #26691: Allow sending partial updates via smart_proxy_dynflow added
Actions #4

Updated by Ivan Necas about 5 years ago

  • Blocked by Feature #26692: Allow sending partial updates from smart_proxy_dynflow to runner added
Actions #5

Updated by The Foreman Bot about 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ivan Necas
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/413 added
Actions #6

Updated by The Foreman Bot over 4 years ago

  • Fixed in Releases foreman_remote_execution 1.8.5 added
Actions #7

Updated by Ivan Necas over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions #8

Updated by Adam Ruzicka over 4 years ago

  • Fixed in Releases foreman_remote_execution_core 1.3.0 added
  • Fixed in Releases deleted (foreman_remote_execution 1.8.5)
Actions

Also available in: Atom PDF