tracker: Rebase onto Fedora 37

[dustymabe]

Rebase to a new version of Fedora (N=37)

At previous Fedora major release

Open tickets to track related work for this release

• Fedora Changes Considerations (example)
• Package Additions/Removals (example)
• Test Week (example)

At Branching

Branching is when a new stream is "branched" off of rawhide. This eventually becomes the next major Fedora (N).

Release engineering changes

• Verify that a few tags were created when branching occurred:

• f${N+1}-coreos-signing-pending

• f${N+1}-coreos-continuous

• Add and tag a package (any package) which is in the stable repos into the continuous tag. This will create the initial yum repo that's used as input for building the COSA container.

• koji add-pkg --owner ${FAS_USERNAME} f${N+1}-coreos-continuous $PKG

  • example: koji add-pkg --owner dustymabe f36-coreos-continuous fedora-release
  • This example uses the fedora-release RPM, but it could be any other.

• koji tag-build f${N+1}-coreos-continuous $BUILD

  • example: koji tag-build f36-coreos-continuous fedora-release-36-0.16

• Add the N+1 signing key short hash (usually found here) to the tag info for the coreos-pool tag. The following commands view the current settings and then update the list to the 32/33/34/35 keys. You'll most likely have to get someone from releng to run the second command (edit-tag).

  • koji taginfo coreos-pool
  • koji edit-tag coreos-pool -x tag2distrepo.keys="12c944d0 9570ff31 45719a39 9867c58f"

coreos-installer changes

• Update coreos-installer to know about the signing key used for the future new major version of Fedora (N+1).
• Drop the signing key for the obsolete stable release (N-2).

Update rawhide stream

• Update manifest.yaml to list N+1 as the releasever.

Enable branched stream

• Update manifest.yaml to list N as the releasever.
• Update streams.groovy to include the branched stream in the list of mechanical refs.

At Fedora (N) Beta

Update fedora-coreos-config next-devel

• Bump releasever in manifest.yaml
• Update the repos in manifest.yaml if needed
• Run cosa fetch --update-lockfile
• PR the result

Ship rebased next

• Ship next
• Set a new update barrier for N-2 on next. In the barrier entry set a link to the docs. See discussion.

Preparing for Fedora (N) GA

Update fedora-coreos-config testing-devel

• Bump releasever in manifest.yaml
• Update the repos in manifest.yaml if needed
• Run cosa fetch --update-lockfile
• Bump the base Fedora version in ci/buildroot/Dockerfile
• PR the result

At Fedora (N) GA

Ship rebased testing

• Ship testing
  • Verify that the next -> testing promotion does not include platforms.yaml
• Set a new update barrier for N-2 on testing. In the barrier entry set a link to the docs. See discussion.

Disable branched stream

• Update streams.groovy to remove the branched stream in the list of mechanical refs.

Untag old packages

koji untag N-2 packages from the pool (at some point we'll have GC in place to do this for us, but for now we must remember to do this manually or otherwise distRepo will fail once the signed packages are GC'ed). For example the following snippet finds all RPMs signed by the Fedora 32 key and untags them. Use this process:

• Find the key short hash. Usually found here. Then:

f32key=12c944d0
key=$f32key
untaglist=''
for build in $(koji list-tagged --quiet coreos-pool | cut -f1 -d' '); do
    if koji buildinfo $build | grep $key 1>/dev/null; then
        untaglist+="${build} "
        echo "Adding $build to untag list"
    fi
done

• Now we have a list of builds to untag. But we need one more sanity check. Let's make sure none of those are actually being used. Fire up the latest FCOS testing-devel and run:

f32key=12c944d0
key=$f32key
rpm -qai | grep -B 8 $key

If there are any RPMs signed by the old key they'll need to be investigated. Maybe they shouldn't be used any longer. Or maybe they're still needed.

• After verifying the list looks good:

koji untag-build coreos-pool $untaglist

• Now that untagging is done, give a heads up to rpm-ostree developers that N-2 packages have been untagged and that they may need to update their CI compose tests to freeze on a newer FCOS commit.

• Remove the N-2 signing key from the tag info for the coreos-pool tag. The following commands view the current settings and then update the list to the 33/34/35 keys. You'll most likely have to get someone from releng to run the second command (edit-tag).

  • koji taginfo coreos-pool
  • koji edit-tag coreos-pool -x tag2distrepo.keys="9570ff31 45719a39 9867c58f"

Disable next-devel stream

We prefer to disable next-devel when there is no difference between testing-devel and next-devel. This allows us to prevent wasting a bunch of resources (bandwidth, storage, compute) for no reason. After the switch to N if next-devel and testing-devel are in lockstep, then disable next-devel.

• Follow the instructions here to disable next-devel

Switch upstream packages to shipping release binaries from Fedora (N)

• Update repo-templates config.yaml with the version number and GPG key ID for Fedora (N).

After Fedora (N) GA

Ship rebased stable

• Ship stable
• Set a new update barrier for N-2 on stable. In the barrier entry set a link to the docs. See discussion.

Open ticket for the next Fedora rebase

• Create a new ticket from the rebase template
  • label with FN label where N is the Fedora version.

Miscellaneous container updates

These are various containers in use throughout our ecosystem. We should update or open a ticket to track updating them once a new Fedora release is out. If you open a ticket instead of doing the update add a link to the ticket as comment.

• Update coreos-assembler or open ticket to update:
  • Dockerfile
• Update coreos-installer
  • Dockerfile
• Update Ignition
  • Dockerfile.validate
• Update Butane
  • Dockerfile
• Update fedora-coreos-cincinnati
  • Dockerfile
• Update config-bot
  • Dockerfile
• Update coreos-koji-tagger
  • Dockerfile
  • ImageStream
  • BuildConfig
• Update coreos-ostree-importer
  • Dockerfile
  • ImageStream
  • BuildConfig

[dustymabe]

• tracker: package additions/removals for F37 #1221
• tracker: Fedora 37 changes considerations #1222

[dustymabe]

• tracker: F37 Test Day #1225

[dustymabe]

• add Fedora 38 signing key to coreos-pool tag

[dustymabe]

• signing-keys: regular Fedora cycle rotation of keys for F37 cycle coreos-installer#963

[dustymabe]

• [rawhide] move to F38; various cleanups fedora-coreos-config#1921

[dustymabe]

• streams: enable branched stream fedora-coreos-pipeline#616
• [branched] manifest: bump to F37 fedora-coreos-config#1927

[dustymabe]

• [next-devel] Move to Fedora Linux 37 fedora-coreos-config#1967

[dustymabe]

• streams: re-enable next-devel fedora-coreos-pipeline#625

[dustymabe]

As with previous rebases we will fast track packages in order to prevent downgrades from happening over any upgrade transition (i.e. F36->F37).

[dustymabe]

• next: new release on 2022-09-13 (37.20220910.1.0) fedora-coreos-streams#558

[dustymabe]

Disabled branched in coreos/fedora-coreos-pipeline#686 - I think we can probably start doing this after next-devel gets switched to N.

[dustymabe]

Going to fast-track glibc-2.36-7.fc37 since it's in the latest RC.

[dustymabe]

Going to fast-track kernel-5.19.16-301.fc37 since it's in the latest RC.

[dustymabe]

Going to fast-track samba-4.17.1-1.fc37 since it's in the latest RC.

[dustymabe]

Fast-tracking a few more packages since a new RC was requested.

• glib2-2.74.1-1.fc37
• systemd-251.7-611.fc37
• mozjs102-102.4.0-1.fc37
• kernel-6.0.5-300.fc37

[dustymabe]

Fast-tracking a few more packages since a new RC was requested.

• kernel-6.0.7-301.fc37
• glib2-2.74.1-2.fc37

[dustymabe]

Need to override vim in the testing release because the current version we're using was obsoleted. We'll forward to the one that hit stable: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4bc60c32a2

[dustymabe]

PR to switch testing-devel to F37 content:

• manifest: Move to Fedora Linux 37 content fedora-coreos-config#2083

[dustymabe]

The fix for this went into testing stream release 37.20221106.2.1.

[dustymabe]

• streams: disable next-devel fedora-coreos-pipeline#761

[dustymabe]

• updates for Fedora 37 fedora-coreos-releng-automation#160

[dustymabe]

• openshift-apps: bump a few apps to Fedora 37

[prestist]

coreos-installer pr
ignition pr
butane pr pr2

Ok I have rebased these.

[jmarrero]

fedora-coreos-cincinnati: coreos/fedora-coreos-cincinnati#87

[jmarrero]

coreos-assembler: coreos/coreos-assembler#3212

[jmarrero]

openshift/release:
https://github.com/coreos/coreos-assembler/blob/main/Dockerfile#L1-L2 : openshift/release#34124

[dustymabe]

• config.yaml: bump current fedora to Fedora 37 repo-templates#64

[dustymabe]

The fix for this went into stable stream release 37.20221106.3.0.

[dustymabe]

• tracker: Rebase onto Fedora 38 #1356