Rebasing to specific version fails

[cgcomer]

Describe the bug

I've been having issues with Bazzite not updating which may be related to this issue #1239. I have attempted several things including this and this to no avail.

Finally, I decided to attempt to rebase to a specific version of Bazzite (40-stable-20240703).

ccomer@main-bazzite:~$ rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:40-stable-20240703
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:40-stable-20240703
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:40-stable-20240703 (digest: sha256:72409340a00bb68365b9863d719c0228c75b08c85073a570a47708625e6a6a6a)
ostree chunk layers already present: 65
custom layers already present: 4
error: Importing: Checking out base commit: Opening content object 77aef39c4ce71b37b26aa6f879f6593872eebf5eeafea29b6ccefb2aaecb79ea: Couldn't find file object '77aef39c4ce71b37b26aa6f879f6593872eebf5eeafea29b6ccefb2aaecb79ea'

As you can see, it immediately failed with an error I can't find good information on.

What did you expect to happen?

To complete a rebase to a specific version of Bazzite stable.

Output of rpm-ostree status

ccomer@main-bazzite:~$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:99cce7eb105cbdc027f1c72399a9ef88458818eeae7a172bbbdc8bb14d2bb22a
                  Version: 40.20240611.0 (2024-06-11T17:00:05Z)
          LayeredPackages: edk2-ovmf qemu virt-manager
            LocalPackages: lact-0.5.4-0.x86_64
                Initramfs: regenerate

Hardware

Operating System: Bazzite 40
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.8.12-301.fsync.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT
Manufacturer: ASUS
Asus Crosshair Hero VIII Wifi
Installed Main Drive: Samsung SSD 970 EVO Plus 2TB NVME (no SMART errors)
BIOS: 4805
Secure Boot: On (despite what Info Center claims)

Extra information or context

Prior attempts to check ostree for errors resulted in the following:
Ostree_Error.txt

comer@main-bazzite:~$ ostree fsck -a --delete
Validating refs...
Validating refs in collections...
Enumerating commits...
Verifying content integrity of 307 commit objects...
fsck objects (1/141729) [             ]   0%In commits c484defc2f9e9e3cb4e096190018702567598b011cdbf894b714f6f0360d8d1d, ba4a4df63a1c1f0fa99c5e0000806050ad9bafa5b3fecd1e2a087dd7471b4cca: fsck content object dbd6f56ad7df7d281fe00effba69a8baf9319eccb9a3fb2dd6ebc79c6ebd2544: Opening content object dbd6f56ad7df7d281fe00effba69a8baf9319eccb9a3fb2dd6ebc79c6ebd2544: openat: Permission denied
Marking commit as partial: c484defc2f9e9e3cb4e096190018702567598b011cdbf894b714f6f0360d8d1d

error: open(state/c484defc2f9e9e3cb4e096190018702567598b011cdbf894b714f6f0360d8d1d.commitpartial): Read-only file system
ccomer@main-bazzite:~$ sudo ostree fsck -a --delete
[sudo] password for ccomer: 
Validating refs...
Validating refs in collections...
Enumerating commits...
Verifying content integrity of 307 commit objects...
fsck objects (141729/141729) [=============] 100%
18 partial commits not verified
error: 18 partial commits from fsck-detected corruption

After another look, it looks like my ostree commit was marked as partial by ostree fsck . How do I get bazzite to repull an updated and complete commit?