| |
@@ -86,9 +86,15 @@
|
| |
manual/copr/copr-dist-git-upgrade.yml
|
| |
sudo rbac-playbook -l copr-dist-git-dev.aws.fedoraproject.org groups/copr-dist-git.yml
|
| |
|
| |
+ .. note::
|
| |
+
|
| |
+ If there is a new version of copr-rpmbuild, follow the
|
| |
+ :ref:`terminate_os_vms` and :ref:`terminate_resalloc_vms` instructions.
|
| |
+
|
| |
+ Make sure expected versions of Copr packages are installed on the dev
|
| |
+ instances::
|
| |
|
| |
- Note: If there is a new version of copr-rpmbuild, follow the
|
| |
- :ref:`terminate_os_vms` and :ref:`terminate_resalloc_vms` instructions.
|
| |
+ ./releng/run-on-all-infra --devel 'rpm -qa | grep copr'
|
| |
|
| |
|
| |
Call for QA
|
| |
@@ -257,7 +263,18 @@
|
| |
manual/copr/copr-dist-git-upgrade.yml
|
| |
sudo rbac-playbook -l copr-dist-git.aws.fedoraproject.org groups/copr-dist-git.yml
|
| |
|
| |
- Note: You shouldn't need to upgrade DB manually, playbook covers it.
|
| |
+ .. note::
|
| |
+
|
| |
+ You shouldn't need to upgrade DB manually, playbook covers it.
|
| |
+
|
| |
+ Make sure expected versions of Copr packages are installed on the
|
| |
+ production instances::
|
| |
+
|
| |
+ ./releng/run-on-all-infra 'rpm -qa | grep copr'
|
| |
+
|
| |
+ And make sure there is no unexpected update available::
|
| |
+
|
| |
+ ./releng/run-on-all-infra 'dnf copr list'
|
| |
|
| |
|
| |
Test production machine
|
| |
frostyx
commented 2 years ago
Use
run-on-all-infrascript to make sure that we use the expected versions of Copr packages during release.