stable: new release on 2021-10-18 ( 34.20211004.3.1)

[ravanelli]

First, verify that you meet all the prerequisites

Name this issue stable: new release on YYYY-MM-DD with today's date. Once the pipeline spits out the new version ID, you can append it to the title e.g. (31.20191117.3.0).

Pre-release

Promote testing changes to stable

• Add the ok-to-promote label to the issue
• Review the promotion PR opened by the bot against the stable branch on https://github.com/coreos/fedora-coreos-config
• Once CI has passed, merge it

Build

• Start a pipeline build (select stable, leave all other defaults)
• Post a link to the job as a comment to this issue
  • x86_64
  • aarch64 (multi-arch pipeline)
• Wait for the job to finish and succeed
  • x86_64
  • aarch64

Sanity-check the build

Using the the build browser for the stable stream:

• Verify that the parent commit and version match the previous stable release (in the future, we'll want to integrate this check in the release job)
  • x86_64
  • aarch64
• Check kola AWS runs to make sure they didn't fail
  • x86_64
  • aarch64
• Check kola GCP run to make sure it didn't fail
• Check kola OpenStack run to make sure it didn't fail

⚠️ 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

• Run the release job, filling in for parameters stable and the new version ID
• Post a link to the job as a comment to this issue
• 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)

From a checkout of this repo:

• Update stream metadata, by running:

fedora-coreos-stream-generator -releases=https://fcos-builds.s3.amazonaws.com/prod/streams/stable/releases.json  -output-file=streams/stable.json -pretty-print

• Add a rollout. For a 48-hour rollout starting at 10 AM ET, run:

./rollout.py add stable <version> "10 am ET" 48

• Commit the changes and open a PR against the repo. Paste the output of make print-rollouts into the PR description.
• Post a link to the PR as a comment to this issue
• Wait for the PR to be approved.
• Once approved, merge it and verify that the sync-stream-metadata job syncs the contents to S3
• Verify the new version shows up on the download page
• Verify the incoming edges are showing up in the update graph.
  • x86_64
  • aarch64

Update graph manual check

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

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

Housekeeping

• If one doesn't already exist, open an issue in this repo with the approximate date in the title of the next release in this stream.
• 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.

[sohankunkerkar]

Pipeline builds:

1. x86: https://jenkins-fedora-coreos.apps.ocp.ci.centos.org/job/fedora-coreos/job/fedora-coreos-fedora-coreos-pipeline/3046/
2. aarch64: https://jenkins-fedora-coreos.apps.ocp.ci.centos.org/job/multi-arch-pipeline/206/

[sohankunkerkar]

kola openstack job failed

[dustymabe]

kola openstack job failed

known issue: coreos/fedora-coreos-tracker#994

Notice that the re-run of the failed test did pass, so we should probably be able to ignore this failure.

[sohankunkerkar]

Release job: https://jenkins-fedora-coreos.apps.ocp.ci.centos.org/job/fedora-coreos/job/fedora-coreos-fedora-coreos-pipeline-release/830/

[sohankunkerkar]

rollout PR: #389