Ability to monitor whether a host is up or not, after a reboot through the remote execution feature.
|Target version:||Foreman - Team Ivan backlog|
|Velocity based estimate||-|
It would be nice to be able to make the job execution survive a restart (or a temporary
host disconnection in general) and continue with the script once it gets back.
For now, we were thinking about a special macro in job invocation that
the smart proxy would understand and would split the script into the subparts
to execute separately, with ability to wait for the host to be ready between
the executions, such as:
yum updtae -y reboot ### WAIT_FOR_RECONNECT ### echo 'Restarted after reboot' >> /etc/motd
This way the execution would be split into two parts, and the second part would be executed after the reboot happens. If the second part was missing (the `### WAIT_FOR_RECONNECT ###` would be the last line in the template, it would serve just as waiting for the reconnection, as required by this RFE.
The `### WAIT_FOR_RECONNECT ###` macro could be used multiple times in the job.
#1 Updated by Ivan Necas 12 months ago
- Subject changed from Ability to monitor whether a Unmanaged host is up or not, after a reboot through the remote execution feature. to Ability to monitor whether a host is up or not, after a reboot through the remote execution feature.
- Description updated (diff)
- Target version set to Team Ivan backlog