releng/tickets

Collision between nightly and candidate compose use of `/mnt/koji/compose/ostree/repo/` with same refs #12010

New issue

Open

opened 2024-03-13 16:04:20 +00:00 by adamwill · 4 comments

adamwill commented

2024-03-13 16:04:20 +00:00

Member

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.

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 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. 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](https://openqa.fedoraproject.org/tests/2485743#step/os_release/33).

adamwill commented

2024-03-13 16:08:17 +00:00

Author

Member

if this repo is the one we ultimately actually publish, I guess this also means nightlies "override" candidates for regular updates of ostree installs...

if this repo is the one we ultimately actually publish, I guess this also means nightlies "override" candidates for regular updates of ostree installs...

phsmoura commented

2024-03-13 19:08:42 +00:00

Metadata Update from @phsmoura:

Issue tagged with: medium-gain, medium-trouble, ops

**Metadata Update from @phsmoura**: - Issue tagged with: medium-gain, medium-trouble, ops

kevin commented

2024-03-13 21:16:43 +00:00

Owner

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?

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?

jnsamyak self-assigned this

2026-06-29 15:32:21 +00:00

jnsamyak commented

2026-06-29 15:32:55 +00:00

Owner

update: check with ostree folks to see if there is more potentials

update: check with ostree folks to see if there is more potentials

Sign in to join this conversation.

No labels

change-noreleng

Fixed with Explanation

Insufficient data

mini-initiative

waiting on external

release-process

No milestone

No project

No assignees

4 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

releng/tickets#12010

No description provided.