No updates since 39.20231205.0 #516
Comments
|
Can reproduce on Kinoite. |
|
same here: |
|
This is indeed super weird. We'll need to file an infra issue. |
|
This is probably unrelated, although I am experiencing same issue, but on top of that GNOME Software reports |
I'm having the same thing with GNOME software shows there's an available update, and appears to be installing it and offers to reboot, but it does nothing and the update is still there on reboot. Running rpm-ostree upgrade --preview shows there's an upgrade available to 2.38-14, but running rpm-ostree upgrade (no --preview or --check) shows it's fine. |
This is a known issue in rpm-ostree: coreos/rpm-ostree#1579 It pops up whenever base image updates are interrupted. See also: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1728 |
|
Can confirm. Two of my Fedora Silverblue instances stopped receiving updates since version 39.20231205.0. Also rpm-ostree is constantly busy doing nothing. Even |
|
Three options for workarounds until this is resolved:
|
|
Likely fixed with https://pagure.io/fedora-infra/ansible/pull-request/1697. We'll see tomorrow. |
not yet, I tried updating and I'm still on the same BaseCommit also this is not the first time it happens #475
that happened to me, at least in my case was gnome-software monopolizing the process (in a bad way) there are two solutions/workarounds for that:
|
|
I am still having this issue: ❯ rpm-ostree update --preview
1 metadata, 0 content objects fetched; 592 B transferred in 0 seconds; 0 bytes content written
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora rpmfusion-nonfree-nvidia-driver google-chrome rpmfusion-nonfree-steam phracek-PyCharm updates-archive
Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'rpmfusion-nonfree-nvidia-driver'... done
Updating metadata for 'google-chrome'... done
Updating metadata for 'rpmfusion-nonfree-steam'... done
Updating metadata for 'phracek-PyCharm'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264'; generated: 2023-03-14T10:57:01Z solvables: 4
rpm-md repo 'updates'; generated: 2023-12-13T01:20:39Z solvables: 15915
rpm-md repo 'fedora'; generated: 2023-11-01T00:12:39Z solvables: 70825
rpm-md repo 'rpmfusion-nonfree-nvidia-driver'; generated: 2023-11-30T17:20:04Z solvables: 29
rpm-md repo 'google-chrome'; generated: 2023-12-12T20:06:21Z solvables: 3
rpm-md repo 'rpmfusion-nonfree-steam'; generated: 2023-08-10T16:27:35Z solvables: 2
rpm-md repo 'phracek-PyCharm'; generated: 2023-08-10T15:35:19Z solvables: 5
rpm-md repo 'updates-archive'; generated: 2023-12-13T01:38:01Z solvables: 16689
Note: --check and --preview may be unreliable. See https://github.com/coreos/rpm-ostree/issues/1579
AvailableUpdate:
Upgraded: glibc-langpack-en 2.38-11.fc39 -> 2.38-14.fc39
gnutls-dane 3.8.2-1.fc39 -> 3.8.2-2.fc39
gnutls-utils 3.8.2-1.fc39 -> 3.8.2-2.fc39❯ rpm-ostree update
2 metadata, 0 content objects fetched; 788 B transferred in 1 seconds; 0 bytes content written
Checking out tree ae1afb4... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora rpmfusion-nonfree-nvidia-driver google-chrome rpmfusion-nonfree-steam phracek-PyCharm updates-archive
Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'rpmfusion-nonfree-nvidia-driver'... done
Updating metadata for 'google-chrome'... done
Updating metadata for 'rpmfusion-nonfree-steam'... done
Updating metadata for 'phracek-PyCharm'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264'; generated: 2023-03-14T10:57:01Z solvables: 4
rpm-md repo 'updates'; generated: 2023-12-13T01:20:39Z solvables: 15915
rpm-md repo 'fedora'; generated: 2023-11-01T00:12:39Z solvables: 70825
rpm-md repo 'rpmfusion-nonfree-nvidia-driver'; generated: 2023-11-30T17:20:04Z solvables: 29
rpm-md repo 'google-chrome'; generated: 2023-12-12T20:06:21Z solvables: 3
rpm-md repo 'rpmfusion-nonfree-steam'; generated: 2023-08-10T16:27:35Z solvables: 2
rpm-md repo 'phracek-PyCharm'; generated: 2023-08-10T15:35:19Z solvables: 5
rpm-md repo 'updates-archive'; generated: 2023-12-13T01:38:01Z solvables: 16689
Resolving dependencies... done
No upgrade available. |
|
I don't know if the today's compose happened yet. But I can confirm, still nothing over here too. 😢 |
You can query for the latest available image on the repo using
|
|
Building with unified core is fixed. The builds are still not pushed to the repo. Still needs more investigation. |
My bad I thought that it will get built today.
I misunderstood your message. |
I tried the second option. I also tried the first option which is rebasing on the latest nightly. ostree remote summary still shows the base from 5 dec 23 so that makes me think i might have to keep upgrading by rebasing regularly? I think I'll switch to ublue since they are unaffected and signed. I'm surprised how little attention this issue seems to be getting from what I can gather as a simple user. |
|
ublue images are based on the images listed in the first workaround. The second and third options are not going to get you updates but only a working podman if you are affected by the issue from the 4.8.0 release: #513. |
|
Hi, |
No ETA at this time; you can follow progress in the Fedora ticket - https://pagure.io/releng/issue/11827 |
|
I'm experiencing this same behaviour with the glibc update showing as always available but not receiving anything isnce 12-05-2023 So am I correct in understanding that we simply wait for the usual update mechanism to have a fix pushed remotely? Will it simply start working again or will there be some manual intervention required afterward? |
|
|
|
Hi, successfully upgraded now with lots of Packages to 39.20231215.1 Previous attempt ~~19:20 CET failed ( online 1 Package SDL2 Update) so it seems directly related to the fix. |
|
Should be good for Fedora 39. Fedora 38 will get its update tomorrow. |
Can confirm it's all good for me on Silverblue. Successfully updated using the |
|
Should be fixed for F38 & F39 now. Closing. |
and others
The composes seem to be finishing correctly, but
rpm-ostree upgradeisn't finding them. Notably, this means the fix for containers/podman#20872 hasn't gone out yet.https://kojipkgs.fedoraproject.org/compose/updates/Fedora-39-updates-20231208.0/logs/x86_64/Everything/ostree-1/create-ostree-repo.log
Side note:
Is that expected? I thought F39 was using unified core.
The text was updated successfully, but these errors were encountered: