Open mritsurgeon opened 10 months ago
Thanks for the suggestion!
Can you please elaborate on how this would be beneficial for your use case?
Automatically rebooting server then waiting for it to be available and then starting with next task , all controlled via one playbook run , as the example I shared which I modified to use , I’m running a UI that’s calling playbook in backend & passing variables , without auto reboot I’ll have to code a reboot button in UI. Simple Boolean Syntax can be passed to playbook through a tick box.
If a server needs reboot now you need to manually reboot it & the rerun playbook, what I suggested and sample is playbook initiates reboot then waits then continues.
Thanks for the additional info.
So in most places in this collection a reboot already occurs when needed. The only exception to that is in the pre-checks.
I left this at a fail as I expected the user to code to check for a pending reboot before initiating an install/upgrade to their Veeam environment. I was hesitant to include an automatic reboot here at the beginning in case jobs are still running or there is some other unforeseen environment change. For example, if someone had neglected to reboot after Windows updates, the reboot could take quite some time.
For the time being, I recommend checking for a pending reboot prior to executing a Veeam install/upgrade.
install_VBR.yml
Example Playbook :