how do you force a new deployment?

[nivekuil]

I have a machine that experienced some data loss issues, with some symptoms like

$ ostree prune
error: No such metadata object fa78ca48747f78fb8fc2d76fb81729da29ad9f2db1e85df3906cafe6417dff43.dirtree

It seems like this will prevent the machine from getting new deployments. Here I try to move from next to stable:

$ rpm-ostree rebase fedora/x86_64/coreos/stable
2 metadata, 0 content objects fetched; 788 B transferred in 1 seconds; 0 bytes content written
Staging deployment... done
error: syscore cleanup: pruning: Pruning system repository: No such metadata object ddf426b360381792ffa2f5e6f6320325bc79e134a784c2a36463b38f4a0eaa78.dirtree

I see that the new deployment is there:

# rpm-ostree status
State: idle
Deployments:
  fedora:fedora/x86_64/coreos/stable
                  Version: 38.20230918.3.2 (2023-10-09T19:12:30Z)
                   Commit: f2824f5801f1fb85c8dc08dd0e7394031362b504ec48a2658e8ea459f52209a3
             GPGSignature: Valid signature by 6A51BBABBA3D5467B6171221809A8D7CEB10B464
                     Diff: 1 upgraded, 422 downgraded, 6 removed, 2 added

but when I reboot I'm still in the old one. I'm guessing the failed prune blocks the deploy somehow but I think it could be a best-effort step instead. How do I force it?

[nivekuil]

rollback is also blocked. Is there a way to just ignore these missing objects and hard reset to a commit?

rpm-ostree rollback
Moving 'f0fcbeb6a0589171ae43aa29e75814fa93957c2bae2dcf1addf5e63f6b1a69ba.0' to be first deployment
Bootloader updated; bootconfig swap: yes; bootversion: boot.1.1, deployment count change: 0
error: Performing final cleanup: Pruning system repository: No such metadata object ddf426b360381792ffa2f5e6f6320325bc79e134a784c2a36463b38f4a0eaa78.dirtree

[cgwalters]

Hmm yes arguably we should ignore nonexistent files when pruning.