Fixes #35379 - Kickstart callback home in the first boot service

[stejskalleos]

Follow up to #9677 (credits @Dyrkon )

Move the callback home with the facts update to the first boot service.

• The callback now really means done & running.
• Subscription manager reports facts from the running system

Tested with CentOS Stream 10

[chris1984]

@stejskalleos I had a question:
The first_boot_script.sh file contains the Foreman orchestration URL, which includes the JWT, should we keep that on the disk or setup systemd to self-destruct it after the first boot service?

[Service]
# Add a cleanup line to remove the script containing the token
ExecStartPost=/usr/bin/rm -f /root/first_boot_script.sh
ExecStartPost=/usr/bin/systemctl disable first_boot_service

[sbernhard]

wouldn't it stay in a boot loop because the boot config would stay to boot from network and not start from disk?
This is actually the case from SLES for example if the "built" callback will not run after the host installation. foreman need to put the host out of the build mode.

actually, I would prefer to have a second stage:

• built => change the boot order so that the host boot from disk instead of starting the network installation
• initialized => now the host is really up => e.g. remove the puppet "autoaccept CSR"

[stejskalleos]

The first_boot_script.sh file contains the Foreman orchestration URL, which includes the JWT, should we keep that on the disk or setup systemd to self-destruct it after the first boot service

Yes, deleting the file is a good idea.

wouldn't it stay in a boot loop because the boot config would stay to boot from network and not start from disk?

Hmm, you are right, wondering why my setup didn't stay in the loop.