Description of problem:

There's no clear way to reboot a system once onboarding is complete. There should be an optional way to define this behavior in the serviceinfo_api_server.yml config.

Version-Release number of selected component (if applicable):
8.6 & 9.0

fdo-owner-onboarding-server-0.4.5-1.el9_0.x86_64




Additional info:

If a command triggers a reboot, it's not clear if this will interrupt the onboarding process and start a boot loop. Also, it's unclear if commands are run in any order, regardless, executing a reboot command, or nesting it as an option for an rpm-ostree --reboot shouldn't be necessary, nor should scheduling an @ job.