[releng] more substitutions

Signed-off-by: Tomas Hrcka <thrcka@redhat.com>
This commit is contained in:
Tomáš Hrčka 2023-03-08 15:39:31 +01:00
parent 3df6025716
commit 3646a4d77b
3 changed files with 60 additions and 25 deletions

View file

@ -9,4 +9,4 @@ Based on the GO/NOGO meeting if the currnet compose is GO. The following steps n
....
$ koji clone-tag --all --latest-only f{branched} f{branched}-Beta
$ koji clone-tag --all --latest-only f{branched}-modular f{branched}-Beta-modular
....
....

View file

@ -4,42 +4,71 @@ include::_partials/attributes.adoc[]
=== Update FedoraPreviousPrevious.yaml in ansible repository
set the variable to True
set the https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all[variable] to True in ansible repository.
==== Koji changes
=== Koji changes
[source,subs="attributes+"]
....
$ koji edit-tag --lock f31
$ koji edit-tag --lock f31-modular
$ koji edit-tag --lock f{branched}
$ koji edit-tag --lock f{branched}-modular
....
==== Bodhi Changes
=== Bodhi Changes
Set the bodhi release to `current`
[source,subs="attributes+"]
....
$ bodhi releases edit --name F31 --state current
$ bodhi releases edit --name F{branched} --state current
....
==== Disable Branched Compose
=== Disable Branched Compose
Now that we have a final GOLD compose, we dont need nightly branched
composes anymore. This is disabled in
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/releng[releng
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/releng/files/branched[releng
role] in infra ansible repo and then running the playbook.
....
$ sudo rbac-playbook groups/releng-compose.yml
....
==== Lift RelEng freeze
=== Lift RelEng freeze
Lift the RelEng Freeze so that the updates will be pushed to stable.
This is done by editing
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/vars/all/RelEngFrozen.yaml[RelEngFrozen
https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/RelEngFrozen.yaml[RelEngFrozen
variable] in infra ansible repo and then run the bodhi playbook.
....
$ sudo rbac-playbook groups/bodhi-backend.yml
....
....
=== Stage Final Release for Mirrors
. Gather the needed info for running the staging script: Release
Version: the numerical version number of the release `{branched}` ComposeID: The
ID of the Compose Label: Compsoe label for the location in stage
`{branched}_RC-1.2` for example Key: the name of teh release key `fedora-{branched}` or
`fedora-{branched}-secondary` as examples Prerelease: 0 or 1 sets if the release
goes in test/ or not Arch: <optional> For secondary arches, changes some
internal locations
+
[source,subs="attributes+"]
....
$ scripts/stage-release.sh {branched} Fedora-{branched}-20160614.0 {branched}_RC-1.2 fedora-{branched} 0
....
. Sync the release to the Red Hat internal archive following internally
documented
=== Check and set EOL on previous releases to reflect reality
. check PDC for active releases and respective EOL date
. if needed run the adjust-eol-all.py script from releng repository to
correct any mistakes
=== Verification
Verification is somewhat difficult as one cannot look at the content via
the web server due to permissions. Typically we ask somebody from the
Infrastructure team to give the tree a second set of eyes.

View file

@ -22,6 +22,7 @@ lists as remainder about the release EOL. Use https://pagure.io/releng/blob/main
* Disable builds by removing targets
[source,subs="attributes+"]
....
$ koji remove-target {old_release}
$ koji remove-target {old_release}-candidate
@ -63,11 +64,12 @@ python scripts/pdc/adjust-eol-all.py <token> f31 2020-11-24
* Run the following bodhi commands to set the releases state to
*archived*
[source,subs="attributes+"]
....
$ bodhi releases edit --name "F31" --state archived
$ bodhi releases edit --name "F31M" --state archived
$ bodhi releases edit --name "F31C" --state archived
$ bodhi releases edit --name "F31F" --state archived
$ bodhi releases edit --name "F{old_release}" --state archived
$ bodhi releases edit --name "F{old_release}M" --state archived
$ bodhi releases edit --name "F{old_release}C" --state archived
$ bodhi releases edit --name "F{old_release}F" --state archived
....
==== Fedora Infra Ansible Changes
@ -136,18 +138,20 @@ ____
previous copy.
+
____
[source,subs="attributes+"]
....
$ rsync -avAXSHP ./35/ /pub/archive/fedora/linux/releases/35/
$ rsync -avAXSHP ./35/ /pub/archive/fedora/linux/releases/{old_release}/
....
____
. we now do the updates and updates/testing in similar ways.
+
____
[source,subs="attributes+"]
....
$ cd ../updates/
$ rsync -avAXSHP 35/ /pub/archive/fedora/linux/updates/35/
$ rsync -avAXSHP {old_release}/ /pub/archive/fedora/linux/updates/{old_release}/
$ cd testing
$ rsync -avAXSHP 35/ /pub/archive/fedora/linux/updates/testing/35/
$ rsync -avAXSHP {old_release}/ /pub/archive/fedora/linux/updates/testing/{old_release}/
....
____
. do the same with fedora-secondary.
@ -156,8 +160,9 @@ will move the old trees to archives.
. in two weeks, log into mm-backend01 and run the archive script
+
____
[source,subs="attributes+"]
....
$ sudo -u mirrormanager mm2_move-to-archive --originalCategory="Fedora Linux" --archiveCategory="Fedora Archive" --directoryRe='/35/Everything'
$ sudo -u mirrormanager mm2_move-to-archive --originalCategory="Fedora Linux" --archiveCategory="Fedora Archive" --directoryRe='/{old_release}/Everything'
....
____
. if there are problems, the postgres DB may have issues and so you need
@ -165,18 +170,19 @@ to get a DBA to update the backend to fix items.
. wait an hour or so then you can remove the files from the main tree.
+
____
[source,subs="attributes+"]
....
$ ssh bodhi-backend01
$ cd /pub/fedora/linux
$ cd releases/35
$ cd releases/{old_release}
$ ls # make sure you have stuff here
$ rm -rf *
$ ln ../20/README .
$ cd ../../updates/35
$ cd ../../updates/{old_release}
$ ls #make sure you have stuff here
$ rm -rf *
$ ln ../20/README .
$ cd ../testing/35
$ cd ../testing/{old_release}
$ ls # make sure you have stuff here
$ rm -rf *
$ ln ../20/README .