Learn more about these different git repos.
Other Git URLs
I can take the torrents section.
The torrents section should be done now. Looking into updating MirrorManager configuration...
Metadata Update from @patrikp: - Issue assigned to patrikp
The way it's referenced in the SOP [1] doesn't work. rbac-playbook doesn't allow extra arguments. Until this feature is added the playbook has to be run with ansible-playbook instead. Only sysadmin-main members can do that.
rbac-playbook
ansible-playbook
sysadmin-main
[1] https://docs.fedoraproject.org/en-US/infra/release_guide/release_post_cleanup/#_update_mirrormanager_configuration
Yeah...
I manually tried to run it but:
PLAY [Run the move-devel-to-release script] **************************************************** TASK [Validate the version 41] ***************************************************************** Thursday 14 November 2024 22:09:16 +0000 (0:00:00.935) 0:00:00.935 ***** Thursday 14 November 2024 22:09:16 +0000 (0:00:00.935) 0:00:00.935 ***** ok: [os-control01.iad2.fedoraproject.org] => { "changed": false, "msg": "All assertions passed" } ok: [os-control01.stg.iad2.fedoraproject.org] => { "changed": false, "msg": "All assertions passed" } TASK [openshift/job : Validate the job name {{ name }}] **************************************** Thursday 14 November 2024 22:09:17 +0000 (0:00:01.176) 0:00:02.112 ***** Thursday 14 November 2024 22:09:17 +0000 (0:00:01.176) 0:00:02.112 ***** fatal: [os-control01.iad2.fedoraproject.org]: FAILED! => { "assertion": "name is defined", "changed": false, "evaluated_to": false, "msg": "The 'name' variable is not defined" } fatal: [os-control01.stg.iad2.fedoraproject.org]: FAILED! => { "assertion": "name is defined", "changed": false, "evaluated_to": false, "msg": "The 'name' variable is not defined" } PLAY RECAP ************************************************************************************* os-control01.iad2.fedoraproject.org : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 os-control01.stg.iad2.fedoraproject.org : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
@abompard ?
OK I fixed the playbook and ran it again. It has completed successfully.
Might still have not worked right? See https://pagure.io/fedora-infrastructure/issue/12308
Huh, ideally the playbook should fail if the command fails. I'll see what I can do in this regard.
Log in to comment on this ticket.