Duplicate Deployments in Fedora Silverblue

Ask Fedora
1

Hey folks,

I’m experiencing something weird with my Fedora Silverblue installation. When I check my system deployments, I see two almost identical entries:

State: idle
Deployments:
● fedora:fedora/41/x86_64/silverblue
                  Version: 41.20250413.0 (2025-04-13T00:45:16Z)
               BaseCommit: 7d303f49e8e40cecdc82583e02458501b488745e2089f80c8d641c254722bade
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
           LocalOverrides: ethtool 2:6.11-1.fc41 -> 2:6.14-2.fc41
                           kernel-tools-libs kernel kernel-core kernel-modules-extra python3-perf kernel-modules kernel-tools kernel-modules-core 6.13.10-200.fc41 -> 6.14.2-100.fc41
                           upower upower-libs 1.90.8-1.fc41 -> 1.90.9-1.fc41
          LayeredPackages: hstr nextcloud-client openssl yq
            LocalPackages: kyodialog-9:9.4-0.x86_64

  fedora:fedora/41/x86_64/silverblue
                  Version: 41.20250413.0 (2025-04-13T00:45:16Z)
               BaseCommit: 7d303f49e8e40cecdc82583e02458501b488745e2089f80c8d641c254722bade
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
           LocalOverrides: ethtool 2:6.11-1.fc41 -> 2:6.14-2.fc41
                           kernel-modules-core kernel-core kernel-modules-extra kernel-modules kernel-tools kernel-tools-libs kernel python3-perf 6.13.10-200.fc41 -> 6.14.1-100.fc41
                           upower-libs upower 1.90.8-1.fc41 -> 1.90.9-1.fc41
          LayeredPackages: hstr nextcloud-client openssl yq
            LocalPackages: kyodialog-9:9.4-0.x86_64

  fedora:fedora/41/x86_64/silverblue
                  Version: 41.20250405.0 (2025-04-05T00:45:42Z)
               BaseCommit: 50cc3b76069e43408e60c0e246e27ff0ffdfce3357a75180890b78b532b26d96
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
           LocalOverrides: kernel-tools-libs kernel kernel-modules-extra python3-perf kernel-modules-core kernel-core kernel-modules kernel-tools 6.13.9-200.fc41 -> 6.13.5-200.fc41
          LayeredPackages: gnome-console hstr nc nextcloud-client openssl yq
            LocalPackages: kyodialog-9:9.4-0.x86_64
                   Pinned: yes

Questions:

  • Why do I have these duplicate deployments?
  • Is this a normal behavior in Silverblue?
  • Has anyone else seen something similar?
2

Does this happen every time you upgrade?

I think this could happen if there’s a change that is applied that doesn’t include an upgrade to the base rpm-ostree commit.

For instance, perhaps one of your layered packages had an update, but nothing else did. Or making a change to the kernel arguments would create a new deployment without a change to the base commit.

3

Based on the information you provided, it appears that the kernel override in one deployment is 6.13.10-200.fc41 -> 6.14.2-100.fc41, and in the other it is 6.13.10-200.fc41 -> 6.14.1-100.fc41. So you probably have two different overridden kernel versions and therefore two different deployments.

4

I don’t know exactly when this happens, but I have noticed it several times now. Today I installed a new kernel and upower to test whether my problem with the graphics card persists.

I would only have expected the BaseCommit to change then but this is probably only for the entire image without changes.

5

The base commit is the commit of the base image your changes are applied on top. If you want to see the commit for each deployment, you can use rpm-ostree status --verbose or rpm-ostree status --json.

1 Like