The fedora ostree repo does not look like it is refreshing so users of Silverblue and other ostree variants are not getting updates.
Ideally it would be fast because users need updates but it has been like this for a week already so not that urgent
nirik@ on IRC seems to be engaged trying to fix it, just filing this for tracking purposes
We need this at some point, sooner the better.
Fedora ostree variant users don't get any updates as the ostree repo is not refreshed
So output I got from ostree pull to showcase the issue:
ostree pull
sudo ostree pull fedora:fedora/38/x86_64/silverblue GPG: Verification enabled, found 1 signature: Signature made Mon 07 Aug 2023 08:44:59 PM using RSA key ID 809A8D7CEB10B464 Good signature from "Fedora <fedora-38-primary@fedoraproject.org>" 2 metadata, 0 content objects fetched; 788 B transferred in 0 seconds; 0 bytes content written
Related IRC conversation on #fedora-admin
<nirik> you can file a releng ticket... I'm looking and I think I see the problem <akdev> ok I will do that, I wasn't sure where to file the issue - thanks for that information! <akdev> I hope it is not hard to fix <nirik> looks like it might just be a config that wasn't pushed out. <nirik> trying that now... and thanks for noting it!
Yeah, we merged some PR's to fix things after branching, but those didn't get rolled out to bodhi-backend01, so it was still looking for f38 under Branched.
I've run the playbook and am doing a f38 updates push now.
ok. The push is done.
Can you confirm it looks ok now?
looks good from here:
sudo ostree pull fedora:fedora/38/x86_64/silverblue [sudo] password for akdev: GPG: Verification enabled, found 1 signature: Signature made Sat 12 Aug 2023 01:42:57 PM using RSA key ID 809A8D7CEB10B464 Good signature from "Fedora <fedora-38-primary@fedoraproject.org>" 247 metadata, 281 content objects fetched; 117346 KiB transferred in 2 seconds; 195.6 MB content written
The composes were failing due to various issues related to branching. Copy from a chat message in the Fedora Infra channel:
So it turns out that https://pagure.io/fedora-comps/pull-request/864 was merged before the packages reached the repos (https://src.fedoraproject.org/rpms/linux-firmware), and I synced this yesterday for Rawhide in https://pagure.io/fedora-comps/pull-request/867 and synced it for all Silverblue branches in https://pagure.io/workstation-ostree-config/pull-request/410 and related. Should I undo all the sync in Silverblue (that won't fix other composes) or should we "just" push the update to all Fedora releases, including the ones on Freeze? I'm not sure where the best place is to report this Hum, nevermind, it has been pushed recently to all releases and is pending just for F38 & 37 now: https://bodhi.fedoraproject.org/updates/?packages=linux-firmware So we should be good "soon"
So it turns out that https://pagure.io/fedora-comps/pull-request/864 was merged before the packages reached the repos (https://src.fedoraproject.org/rpms/linux-firmware), and I synced this yesterday for Rawhide in https://pagure.io/fedora-comps/pull-request/867 and synced it for all Silverblue branches in https://pagure.io/workstation-ostree-config/pull-request/410 and related.
Should I undo all the sync in Silverblue (that won't fix other composes) or should we "just" push the update to all Fedora releases, including the ones on Freeze? I'm not sure where the best place is to report this
Hum, nevermind, it has been pushed recently to all releases and is pending just for F38 & 37 now: https://bodhi.fedoraproject.org/updates/?packages=linux-firmware
So we should be good "soon"
You can see the compose failures in https://pagure.io/releng/failed-composes/issues.
All variants excepted for Onyx are now updated. Onyx is failing on dependency issues.
Metadata Update from @kevin: - Issue assigned to kevin
Great. Sorry for the trouble
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
maybe we sang victory a little too early, seems like F37 is still outdated:
sudo ostree pull fedora:fedora/37/x86_64/silverblue GPG: Verification enabled, found 1 signature: Signature made Mon 07 Aug 2023 10:25:05 PM using RSA key ID F55AD3FB5323552A Good signature from "Fedora <fedora-37-primary@fedoraproject.org>" 1861 metadata, 8223 content objects fetched; 689444 KiB transferred in 48 seconds; 1.5 GB content written
got this report from a F37 user, I originally only checked F38 ;-(
Metadata Update from @akdev: - Issue status updated to: Open (was: Closed)
This is a different issue.
f37/f38 updates composes failed yesterday.
"error: Packages not found: libertas-firmware"
so, some firmware change broke them... will try and figure out where.
This update needs to go stable: https://bodhi.fedoraproject.org/updates/FEDORA-2023-eabbf4ca4d
because there is already a change in comps to use it. I'll try and scare up karma.
Oh I see but if they failed yesterday why is the ostree repo showing August 7th? Shouldn’t it show August 20th or so?
The date is what led me to believe it might be related
Oh I see but if they failed yesterday why is the ostree repo showing August 7th? Shouldn’t it show August 20th or so? The date is what led me to believe it might be related
Yes I'm the F37 user that brought it to @akdev's attention, I'm still on a build dated August 8th.
This is what I wrote in https://pagure.io/releng/issue/11614#comment-868764
The update has finally been submitted for stable so we should have a compose tomorrow.
I did f37/f38 pushes this morning.
Can you confirm all looks ok now?
I did f37/f38 pushes this morning. Can you confirm all looks ok now?
Yes I see a new update now
F38 looks good:
printf '%s\n' kinoite silverblue sericea | xargs -tI{} sudo ostree pull fedora:fedora/38/x86_64/{} sudo ostree pull fedora:fedora/38/x86_64/kinoite GPG: Verification enabled, found 1 signature: Signature made Tue 22 Aug 2023 12:48:52 PM using RSA key ID 809A8D7CEB10B464 Good signature from "Fedora <fedora-38-primary@fedoraproject.org>" 2 metadata, 0 content objects fetched; 788 B transferred in 0 seconds; 0 bytes content written sudo ostree pull fedora:fedora/38/x86_64/silverblue GPG: Verification enabled, found 1 signature: Signature made Tue 22 Aug 2023 12:43:23 PM using RSA key ID 809A8D7CEB10B464 Good signature from "Fedora <fedora-38-primary@fedoraproject.org>" 2 metadata, 0 content objects fetched; 788 B transferred in 0 seconds; 0 bytes content written sudo ostree pull fedora:fedora/38/x86_64/sericea GPG: Verification enabled, found 1 signature: Signature made Tue 22 Aug 2023 12:43:01 PM using RSA key ID 809A8D7CEB10B464 Good signature from "Fedora <fedora-38-primary@fedoraproject.org>" 2 metadata, 0 content objects fetched; 788 B transferred in 0 seconds; 0 bytes content written
F37 too:
printf '%s\n' kinoite silverblue sericea | xargs -tI{} sudo ostree pull fedora:fedora/37/x86_64/{} sudo ostree pull fedora:fedora/37/x86_64/kinoite GPG: Verification enabled, found 1 signature: Signature made Tue 22 Aug 2023 12:47:59 PM using RSA key ID F55AD3FB5323552A Good signature from "Fedora <fedora-37-primary@fedoraproject.org>" 2 metadata, 0 content objects fetched; 788 B transferred in 0 seconds; 0 bytes content written sudo ostree pull fedora:fedora/37/x86_64/silverblue GPG: Verification enabled, found 1 signature: Signature made Tue 22 Aug 2023 12:43:57 PM using RSA key ID F55AD3FB5323552A Good signature from "Fedora <fedora-37-primary@fedoraproject.org>" 2 metadata, 0 content objects fetched; 788 B transferred in 0 seconds; 0 bytes content written
Great. Hopefully we are all back on track now.
Sorry for the weirdness...
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.