here RJ, do the honors, I should be away from the buttons
here RJ, do the honors, I should be away from the buttons
EI JUST started mine and the notification came through hahaha
EWill do 
Bthis is weird... but not the same problem we had been concerned about:
https://github.com/ublue-os/bluefin/actions/runs/9571552636/job/26388921481#step:12:142
https://github.com/ublue-os/bluefin/actions/runs/9571552636/job/26388921481#step:12:142
GitHub
The next generation Linux workstation, designed for reliability, performance, and sustainability. - feat: Add kernel signer to sign Fedora kernel with ublue's keys for s… · ublue-os/bluefin...
KBanned banned none of you are free from sin
JLet us never speak of the noodle incident
KBe sure to play some Selaco when things calm down so you can unwind
BThis needs to be in the history books:
JI am on a work trip, unwinding is not in the cards this week
Jit would be nice to have like, just one uneventful kernel upgrade
Jsomeday
Bi gotta step away for work... 
J
EThe action is missing image as an input... how has it been working
KCarefully
EI'm going to restore it but now... I'm concerned. It's been parsing something somehow
Jwould it be easier to just pin to the older image/kernel?
EUnsure at this point. Fixed the input and incremented the signer in your PR. Let's see if this works. If not, let's pin an older kernel for now
JI think we'd need to backport bootupd to 39 to update people's bootloaders if I'm reading this issue right
EFedora really messed up here. Looks like the action failed. Can't connect to the registry :/. Exact same issue Bazzite had last month
EI think I see why
EBluefin images, when they're built, don't appear to be tagged with latest
EUnless they're built on main
EPR'd builds are tagged with the PR number
ELooking into it
Koh yeah, I thought this earlier
Kthen jorge merged
EThat's probably why it succeeded post merge
EBut failed in the PR
Kyeppo
EWe just need to tag them with gts/latest/etc in PRs as well. Will fix this
Rit's still not clear to me what fedora did here that caused the fuckup
Ri dont see anything indicating the kernel signing key changed?
Rplus i see people getting this issue on other kernel versions in that thread
KI am 3 badgers in a trench coat trying to get real work done, all I know is it works fine in bazzite and the only functional difference is the signing
Kbest we got atm
Ryup
Rwas more a curiosity than trying to get at a better solution
Ri'll keep digging
Fmakes me wonder if there are users who experienced this same issue on Ublue images before 6.9 kernel
Ryeah it's strange
JIt's in the upstream issue
JLinked in #bluefin, sorry landing now
Rthe root cause isn't specified here
Rthere's a comment from timothee "It's likely due to the bootloader being too old" but that's about it
Rand I don't see how that relates if changing the kernel signature fixes the issue
EThis should do the trick: https://github.com/ublue-os/bluefin/pull/1406/commits/77ae37b65609c5c258caaa7645b962db37c53f20
Bthat looks good, but still doesn't solve the signing failures in PR
EEmm... Worked for some of them
