Post-Release Clean-up Documentation

Overview

This document outlines the necessary steps for cleaning up resources after the release of a Fedora version. It includes actions such as removing outdated content from servers, updating mirroring configurations, and closing open issues related to the release process.

Removing N_Beta from Torrents

Description

Remove beta versions of the Fedora release from the torrent server to prevent them from being distributed. This helps focus resources on the stable release.

Steps

  1. SSH into torrent01.fedoraproject.org.

  2. Navigate to the directory containing the 43_Beta torrents.

  3. Delete the beta torrents for the 43 version.

  4. Regenerate the whitelist to exclude these torrents.

Update MirrorManager Configuration

Description

After the release, update MirrorManager to redirect requests from the development directory to the releases directory.

Steps

  1. Run the following playbook on batcave to update the paths in MirrorManager:

    $ rbac-playbook -v /srv/web/infra/ansible/playbooks/manual/mirrormanager/move-devel-to-release.yml --extra-vars="version='43'"

Cleanup of RCs and Unnecessary Composes

Description

Remove release candidates and unnecessary composes that are no longer needed to free up storage.

Steps

  1. SSH into bodhi-backend01.rdu3.fedoraproject.org or any server where Koji is mounted.

  2. Perform the following:

    • Remove all directories related to Beta and Final RCs in /pub/alt/stage/.

    • Clean up old composes by removing all but the latest in /mnt/koji/compose/branched/ and /mnt/koji/compose/43/.

    • Two weeks after release: Remove directories at /pub/fedora/linux/development/43 and /pub/fedora-secondary/development/43.

    • After MirrorManager playbook is run: Remove all but rawhide dirs at /pub/alt/development/.

Closure of Failed Composes Issues

Description

Address and close any open issues related to failed composes to maintain the health of the Fedora release process infrastructure.

Steps

  1. Use the script available in the Fedora RelEng repository: https://pagure.io/releng/blob/main/f/scripts_new/release-process/post-release/failed_composes_cleanup.py

    python3 failed_composes_cleanup.py

  2. Run the script to automatically identify and close open issues.

Want to help? Learn how to contribute to Fedora Docs ›