Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Add Koschei EOL steps to Koschei sysadmin guide and EOL SOP

Browse source 
The Koschei collection for the EOL release needs to be removed at
EOL. Add instructions for that to the Koschei sysadmin guide and
link them from the EOL SOP.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2024-11-27 08:56:16 -08:00
parent 0c93bda207
commit 77b843beb7
2 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
modules/release_guide/pages/release_eol.adoc
View file

@ -146,6 +146,12 @@ Syntax: sudo rbac-playbook groups/bodhi-backend.yml
Send the final announcement to `devel@`, `devel-announce@`, `test@`, `test-announce@`, `announce@` lists.
Use the https://pagure.io/releng/blob/main/f/mail-templates/08-end-of-life.txt[template] from release engineering repo.
=== Other tasks
==== Remove EOL release from Koschei
The release going EOL must be removed from Koschei to prevent a flood of failed scratch builds.
See the xref:sysadmin_guide:koschei.adoc#_removing_an_eol_fedora_release[Koschei sysadmin guide] for details.
=== Stage the EOL release to archive

12
modules/sysadmin_guide/pages/koschei.adoc
View file

@ -230,6 +230,18 @@ Then you can optionally verify that the collection configuration is
correct by visiting https://koschei.fedoraproject.org/collections
and examining the configuration of the newly branched collection.
== Removing an EOL Fedora release
When a Fedora release goes EOL its collection must be removed from Koschei.
Otherwise Koschei will flood Koji with scratch build attempts that fail.
To do this, from the admin pod, run:
....
koschei-admin delete-collection --force f39
....
with '39' changed to the number of the release going EOL.
== Edit Koschei group to make it global
To turn `mygroup` group created by user `someuser` into a global group