should we just pin the last known kernel for now?
should we just pin the last known kernel for now?
JI can back this out.
KNot a bad way to go
KBut let's see if this works
KShould be there anyway
Blet's watch it
Jit failed already, same issue
Jdoes anybody remember how to pin a kernel?
EI think we need to fetch it from Koji and do an override replace?
Bthat's how pin/rollback of package works, yes
JI have no idea how to do this, does someone have cycles to help out?
Jlooks like if we had a newer bootupd it might have helped
Rit's probably less jank at that point to pin the entire upstream image
EI'm taking a look but more eyes would be appreciated
Jyeah that might be a better idea
Jjust pin the entire thing lol
KFiguring out why your action can't connect to the local registry in bluefin would also help
KSince bluefin should be signed with the akmod key anyway
EI'll start there
Byep @EyeCantCU, the local registry issue is what blocked signing in bluefin
EAm I looking at the wrong job right now? It looks like it was able to pull and sign the image: https://github.com/ublue-os/bluefin/actions/runs/9571552636/job/26388915091#step:12:478
Bok, well maybe @j0rge simply reverted too quickly
Bit was failing in the PR builds, but you are right, that looks correct
ELet's revert the revert?
Jlol
Jok so am i reverting the revert?
Byeah, the failures i saw on the non-reverted PR merge (getting confusing now) were not the kernel signing
Byes, i think it should work
KSee this is what happens when I go to lunch
Elmao
JJhere 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
