Bug 2075642

Summary: add an option to reboot once onboarding is complete
Product: Red Hat Enterprise Linux 9 Reporter: Ben Breard <bbreard>
Component: fido-device-onboardAssignee: idiez
Status: CLOSED COMPLETED QA Contact: Xiaofeng Wang <xiaofwan>
Severity: unspecified Docs Contact: Eliane Ramos Pereira <elpereir>
Priority: unspecified    
Version: 9.0CC: amurdaca, elpereir
Target Milestone: rc   
Target Release: 9.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-27 07:37:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben Breard 2022-04-14 18:31:23 UTC 
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.
Comment 1 idiez 2023-03-03 10:20:43 UTC 
Done upstream: https://github.com/fedora-iot/fido-device-onboard-rs/pull/410