next: new release on 2022-11-15 (37.20221111.1.0)

[marmijo]

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

• Add the ok-to-promote label to the issue
• Review the promotion PR against the next branch on https://github.com/coreos/fedora-coreos-config
• 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

• 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
  • x86_64
  • aarch64 (multi-arch build job)
  • s390x (multi-arch build job)
• Wait for the jobs to finish and succeed
  • x86_64
  • aarch64
  • 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)
  • x86_64
  • aarch64
  • s390x
• Check kola AWS runs to make sure they didn't fail
  • x86_64
  • aarch64
• Check kola OpenStack runs to make sure they didn't fail
  • x86_64
  • aarch64
• Check kola Azure run to make sure it didn't fail
• Check kola GCP 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 next 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)

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

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 <version> "10 am ET today" 48

• Commit the changes and open a PR against the repo

• Verify that the PR contains the expected OS versions
• Post a link to the resulting PR as a comment to this issue
• Review and approve the PR, then wait for someone else to approve it also
• 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
  • 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=s390x&stream=next&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 for the next release in this stream. Use the approximate date of the release in the title.
• 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.

[dustymabe]

Because of a podman regression in 4.3.0 that causes podman --remote to not work (i.e. our multi-arch builds won't work) we need to use quay.io/coreos-assembler/coreos-assembler:v37.20221106.2.0 for these builds too.

[dustymabe]

Reminder - continue to skip ppc64le for now.

[marmijo]

• build x86_64: https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/job/build/568/ 🕓
• build s390x: https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/job/build-arch/703/ 🕓
• build aarch64: https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/job/build-arch/702/ 🕓

[marmijo]

	AWS	Azure	GCP	OpenStack
x86_64	✔️	✔️	✔️	✔️
aarch64	✔️	−	−	✔️

[marmijo]

next release: https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/job/release/227/ ✔️

[marmijo]

Rollout PR: #596