Markus Boehme

As for the semi-random occurrence of the issue: The value-less key must not be the last line in the configured boot config. The order in which prairiedog writes out these...

>> I don't think a migration is needed as the setting is persisted and restored by prairiedog in the bootconfig initrd. Older versions of prairiedog will just ignore the setting....

> I don't quite understand the need to persist the `reboot-to-reconcile` flag within the actual bootconfig data. Originally, this is mainly a result of misunderstanding the serialization of `BootSettings`, i.e....

@bcressey I see what you mean now. This definitely looks and feels more as if made from one piece, and doesn't preclude bootstrap containers from signalling a need to reboot...

The force push changes the approach as discussed above: * The reboot now happens after reaching the `configured.target`, sidestepping the need to explicitly consider bootstrap containers and whether they're essential...

The latest force push contains these changes: * `reboot-if-required.service` now is `Type=oneshot` as it should have been, waiting for prairiedog to issue the reboot * Extracted a function to actually...

Thanks for the reviews! I force-pushed now to resolve the conflicts in `Cargo.toml` and `Release.toml`, unblocking the automated tests.

One more thing that this migration will be helpful for: Running Pubsys on EC2 instances with IMDS v1 disabled. Unfortunately, Rusoto doesn't support the two-step process (fetch token, query IMDS)...

Hi Chris, The recently released Bottlerocket v1.9.1 switched to the xz format for kernel module compression which, at least for now, is more widely supported than zstd. Please give it...

Confirmed patches match their upstream counterparts and the shim update included revokes the previous `grub` generation number. Ready to approve once test results are in. :racehorse: