From 0ad40057fb42dc355420d812ebc597cb96d06ffc Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: Sep 03 2025 20:33:21 +0000 Subject: openQA sysadmin guide: add note about base images at branch I totally forgot the most important thing to deal with for openQA at branch time - rebuilding base disk images. D'oh. This adds that. Signed-off-by: Adam Williamson --- diff --git a/modules/sysadmin_guide/pages/openqa.adoc b/modules/sysadmin_guide/pages/openqa.adoc index 9aa7bbd..2fb8109 100644 --- a/modules/sysadmin_guide/pages/openqa.adoc +++ b/modules/sysadmin_guide/pages/openqa.adoc @@ -212,7 +212,10 @@ metadata is updated. These steps are all covered in the xref:release_guide:sop_mass_branching.adoc[mass brancing guide], but be aware they need to happen and work with releng to monitor them. You may need to edit the relval release metadata if the release engineer -does not have access to it. +does not have access to it. On the openQA side, new base disk images +need to be created for both the new Branched release and for Rawhide. +This can only be done once the composes are complete and mirrored and +the relval metadata is updated. Until the relval metadata is updated, openQA will believe the to-be- branched release number is Rawhide, and any updates for the new Rawhide @@ -224,6 +227,27 @@ fail due to the expected repositories not existing, etc. There is no perfect time to update the metadata, so just be aware that you may see odd behavior related to this during the branching process. +Update tests for Rawhide updates created after branching will expect +base disk images with the new release number, and so will all fail +until these are created. Update tests for the new Branched release +will attempt to run with the existing base disk images for that release +number, but because these will be Rawhide images (and have Rawhide +repository configuration), various things will fail until new images +are built from the new Branched compose. + +The simplest way to create the appropriate base disk images is to +wait until both Branched and Rawhide composes are done and mirrored +and the relval metadata is updated, then delete all existing base +images for the new branched release number from +`/var/lib/openqa/share/factory/hdd/fixed` (you can do staging first +as a test, then prod if staging works OK). Then run the openQA worker +playbook, which will cause the necessary images to be built (this +takes some time). You can also do things more manually by ssh'ing into +the worker hosts that are configured to build disk images (see +openqa_hdds_workers group in ansible), going to +`/var/lib/openqa/share/factory/hdd/fixed`, and running +`/root/createhdds/createhdds.py` commands. + At the time a test is scheduled, several release-number-related variables are set based on info from fedfind, especially `RAWREL`, which is set to whatever number relval currently believes is Rawhide.