If I'm following the process correctly, when we do a Fedora compose, we build ostrees and put them in a repo at /mnt/koji/compose/ostree/repo/ with appropriate refs - e.g. fedora/40/${basearch}/silverblue for the Silverblue ostrees.
/mnt/koji/compose/ostree/repo/
fedora/40/${basearch}/silverblue
Unfortunately, it seems like the same repo and refs are used for nightly and candidate composes. So I think it's possible that if a candidate and nightly compose are running at the same time, one can actually overwrite the other's ostrees and cause problems. I think this happened to Fedora 40 Beta-1.3, because the Silverblue ostree installer actually deploys the ostree from the Fedora-40-20240313.n.0 nightly compose.
if this repo is the one we ultimately actually publish, I guess this also means nightlies "override" candidates for regular updates of ostree installs...
Metadata Update from @phsmoura: - Issue tagged with: medium-gain, medium-trouble, ops
Yeah, I'm open to ideas here. ;(
We could do the rc's with a different ref? but then people who switch to that wouldn't get any more updates until they switch back to the nightly stream right?
Log in to comment on this ticket.