OVMF upgrading for Koji

docs/koji/upgrading.md

@@ -6,7 +6,8 @@ The standard process to upgrade koji is:
 2. Stopping all Koji services
 3. Running the DB migration script (or anything else listed at [https://docs.pagure.org/koji/migrations/migrations/](https://docs.pagure.org/koji/migrations/migrations/))
 4. Upgrade the Koji RPMs
-5. Restarting Koji services
+5. (Optional) Upgrade the ` edk2.git-ovmf-x64-0` RPM
+6. Restarting Koji services
 
 
 !!! Note ""
@@ -34,6 +35,8 @@ Once you have tested a few builds, tags, image-builds or else, you will have val
 
 You may want to install the test rpm from <linuxsoft.cern.ch/internal/repos/linuxsupport8s-qa/> (or the corresponding one for other distros) locally to do this. Please be aware of your `/etc/koji.conf` content, take it from `aiadm.cern.ch` if you need to adjust it.
 
+In order to ease testing, you can run test pipelines from <https://gitlab.cern.ch/linuxsupport/testing/koji-tester>.
+
 ## Disable alerts
 
 !!! Note ""
@@ -168,6 +171,14 @@ wassh -l root -c lsb/web '/usr/bin/yum clean all && /usr/local/sbin/distro_sync.
 wassh -l root -c lsb/builder '/usr/bin/yum clean all && /usr/local/sbin/distro_sync.sh'
 ```
 
+## (Optional) Upgrade ` edk2.git-ovmf-x64-0` RPM
+
+This step is optional, as it is not strictly required to update the RPM. The reason behind the yumlock pinning is that since we are using nightly builds we have seen that certain updates make UEFI VM booting impossible, so we should better control the version we use at any given point to make sure it keeps on working.
+
+Pinned at <https://gitlab.cern.ch/ai/it-puppet-module-koji/-/blob/qa/code/manifests/builder.pp#L48-57>.
+
+To test it you would need to follow the usual Puppet environments workflow as per <https://configdocs.web.cern.ch/changes/environment.html>.
+
 ## Restart Koji
 
 ```