Fedora Core failed to upgrade. "Expected commitmeta object, not DirMeta"

Ask Fedora
1

Hello guys, I have been using Fedora Core for a few months, and it always worked well for me.

However in the latest update(43.20251024.3.0, arch=x86_64, channel=stable), I cannot get my instance of Fedora Core upgraded, whether manually or by zincati service.

The error reports is always the same, saying that “error: Importing: Unencapsulating base: Importing commit: Using remote fedora for verification; Expected commitmeta object, not DirMeta”.

I installed my instance a few updates ago, when the update was through rpm packages, I ran a few command to switch to upgrading using container layers from quay.io. Which makes me wonder if there’s some command to fix this situation for me as well.

What I tried including pruning rpm-ostree cache and update again, which didn’t work for me.

So if you have any suggestion, I’d be willing to hear from you. Much thanks in advance.

2

Please provide the output of the rpm-ostree status command.

What are these commands and why did you execute them?

3

I started seeing this randomly too today.

[admin@myhost ~]$ sudo rpm-ostree upgrade --bypass-driver
Pulling manifest: ostree-remote-image:fedora:docker://quay.io/fedora/fedora-coreos:stable
Importing: ostree-remote-image:fedora:docker://quay.io/fedora/fedora-coreos:stable (digest: sha256:44528ecc3fe8ab2c2a4d0990cdc0898aca334aa632d4a77f23118f8900435636)
ostree chunk layers already present: 64
ostree chunk layers needed: 1 (1.6 MB)
custom layers needed: 1 (178 bytes)
[0/2] Fetching ostree chunk 1bd5d589fdb077fde3a (1.6 MB)... done
error: Importing: Unencapsulating base: Importing commit: Using remote fedora for verification; Expected commitmeta object, not DirMeta
[admin@myhost ~]$ sudo rpm-ostree status
State: idle
Deployments:
● ostree-remote-image:fedora:docker://quay.io/fedora/fedora-coreos:stable
                   Digest: sha256:29177c8a90b2102839a65571d2b60837c6bd78fdf167e2228dad41bae790712a
                  Version: 42.20250914.3.0 (2025-09-30T03:08:59Z)
          LayeredPackages: btop

  ostree-remote-image:fedora:docker://quay.io/fedora/fedora-coreos:stable
                   Digest: sha256:29177c8a90b2102839a65571d2b60837c6bd78fdf167e2228dad41bae790712a
                  Version: 42.20250914.3.0 (2025-09-30T03:08:59Z)
          LayeredPackages: btop
1 Like
4

The output of “rpm-ostree status” are as follows:

$ sudo rpm-ostree statusState: idleAutomaticUpdatesDriver: ZincatiDriverState: active; trying to stage 43.20251024.3.0 (failed attempts: 5)Deployments:● ostree-remote-image:fedora:registry:quay.io/fedora/fedora-coreos:stableDigest: sha256:1693b47dfccebdde19e81c3d0a0392010f0ec67e827f096d1b3f8aec662eb5cfVersion: 42.20251012.3.0 (2025-10-25T02:24:05Z)LayeredPackages: bc btop fail2ban firewalld genisoimage grubby man mosh nnn podman-compose policycoreutils-python-utils setools-console setroubleshoot-server tmux tree trivy udica vim

ostree-remote-image:fedora:registry:quay.io/fedora/fedora-coreos:stableDigest: sha256:1693b47dfccebdde19e81c3d0a0392010f0ec67e827f096d1b3f8aec662eb5cfVersion: 42.20251012.3.0 (2025-10-25T02:24:05Z)LayeredPackages: bc btop fail2ban firewalld genisoimage grubby man mosh nnn policycoreutils-python-utils setools-console setroubleshoot-server tmux tree trivy udica vim

The command for rebase was

sudo rpm-ostree rebase ostree-remote-image:fedora:registry:quay.io/fedora/fedora-coreos:stable --bypass-driver

Reason for that was the problem fixed in release 42.20250803.3.0, as stated in [https://github.com/coreos/fedora-coreos-tracker/issues/1890\]. I didn’t want to wait for an update, so I googled and did it myself.

5

Oh you’re getting a similar error to the one I’m getting!
I’m using the silverblue bootc image from quay.io
Can no longer upgrade F43 Silverblue bootc

6

Have you solved this problem?

7

No, but I believe this GitHub issue is related

8

There are two separate issues here.

@kenryo (and anyone else). For the booted deployment not found in the update graph issue, follow: Zincati: booted deployment not found in update graph for FCOS testing 43.20251110.2.0 (container/ostree-image-signed) · Issue #2066 · coreos/fedora-coreos-tracker · GitHub

For the Expected commitmeta object, not DirMeta issue. @yikai somehow you missed the container signing migration. Try running this command:

sudo systemctl stop zincati
sudo rpm-ostree rebase ostree-image-signed:docker://quay.io/fedora/fedora-coreos:stable --reboot
1 Like
9

For the Expected commitmeta object, not DirMeta issue, I’m getting a secondary error now. And also, this is pretty much a vanilla coreos install just sitting; I didn’t run any commands previously for this.

[root@node admin]# sudo systemctl stop zincati

[root@node admin]# sudo rpm-ostree rebase ostree-image-signed:docker://quay.io/fedora/fedora-coreos:stable --reboot
Pulling manifest: ostree-image-signed:docker://quay.io/fedora/fedora-coreos:stable
error: Preparing import: Fetching manifest: containers-policy.json specifies a default of `insecureAcceptAnything`; refusing usage

[root@node admin]# rpm-ostree status
State: idle
Deployments:
● ostree-remote-image:fedora:docker://quay.io/fedora/fedora-coreos:stable
                   Digest: sha256:29177c8a90b2102839a65571d2b60837c6bd78fdf167e2228dad41bae790712a
                  Version: 42.20250914.3.0 (2025-09-30T03:08:59Z)
          LayeredPackages: btop

  ostree-remote-image:fedora:docker://quay.io/fedora/fedora-coreos:stable
                   Digest: sha256:29177c8a90b2102839a65571d2b60837c6bd78fdf167e2228dad41bae790712a
                  Version: 42.20250914.3.0 (2025-09-30T03:08:59Z)
          LayeredPackages: btop
10

@nick123pig the container signing migration didn’t land until 42.20250929.3.0. You can deploy 42.20250929.3.0 and that should then migrate you properly I think.

sudo systemctl stop zincati
sudo rpm-ostree rebase ostree-remote-image:fedora:docker://quay.io/fedora/fedora-coreos:42.20250929.3.0 --reboot
11

@dustymabe that did it! Thank you!!

12

Thank you very much. This command worked for me!