next: new release 35.20211003.1.0 on 2021-10-04

[lucab]

First, verify that you meet all the prerequisites

Name this issue next: 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.2.0).

Pre-release

Promote next-devel changes to next

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

Build

• Start a pipeline build (select next, leave all other defaults)
• Post a link to the jobs 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 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
• 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 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)

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 a 48-hour rollout starting at 10 AM ET, run:

./rollout.py add next <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=next&rollout_wariness=0'
curl -H 'Accept: application/json' 'https://updates.coreos.fedoraproject.org/v1/graph?basearch=aarch64&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.

[gursewak1997]

Failed build with process apparently never started in /home/jenkins/agent/workspace/fedora-coreos/fedora-coreos-fedora-coreos-pipeline@tmp/durable-7abe8fcd due to pipeline overload
https://jenkins-fedora-coreos.apps.ocp.ci.centos.org/job/fedora-coreos/job/fedora-coreos-fedora-coreos-pipeline/2890/

[gursewak1997]

Builds:

• x86_64: https://jenkins-fedora-coreos.apps.ocp.ci.centos.org/job/fedora-coreos/job/fedora-coreos-fedora-coreos-pipeline/2891/
• aarch64: https://jenkins-fedora-coreos.apps.ocp.ci.centos.org/job/multi-arch-pipeline/151/

[gursewak1997]

kola OpenStack run: https://jenkins-fedora-coreos.apps.ocp.ci.centos.org/job/kola-openstack/403/
Getting ⚠️ harness.go:1130: Cluster failed starting machines: waiting for instance to run: time limit exceeded
Ignoring since infra is just taking too long for instances to come up

[dustymabe]

Ignoring since infra is just taking too long for instances to come up

👍 - this was under my advice - any tests where the instances came up in time completed tests successfully

[gursewak1997]

Release job (35.20211003.1.0): https://jenkins-fedora-coreos.apps.ocp.ci.centos.org/job/fedora-coreos/job/fedora-coreos-fedora-coreos-pipeline-release/770/

[gursewak1997]

Rollout PR: #382

[gursewak1997]

Housekeeping: #383