Hey folks,
we are currently implementing systemd-boot boot assessment on Kairos, where we have a few entries under /loader/entries/
We made it so they start at threes tries so the config fails are for example active+3.conf
On boot, we can see the filename renamed properly to active+2-1.conf until the systemd-bless-boot starts, checks that the system is in complete boot (reached boot-complete.target) and it marks it as good and renames it to disable the boot assessment
Nov 21 13:08:10 kairos-vfog systemd[1]: Starting systemd-bless-boot.service - Mark the Current Boot Loader Entry as Good...
Nov 21 13:08:10 kairos-vfog systemd-bless-boot[1522]: Marked boot as 'good'. (Boot attempt counter is at 1.)
Nov 21 13:08:10 kairos-vfog systemd[1]: Finished systemd-bless-boot.service - Mark the Current Boot Loader Entry as Good.
Nov 21 13:08:10 kairos-vfog systemd-bless-boot[1522]: Marked boot as 'good'. (Boot attempt counter is at 1.)
Nov 21 13:08:10 kairos-vfog systemd[1]: Finished systemd-bless-boot.service - Mark the Current Boot Loader Entry as Good.
That's all good and dandy but now, our loader.conf is pointing to the active+3.conf as the default key, so that wont match anymore.
Should systemd-bless-boot update the default entry in loader.conf if it matches the current boot loader entry? Should systemd-boot ignore the boot assessment part in the loader.conf default?
Does loader.conf accept a regex for the default entry so this can be fixed by setting the entry to ^WHATEVER\+\d+(-\d+)?.conf$ ?
Cheers!
