#12700 F42 Post Release Cleanup
Closed: Fixed 16 hours ago by amedvede. Opened a month ago by jnsamyak.

F42 Post Release Cleanup is up for this week, which involves dealing with these four tasks mainly:
Doc: https://docs.fedoraproject.org/en-US/infra/release_guide/release_post_cleanup/

  1. Update MirrorManager Configuration - @patrikp
  2. Removing N_Beta from Torrents - @patrikp
  3. Cleanup of RCs and Unnecessary Composes - @amedvede
  4. Closure of Failed Compose Issues - @amedvede

Anton wanted support on this, so I assigned him points 3 and 4.

Please make sure to get the things required to be done this week. Thanks.


Metadata Update from @amedvede:
- Issue assigned to amedvede

a month ago

I need to be part either sysadmin-bodhi or sysadmin-releng group to be able to connect to the bodhi-backend server, can I get access?

Metadata Update from @james:
- Issue tagged with: medium-gain, medium-trouble

a month ago

Metadata Update from @jnsamyak:
- Issue tagged with: f42

24 days ago

The beta torrents should be cleaned up now.

The command as it is currently written int he SOP can't be run. This is because the rbac-playbook wrapper script in Fedora Infrastructure's Ansible setup has specific syntax requirements that differ from vanilla Ansible. rbac-playbook doesn't support the --extra-vars flag so we have to move the variable to the playbook itself and it'll be changed via PRs in the future.

Here's the PR:
https://pagure.io/fedora-infra/ansible/pull-request/2584

I have removed dirs related to beta and final RC.
Removed composes except for the final one
Waiting for +1 from Kevin to remove dirs in /pub/fedora/linux/development/42 and /pub/fedora-secondary/development/42
Send email about closing open issues in failed composes, I'll wait until Monday and then will run the script

The torrents were not actually done, and it has some missing pieces The ini files were still there, and hence it was showing the reference in the layout, even though the contents were not there, I fixed it now and it's all okay; The whitelist cron has some problems for which I have manually created it from the /root/torrent-hash py script which is also sorted - these are the update from step 1

Turns out step 2 is not open for the rbac-playbooks yet, so might need to see if there is a specific reason to do that, but for 42 cleanup it's done, with my sysadmin-main hat on!

@amedvede shared in standup today that failed-composes cleanup will happen today, and otherwise the dirs are cleaned up, if there is anything missing please report us here

So, we need to wait until mirrormanager updates after that playbook run. You can see:

curl 'https://mirrors.fedoraproject.org/metalink?repo=fedora-42&arch=x86_64'

still shows development/42/
When that changes to show releases/42 we can remove those dirs.

Also, we need to add to the SOP: /pub/alt/development/ (it has been missed the last few cycles. We should remove all the non rawhide ones from there at this point)

It still hasn't updated. We should doublecheck that the script ran... and/or ask @abompard to look closeer.

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak (was: amedvede)

10 days ago

@kevin So, I should add to documentation SOP to the 3rd section, also removing all development items except rawhide from /pub/alt/development/. Give me +1 and I'll do it

Please do NOT do that step until we fix mirrormanager. It's currently pointing at that location. If we delete it now, all the people using f42 will get no content. ;(

sure!, can i at least update doc for now?

Oh, right, sure, please do.

The mirror manager is now fixed, and the playbook ran successfully!

nice, so now I can remove old development items from pub/alt/development/?

Metadata Update from @amedvede:
- Issue assigned to amedvede (was: jnsamyak)

2 days ago

yep. I think it's ok to move forward to complete this all now.

the doc is updated: https://pagure.io/infra-docs-fpo/pull-request/374
Also, dirs are removed, so now post-release cleanup is done.

Post-release cleanup is done

Metadata Update from @amedvede:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

16 hours ago

Log in to comment on this ticket.

Metadata