consider running `bootupctl update` as part of firstboot
cgwalters opened this issue · 5 comments
Today the bootloader stack is updated outside of ostree - for us via https://github.com/coreos/bootupd/
But nothing runs that by default because it's not transactional.
OTOH today, for the initial provisioning of machines, the Ignition phase is definitely not transactional when it does things like repartitioning disks. So we might as well run bootupctl update by default as part of the firstboot phase.
A big big difference here between the "stock FCOS" and RHCOS flows is that for RHCOS (well, OCP, which includes OKD-using-FCOS) we always do this OS update before landing user workloads. So we'll always have the OS update available.
Ah but this definitely wants coreos/bootupd#108
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.