| |
@@ -21,7 +21,7 @@
|
| |
Example ostree compose ID: Fedora-29-updates-20181119.0
|
| |
|
| |
|
| |
- Before sending out candidate email:
|
| |
+ Before requesting releng for a release:
|
| |
|
| |
- Check to make sure the compose state is FINISHED and not FINISHED_INCOMPLETE or any other state
|
| |
- ex: https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-updates-20181119.0/STATUS
|
| |
@@ -35,7 +35,7 @@
|
| |
- Check to see if ISO image tests passed in OpenQA
|
| |
- http://openqa.fedoraproject.org/
|
| |
- ex: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=29&build=Fedora-29-updates-20181119.0&groupid=1
|
| |
- - Check to make sure AMIs were published for every region for that compose
|
| |
+ - Check to make sure x86_64 AMIs were published for every region for that compose
|
| |
- use: https://pagure.io/fedora-websites/blob/master/f/tools/get_ami.py (EX: python get_ami.py | grep Fedora-AtomicHost-$VERSION-$RELEASE)
|
| |
- There should be a standard and gp2 for each of the following:
|
| |
- ap-northeast-1
|
| |
@@ -51,13 +51,18 @@
|
| |
- us-east-1
|
| |
- us-west-1
|
| |
- us-west-2
|
| |
- - Run an openshift test against the latest AMI
|
| |
+ - Check to make sure aarch64 AMIs has been uploaded in following regions:
|
| |
+ - us-east-1
|
| |
+ - us-west-2
|
| |
+ - eu-west-1
|
| |
+ - Note that aarch64 resources in AWS are available only in above mentioned regions. Make sure that AMI boots by launching instance in any one of these regions. It may take longer time (~6 minutes) to get ssh access to the booted instance.
|
| |
+ - Run an openshift test against the latest x86_64 AMI
|
| |
- Use the latest release of openshift-ansible (currently, 3.11 is the latest)
|
| |
- something like: http://www.projectatomic.io/blog/2016/12/part1-install-origin-on-f25-atomic-host/
|
| |
- Check https://sinnykumari.fedorapeople.org/openshift/readme for latest updates required to perform
|
| |
successful openshift cluster install
|
| |
- If anything breaks, open up bug(s)/issue(s) in proper locations for whatever component is causing problems
|
| |
- - If possible, check with jbrooks to see if kube works
|
| |
+ - If possible, check kube works
|
| |
- talk with jbrooks
|
| |
- or, make sure kubeadm test from wiki https://fedoraproject.org/wiki/User:Jasonbrooks/QA/AtomicTests/Install_Kubeadm works
|
| |
- Nice to have: We don't have automated tests running for ppc64le and aarch64 architectures.
|
| |
@@ -73,7 +78,6 @@
|
| |
After release:
|
| |
|
| |
- Update Vagrant Boxes in Vagrant Cloud ( Dusty can provide access)
|
| |
- - issue for having us automate this via API calls: https://pagure.io/atomic-wg/issue/393
|
| |
- Send out "follow up" email:
|
| |
- - example: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-November/msg00001.html
|
| |
+ - example: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2019-March/msg00001.html
|
| |
- Verify static delta works for upgrade from previous release
|
| |
Signed-off-by: Sinny Kumari sinny@redhat.com