What were you trying to do that didn't work?

I suspect this error is caused by ostree. On a RHEL9.5 machine, rebase a rhel8.10 edge vm to rhel9.5, it can reboot to new rhel9.5, but if reboot it again, ostree service will fail and cannot boot.

Please provide the package NVR for which bug is seen:

osbuild-selinux-119-1.el9.noarch
osbuild-119-1.el9.noarch
osbuild-depsolve-dnf-119-1.el9.noarch
osbuild-composer-core-110-1.el9.x86_64
osbuild-luks2-119-1.el9.noarch
osbuild-lvm2-119-1.el9.noarch
osbuild-ostree-119-1.el9.noarch
osbuild-composer-worker-110-1.el9.x86_64
osbuild-composer-110-1.el9.x86_64

How reproducible:

100%

Steps to reproduce

1. The steps are from test case https://github.com/virt-s1/rhel-edge/blob/main/ostree-8-to-9.sh, log can be found in attached log.txt.
2. On a RHEL9.5 machine, install osbuild-composer.
3. Create an edge container, set distro to rhel8.10, blueprint is like:

name = "container"
description = "A base rhel-edge container image"
version = "0.0.1"
distro = "rhel-810"
modules = []
groups = []

[[packages]]
name = "python3"
version = "*"

[[customizations.user]]
name = "admin"
description = "Administrator account"
password = "xxxxxxxxxxxxxx"
key = "xxxxxxxxxxxxxxx"
home = "/home/admin/"
groups = ["wheel"]
    4. Provision a bios edge vm with this container using anaconda kickstart file, edge vm can boot and work well.

    5. Create a new rhel9.5 edge container.

    6. Try to rebase edge vm from rhel8.10 to rhel9.5, rebase finished successfully.

    7. Reboot this edge vm, I can see there are two boot entry items listed in boot menu, one is the old rhel8.10, and one is the new rhel9.5 entry which is also the default one, select rhel9.5 and boot, edge vm can boot and works well.

    8. Reboot this edge vm again, this time I saw four boot entries listed in boot menu, there are two identical rhel9.5, and two identical rhel8.10, and rhel9.5 is still the default one. (please see attached screenshot)

     8. Choose the first rhel9.5 entry to boot, system failed to boot, found these error messages in boot screen:

Displaying logs from failed units: ostree-prepare-root.service
Jun 26 06:24:50 ostree-prepare-root[575]: Resolved OSTree target to: /sysroot/ostree/deploy/rhel-edge/deploy/599bae661ef4b4b71ae589fece51025b6f60b727e968a006303cd2c5b8fb4ede.0
Jun 26 06:24:50 ostree-prepare-root[575]: Found legacy sysroot.readonly flag, not configured in ostree/prepare-root.conf
Jun 26 06:24:50 ostree-prepare-root[575]: sysroot.readonly configuration value: 1 (fs writable: 0)
Jun 26 06:24:50 ostree-prepare-root[575]: composefs: No image present
Jun 26 06:24:50 ostree-prepare-root[575]: Using legacy ostree bind mount for /
Jun 26 06:24:50 ostree-prepare-root[575]: ostree-prepare-root: sysroot.readonly=true requires /sysroot to be writable at this point, the cmdline should contain rw but not ro, if that is not the case this is likely the issue
Jun 26 06:24:50 systemd[1]: ostree-prepare-root.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 06:24:50 systemd[1]: ostree-prepare-root.service: Failed with result 'exit-code'.
Jun 26 06:24:50 systemd[1]: Failed to start OSTree Prepare OS/.
Jun 26 06:24:50 systemd[1]: ostree-prepare-root.service: Triggering OnFailure= dependencies.

Expected results

Actual results