#12053 Extend duration that ELN buildroot repos are kept to 17 days
Opened a year ago by mh21. Modified 9 months ago

Describe the issue

The Red Hat kernel team (and maybe other teams with similar requirements) have to develop and test their software packages before official development is open for the next major RHEL release. This is commonly done via ELN (=Enterprise Linux Next), which by definition is the designed test bed for the next RHEL release.

Two pieces are necessary for building on and testing a specific ELN iteration:

  • the compose itself
  • a matching buildroot repository

These pieces are available at:

ELN composes are mirrored inside Red Hat and kept for ~10 days. This is not done for ELN buildroots.

As ELN composes are not gated in any way, failure to install/boot are pretty common.

As the party responsible for the kernel CI workflow, the CKI team would like to request to extend the duration that ELN buildroot repos are kept to 17 days.

This would allow us to implement compose freezing with a weekly update cycle, with about 1 week time to resolve critical problems like instability/boot failures.

When do you need this?

With the ELN composes currently not installing because of https://bugzilla.redhat.com/show_bug.cgi?id=2273333, ideally yesterday 😄

When is this no longer needed or useful?

When Rawhide/ELN composes are gated for instability/bootability, eg. via Fedora CI.

If we cannot complete your request, what is the impact?

ELN is currently underused and undertested because of its instability. This is a small first step to make it easier to implement custom testing/gating/promotion workflows for ELN composes.

If this is not possible on the Fedora side, mirroring of the ELN buildroots to Red Hat internal infra is also a possibility. Note that this makes it impossible to implement such workflows outside Red Hat.


So, I do not think this is possible.

kojira only has a global setting, so we would have to change it for everything, we do not have at all nearly enough disk space to keep all buildroots for that long. ;(

So, we need to possibly look at better ways to do this? ie, some kind of gating/testing of composes so they aren't broken?

CC: @sgallagh @adamwill

Metadata Update from @kevin:
- Issue tagged with: high-trouble, low-gain, ops

a year ago

I think this becomes a bit less of an issue once https://pagure.io/pungi-fedora/pull-request/1304 is done, as at that point, ELN composes will stick around for two weeks, as the other nightlies do.

some further RH-internal discussions about this at https://redhat-internal.slack.com/archives/C04KPCFGDTN/p1725360040422199:

  • @sgallagh and @adamwill are going to look into onboarding ELN to the OpenQA installability/bootability tests 💕

That will change the release repos, but the buildroot repos retention will not be changed...

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog