next: new release on 2020-06-26 (32.20200625.1.0)

[dustymabe]

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

From the checkout for fedora-coreos-config (replace upstream below with
whichever remote name tracks coreos/):

• git fetch upstream
• git checkout next
• git reset --hard upstream/next
• /path/to/fedora-coreos-releng-automation/scripts/promote-config.sh next-devel
• Sanity check promotion with git show
• Open PR against the next branch on https://github.com/coreos/fedora-coreos-config
• Post a link to the PR as a comment to this issue
• Ideally have at least one other person check it and approve
• Once CI has passed, merge it

Build

• Start a pipeline build (select next, leave all other defaults)
• Post a link to the job as a comment to this issue
• Wait for the job to finish

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)
• Check kola AWS 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
• Verify that the OSTree commit and its signature are present and valid by booting a VM at the previous release (e.g. cosa run --qemu-image /path/to/previous.qcow2) and verifying that rpm-ostree upgrade works and rpm-ostree status shows a valid signature.

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

• Update the updates metadata, editing updates/next.json:
  • Find the last-known-good release (whose rollout has a start_percentage of 1.0) and set its version to the most recent completed rollout
  • Delete releases with completed rollouts
  • Add a new rollout:
    • Set version field to the new version
    • Set start_epoch field to a future timestamp for the rollout start (e.g. date -d '2019/09/10 14:30UTC' +%s)
    • Set start_percentage field to 0.0
    • Set duration_minutes field to a reasonable rollout window (e.g. 2880 for 48h)
  • Update the last-modified field to current time (e.g. date -u +%Y-%m-%dT%H:%M:%SZ)

A reviewer can validate the start_epoch time by running date -u -d @<EPOCH>. An example of encoding and decoding in one step: date -d '2019/09/10 14:30UTC' +%s | xargs -I{} date -u -d @{}.

• Commit the changes and open a PR against the repo.
• 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:

curl -H 'Accept: application/json' 'https://updates.coreos.fedoraproject.org/v1/graph?basearch=x86_64&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.
  • Add the jira label to the ticket
• Check the overrides lockfiles in the configs repo for the next-devel stream to see if any overrides are obsolete. They are obsolete if the rpms have hit the stable fedora repos.
  • If a PR was created post a link to the PR as a comment to this issue.

[dustymabe]

coreos/fedora-coreos-config#494

[dustymabe]

The context for this release: coreos/fedora-coreos-tracker#484 (comment)
This is the release after the barrier release that actually fixes the problem.

[dustymabe]

coreos/fedora-coreos-config#494

We changed out minds on that one (see coreos/fedora-coreos-config#494 (comment))

New PR: coreos/fedora-coreos-config#495

[dustymabe]

https://jenkins-fedora-coreos.apps.ci.centos.org/job/fedora-coreos/job/fedora-coreos-fedora-coreos-pipeline/13236/

[dustymabe]

The kola gcp run is failing because of coreos/fedora-coreos-tracker#552

The kola AWS run is still failing on coreos/fedora-coreos-tracker#507

[dustymabe]

https://jenkins-fedora-coreos.apps.ci.centos.org/job/fedora-coreos/job/fedora-coreos-fedora-coreos-pipeline-release/576/

[dustymabe]

[core@localhost ~]$ sudo rpm-ostree status 
State: idle
Deployments:
● ostree://fedora:fedora/x86_64/coreos/next
                   Version: 32.20200625.1.0 (2020-06-25T22:16:51Z)
                    Commit: 3c00a989cdcf6b9880c31b9bbabe8232d73195b44d134f4a0c06ea0d647177ae
              GPGSignature: Valid signature by 97A1AE57C3A2372CCA3A4ABA6C13026D12C944D0

  ostree://fedora:fedora/x86_64/coreos/next
                   Version: 32.20200615.1.3 (2020-06-25T08:11:24Z)
                    Commit: 1f65afd4e6b7ec80d3eb1ecf1271f66042e1ce971c38d368ff101d08305444f4
              GPGSignature: Valid signature by 97A1AE57C3A2372CCA3A4ABA6C13026D12C944D0

[dustymabe]

#143

[dustymabe]

ok I'm seeing edges in the graph and the rollout is already started.

next issue for this stream already exists

no overrides need to be removed (we're following testing-devel for now)