I noticed an issue when chain-building the kernel a few days ago where the kernel didn't get assigned to the secure-boot channel. I filed a koji issue since I wasn't sure what the problem was. Based on the response on the ticket, it sounds like a Fedora policy thing. Builds and such are linked on the Koji ticket.
No specific date, it's not urgent.
I guess when we stop using Koji or the kernel
Minimal, I just can't be lazy and chain-build.
This will require updating Koji hub policy.
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on Assignee (was: Needs Review)
We are likely going to update it anyhow for the coreos-continious stuff, might as well add this in too. :)
Metadata Update from @mizdebsk: - Issue assigned to mizdebsk
Fixed in ansible.git commit 0fc00d4. I've deployed the fix in staging Koji only and verified that it fixes the issue. The fix will be deployed in production on Wednesday during scheduled Koji maintenance (ticket #7700).
This should be live now.
Please let us know if it doesn't fix things.
:currency_exchange:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.