prestist commented 3 months ago

First, verify that you meet all the prerequisites

Edit the issue title to include today's date. Once the pipeline spits out the new version ID, you can append it to the title e.g. (31.20191117.1.0).

Pre-release

Promote next-devel changes to next

[x] Add the ok-to-promote label to the issue
[x] Review the promotion PR against the next branch on https://github.com/coreos/fedora-coreos-config
[x] Once CI has passed, merge it

Manual alternative

Sometimes you need to run the process manually like if you need to add an extra commit to change something in `manifest.yaml`. The steps for this are: - `git fetch upstream` - `git checkout next` - `git reset --hard upstream/next` - `/path/to/fedora-coreos-releng-automation/scripts/promote-config.sh next-devel` - Open PR against the `next` branch on https://github.com/coreos/fedora-coreos-config

Build

[x] Start a build job (select next, leave all other defaults). This will automatically run multi-arch builds.
Post links to the jobs as a comment to this issue
- [x] x86_64
- [x] aarch64 (multi-arch build job)
- [x] ppc64le (multi-arch build job)
- [x] s390x (multi-arch build job)
Wait for the jobs to finish and succeed
- [x] x86_64
- [x] aarch64
- [x] ppc64le
- [x] s390x

Sanity-check the build

Using the the build browser for the next stream:

Verify that the parent commit and version match the previous next release (in the future, we'll want to integrate this check in the release job)
- [x] x86_64
- [x] aarch64
- [x] ppc64le
- [x] s390x
Check kola extended upgrade runs to make sure they didn't fail
- [x] x86_64
- [x] aarch64
- [x] ppc64le
- [x] s390x
Check kola AWS runs to make sure they didn't fail
- [x] x86_64
- [x] aarch64
Check kola OpenStack runs to make sure they didn't fail
- [x] x86_64
- [x] aarch64
Check kola Azure run to make sure it didn't fail
- [x] x86_64
Check kola GCP runs to make sure they didn't fail
- [x] x86_64
- [x] aarch64

⚠️ Release ⚠️

IMPORTANT: this is the point of no return here. Once the OSTree commit is imported into the unified repo, any machine that manually runs rpm-ostree upgrade will have the new update.

Run the release job

[x] Run the release job, filling in for parameters next and the new version ID
[x] Post a link to the job as a comment to this issue
[x] Wait for job to finish

At this point, Cincinnati will see the new release on its next refresh and create a corresponding node in the graph without edges pointing to it yet.

Refresh metadata (stream and updates)

[x] Wait for all releases that will be released simultaneously to reach this step in the process
[x] Go to the rollout workflow, click "Run workflow", and fill out the form

Rollout general guidelines

|Risk|Day of the week|Rollout Start Time|Time allocation| | -------- | ------- | ------- | ------- | |risky| Tuesday | 2PM UTC | 72H | |common| Tuesday | 2PM UTC | 48H | |rapid| Tuesday | 2PM UTC | 24H | When setting a rollout start time ask "when would be the best time to react to any errors or regressions from updates?". Commonly we select 2PM UTC so that the rollout's start at 10am EST(±1 for daylight savings), but these can be fluid and adjust after talking with the fedora-coreos IRC. Note, this is impacted by the day of the week and holidays. The later in the week the release gets held up due to unforeseen issues the more likely the rollout time allocation will need to shrink or the release will need to be deferred.

Manual alternative

- Make sure your `fedora-coreos-stream-generator` binary is up-to-date. From a checkout of this repo: - Update stream metadata, by running: ``` fedora-coreos-stream-generator -releases=https://fcos-builds.s3.amazonaws.com/prod/streams/next/releases.json -output-file=streams/next.json -pretty-print ``` - Add a rollout. For example, for a 48-hour rollout starting at 10 AM ET the same day, run: ``` ./rollout.py add next "10 am ET today" 48 ``` - Commit the changes and open a PR against the repo

[x] Verify that the expected OS versions appear in the PR on https://github.com/coreos/fedora-coreos-streams
[x] Post a link to the resulting PR as a comment to this issue
[x] Review and approve the PR, then wait for someone else to approve it also
[x] Once approved, merge it and verify that the sync-stream-metadata job syncs the contents to S3
[x] Verify the new version shows up on the download page
Verify the incoming edges are showing up in the update graph.
- [x] x86_64
- [x] aarch64
- [x] ppc64le
- [x] s390x

Update graph manual check

``` curl -H 'Accept: application/json' 'https://updates.coreos.fedoraproject.org/v1/graph?basearch=x86_64&stream=next&rollout_wariness=0' curl -H 'Accept: application/json' 'https://updates.coreos.fedoraproject.org/v1/graph?basearch=aarch64&stream=next&rollout_wariness=0' curl -H 'Accept: application/json' 'https://updates.coreos.fedoraproject.org/v1/graph?basearch=ppc64le&stream=next&rollout_wariness=0' curl -H 'Accept: application/json' 'https://updates.coreos.fedoraproject.org/v1/graph?basearch=s390x&stream=next&rollout_wariness=0' ```

NOTE: In the future, most of these steps will be automated.

Housekeeping

[x] If one doesn't already exist, open an issue in this repo for the next release in this stream. Use the approximate date of the release in the title.
[x] Issues opened via the previous link will automatically create a linked Jira card. Assign the GitHub issue and Jira card to the next person in the rotation.