Feature #14180
open
Unattended deployment with additional local boot step
Description
During the unattended deployment process I want the client to perform a local boot. If I just reboot the client it restarts the installation because Foreman does not know about the reason and delivers the same old boot file. If I wget the built-URL the client state switches to successfully installed and the client does the local boot. The problem is that the installation process is still running and might go south. That leads to a dysfunctional client that looks green and good in Foreman.
I think something like foreman_url('continue_local'), that switches the state to local boot, but installation still running would help. In a subsequent step the client then can signal the successful completion of the installation process with wgetting the built-URL.
Updated by Lukas Zapletal over 3 years ago
- Status changed from New to Need more information
- Triaged changed from No to Yes
Hello, I do not understand the request.
The foreman_url("built") is always called at the very end of installation, at least for Kickstart. The next step is reboot. Installer might live for few seconds, but the system really is in production mode and booting. Several other things can still happen during firstboot, this highly depends on configuration management deployed, however, from Foreman's perspective the host is no longer in build mode.