Learn more about these different git repos.
Other Git URLs
We created the EPEL-10.0 bodhi release in #12227. Originally I was planning to not have bodhi do the composes and instead use a nightly script similar to rawhide. However, after a few discussions about this approach at Flock, I believe it would be better to let bodhi do this compose. My understanding is the primary reason rawhide uses a script outside of bodhi is that it needs to generate images, which isn't applicable for EPEL. I believe this is the correct command that needs to be run.
bodhi releases edit --name EPEL-10.0 --composed-by-bodhi
Since we've never done this compose before, we should be ready to undo this if the compose fails. We may need to make adjustments to the pungi template to account for the minor version.
Ideally by 2024-08-23.
RHEL 10 EOL (estimated 2035-05-31).
Several packagers have asked for the published repository in order to better test packages they have built. We cannot publish the EPEL 10 repository until we have a compose.
EDIT: We ran into problems with having bodhi do the compose. It seems bodhi doesn't like having both composed-by-bodhi and create-automatic-updates enabled for a release. Rather than work through the code changes in bodhi to make this a supported combination, we're just going to switch back to the original plan of doing a rawhide-style nightly compose script.
Metadata Update from @jnsamyak: - Issue tagged with: investigation, low-gain, low-trouble, ops
Metadata Update from @jnsamyak: - Issue untagged with: investigation
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
Hello!
I was busy with branching and just saw this request! I have set Composed by Bodhi to True. I'll keep this open until you test and see if this Is a feasible option, if not we can always set it back to false.
Composed by Bodhi
True
cf: https://bodhi.fedoraproject.org/releases/EPEL-10.0
I noticed that bodhi releases have a version_int property that we use in our pungi template. Since this is the first time we've given bodhi a version that isn't a simple integer, I looked into the code a bit. I think it's going to fail like this:
[ins] In [1]: import re [ins] In [2]: version_int_regex = re.compile(r'\D+(\d+)[CMFN]?$') [ins] In [3]: int(version_int_regex.match('EPEL-10.0').groups()[0]) --------------------------------------------------------------------------- AttributeError Traceback (most recent call last) Cell In[3], line 1 ----> 1 int(version_int_regex.match('EPEL-10.0').groups()[0]) AttributeError: 'NoneType' object has no attribute 'groups'
Relevant code:
I submitted a PR to avoid usage of verison_int in our pungi template, as a stop gap measure until bodhi can be adjusted.
https://pagure.io/fedora-infra/ansible/pull-request/2212
Bodhi also checks to confirm content is synced before it says a push is completed. So, we likely need to setup sync of the repos ASAP, or this will block updates.
A epel10.0-testing compose has finished. :)
Nice, to retrospect what more was needed here, can we add things that were missing?
I tried recordings things from IRC logs etc, in case I miss something let's add it here for future
CC: @carlgeorge @kevin
Metadata Update from @jnsamyak: - Issue untagged with: low-gain, low-trouble - Issue tagged with: medium-gain, medium-trouble
I was just typing up pretty much the same notes :grinning:
Gonna go ahead and post what I had to make sure we capture it all, even if some of it is duplicated.
Fingers crossed we got everything, and the next attempt at a compose will pass. If it doesn't please share the error and I'll try to identify the cause.
We ran into problems with having bodhi do the compose. It seems bodhi doesn't like having both composed-by-bodhi and create-automatic-updates enabled for a release. Rather than work through the code changes in bodhi to make this a supported combination, we're just going to switch back to the original plan of doing a rawhide-style nightly compose script. Next steps:
@carlwgeorge, looking at the last comment and reviews on the PR, I had a quick question, do you want me to update the bodhi release to pending and false now, or once the PR goes in?
I believe we need to time those at the same time, or at least the same day. I did a test run of the separate compose (just the pungi-koji command to validate the config) and it seems to have worked fine. I'm planning on doing one more test run of the whole script (not just the pungi-koji command), and then I think it will be ready to merge.
"It seems bodhi doesn't like having both composed-by-bodhi and create-automatic-updates enabled for a release."
oooo, can I cash in my "told ya so" points
Quick note for anyone subscribed to this issue, the new nightly compose has been deployed and works, but we have previous builds stuck in "pending->testing" in bodhi and we don't think they'll process further. We're going to temporarily remove the epel10 and epel10.0 targets and switch things back to get these builds to finish processing, then put it back.
We were able to get all of the in-between builds processed, and have re-enabled the new compose method. We’ve also re-created the build targets, and verified that a new build got an automatic update that moved to stable automatically.
I think we can put this issue to bed now, and things will stay in this shape until we're ready to switch back to bodhi composes for the official launch. Thanks y'all!
Metadata Update from @carlwgeorge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.