cc: @pjgeorg @jcpunk

Thanks @ngompa for opening this issue.
Just confirming that the Kmods SIG indeed requests these tags to be created once rhel9 buildroot is available in CBS.

Concerning the tags one small clarification:
For kmods9-packages-rebuild-el9-build we do not want epel9 to be enabled.
For kmods9-packages-main-el9-build we do want epel9 to be enabled.

This corresponds to the configuration of the el8 tags.

Thanks!

@bstinson opinions/thoughts on this request ? it's true that we had a el8 feature to let people move from centos 8 to rhel 8 but what about doing this for rhel 9 ?
The main question is : where should these packages land : mirror.stream.centos.org ?

[backlog refinement]
We just implement the mechanics for this ticket, but where these packages will land will be decided later.

We'll first start by downloading RHEL9 content for internal mirror used by cbs builders.
Once we'll have this ready, we'll create some tags but the -release ones will be locked (per discussion , while waiting for centos-board decision about where packages should land)

Just pushed to git/ansible the needed changes to start generating/updating internal mirror for RHEL9 content. Once we'll have that, we'll work on the cbs tags (worth knowing that myself I'll be on PTO soon so either I'll do it when I'll be back or someone else from Infra and Releng team will take care of this)

quick update : we have now an internal RHEL9 mirror that was can use as externalrepo for CBS, but creating new tags using RHEL instead of CentOS will need a very small change (as it wasn't designed to use rhel by default).
The other question remains : do we have news about where the built content should land ?
@bstinson ^

Please note that I opened an issue with the CentOS board 1 which also concerns where the built content should land.

Tags were created :

* Checking distribution el9 configuration...
 -> Checking kmods config...
Using default options for kmods/packages
Creating tag  : kmods9-packages-main-candidate
Creating tag  : kmods9-packages-main-testing
Creating tag  : kmods9-packages-main-release
 -> creating kmods9-packages-main-el9
Added external repo rhel9-baseos to tag kmods9-packages-main-el9-build (priority 5)
Added external repo rhel9-appstream to tag kmods9-packages-main-el9-build (priority 10)
Added external repo rhel9-crb to tag kmods9-packages-main-el9-build (priority 15)

* Checking distribution el9 configuration...
 -> Checking kmods config...
Using default options for kmods/packages
Creating tag  : kmods9-packages-rebuild-candidate
Creating tag  : kmods9-packages-rebuild-testing
Creating tag  : kmods9-packages-rebuild-release
 -> creating kmods9-packages-rebuild-el9
Added external repo rhel9-baseos to tag kmods9-packages-rebuild-el9-build (priority 5)
Added external repo rhel9-appstream to tag kmods9-packages-rebuild-el9-build (priority 10)
Added external repo rhel9-crb to tag kmods9-packages-rebuild-el9-build (priority 15)

the rpm.macro.vendor option was also set on both and epel9 repo enabled/added only on kmods9-packages-main-el9-build

Worth knowing that in current state, tags are created but locked for -testing and -release until we know where signing process should send built/tagged packages, and that also means a modification in our script (and so test it first)

@pjgeorg , @bstinson : as it's working at the koji side, let us know when we have a decision on where to push as we'll just need to also reflect that in signing+push process ... (also 9 vs 9-stream case)

[backlog refinement]
The place was decided on the meeting and the signing and push process needs to be adjusted to reflect the change.

Indeed per discussion/meeting yesterday it was said that it's just expected to be pushed under mirror.stream.centos.org/SIGs/9/ so small change in the sign+push process was added/tested today and kmod9 tags unlocked.
You can now tag-build in -testing and -release tags