[releng] update eol and fix some stuff

Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>

modules/release_guide/pages/release_eol.adoc

@@ -19,6 +19,11 @@ https://fedorapeople.org/groups/schedule/f-{branched}/f-{branched}-key-tasks.htm
 Send an email to devel@, devel-announce@, test-announce@, announce@
 lists as remainder about the release EOL. Use https://pagure.io/releng/blob/main/f/mail-templates/07-end-of-life.txt[template] from release engineering repo
 
+[NOTE]
+====
+Please ensure that the reminder email is scheduled to be sent one week before the end of life.
+====
+
 ==== Koji tasks
 
 * Disable builds by removing targets
@@ -87,11 +92,17 @@ $ sudo ansible-playbook /srv/web/infra/ansible/playbooks/groups/bodhi-backend.ym
 $ sudo ansible-playbook /srv/web/infra/ansible/playbooks/groups/koji-hub.yml
 $ sudo ansible-playbook /srv/web/infra/ansible/playbooks/groups/mbs.yml
 $ sudo ansible-playbook /srv/web/infra/ansible/playbooks/groups/releng-compose.yml
-$ sudo ansible-playbook /srv/web/infra/ansible/playbooks/groups/proxies -t pkgdb2
+$ sudo ansible-playbook /srv/web/infra/ansible/playbooks/groups/proxies.yml -t pkgdb2
 $ sudo ansible-playbook /srv/web/infra/ansible/playbooks/manual/autosign.yml
 $ sudo ansible-playbook /srv/web/infra/ansible/playbooks/openshift-apps/bodhi.yml
 ....
 
+[NOTE]
+====
+Another way to run the playbook is using rbac-playbook, in case one don't have sysadmin-main rights or can't become root.
+Syntax: sudo rbac-playbook mbs.yml
+====
+
 ==== MBS Platform Retirement
 
 * To retire the platform in mbs, run the following command on
@@ -111,11 +122,11 @@ Use https://pagure.io/releng/blob/main/f/mail-templates/07-end-of-life.txt[templ
 
 ===== Update FedoraPreviousPrevious.yaml in ansible repository
 
-set the variable to False
+* set the variable to False
 
 ===== Move the EOL release to archive
 
-. log into to bodhi-backend01 and become root
+. Log into to bodhi-backend01 and become root
 +
 ____
 ....
@@ -124,21 +135,21 @@ $ sudo su
 $ su - ftpsync
 ....
 ____
-. then change into the releases directory.
+. Then change into the releases directory.
 +
 ____
 ....
 $ cd /pub/fedora/linux/releases
 ....
 ____
-. check to see that the target directory doesnt already exist.
+. Check to see that the target directory doesnt already exist.
 +
 ____
 ....
 $ ls /pub/archive/fedora/linux/releases/
 ....
 ____
-. do a recursive rsync to update any changes in the trees since the
+. Do a recursive rsync to update any changes in the trees since the
 previous copy.
 +
 ____
@@ -147,7 +158,7 @@ ____
 $ rsync -avAXSHP ./{old_release}/ /pub/archive/fedora/linux/releases/{old_release}/
 ....
 ____
-. we now do the updates and updates/testing in similar ways.
+. We will now do the updates and updates/testing in similar ways.
 +
 ____
 [source,subs="attributes+"]
@@ -158,8 +169,20 @@ $ cd testing
 $ rsync -avAXSHP {old_release}/ /pub/archive/fedora/linux/updates/testing/{old_release}/
 ....
 ____
-. do the same with fedora-secondary.
+. Do the same with fedora-secondary.
-. announce to the mirror list this has been done and that in 2 weeks you
++
+____
+[source,subs="attributes+"]
+....
+$ cd /pub/fedora-secondary/releases/
+$ rsync -avAXSHP ./{old_release}/ /pub/archive/fedora-secondary/releases/{old_release}/
+$ cd ../updates/
+$ rsync -avAXSHP {old_release}/ /pub/archive/fedora-secondary/updates/{old_release}/
+$ cd testing
+$ rsync -avAXSHP {old_release}/ /pub/archive/fedora-secondary/updates/testing/{old_release}/
+....
+____
+. Announce to the mirror list this has been done and that in 2 weeks you
 will move the old trees to archives.
 . in two weeks, log into mm-backend01 and run the archive script
 +
@@ -169,24 +192,42 @@ ____
 $ sudo -u mirrormanager mm2_move-to-archive --originalCategory="Fedora Linux" --archiveCategory="Fedora Archive" --directoryRe='/{old_release}/Everything'
 ....
 ____
-. if there are problems, the postgres DB may have issues and so you need
+. If there are problems, the postgres DB may have issues and so you need
 to get a DBA to update the backend to fix items.
 . wait an hour or so then you can remove the files from the main tree. 
-+
+
+[NOTE]
+====
+We need to do a cleanup here for both fedora and fedora-secondary for releases, updates, and updates/testing for the {old_release} release.
+====
+
 ____
 [source,subs="attributes+"]
 ....
 $ ssh bodhi-backend01
-$ cd /pub/fedora/linux
+$ cd /pub/fedora/linux/releases/{old_release}
-$ cd releases/{old_release}
 $ ls # make sure you have stuff here
 $ rm -rf *
 $ ln ../20/README .
-$ cd ../../updates/{old_release}
+$ cd /pub/fedora/linux/updates/{old_release}
-$ ls #make sure you have stuff here
+$ ls # make sure you have stuff here
 $ rm -rf *
 $ ln ../20/README .
-$ cd ../testing/{old_release}
+$ cd /pub/fedora/linux/updates/testing/{old_release}
+$ ls # make sure you have stuff here
+$ rm -rf *
+$ ln ../20/README .
+
+#for fedora-secondary
+$ cd /pub/fedora-secondary/releases/{old_release}
+$ ls # make sure you have stuff here
+$ rm -rf *
+$ ln ../20/README .
+$ cd /pub/fedora-secondary/updates/{old_release}
+$ ls # make sure you have stuff here
+$ rm -rf *
+$ ln ../20/README .
+$ cd /pub/fedora-secondary/updates/testing/{old_release}
 $ ls # make sure you have stuff here
 $ rm -rf *
 $ ln ../20/README .