tracker: Rebase onto Fedora 39

[dustymabe]

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

At previous Fedora major release

Open tickets to track related work for this release

• Fedora Changes Considerations (example) 👉 tracker: Fedora 39 changes considerations #1491
• Package Additions/Removals (example)
• Test Week (template)
• Fedora N Release Communications (example) 👉 tracker: Fedora 39 Release communications #1503

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 config.yaml to un-comment out the branched stream definition.

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 --dry-run --update-lockfile

  • this updates the x86_64 lockfile - the others will get updated when bump-lockfile runs.
  • in the future we may support this in cosa fetch directly

• PR the result

• Re-enable next-devel if needed (docs)

• Disable branched stream since it is no longer needed.

  • Update config.yaml to comment out the branched stream definition.

Ship rebased next

• Ship next
• Set a new update barrier for the final release of N-1 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
• Sync the lockfiles for all arches from next-devel
• Bump the base Fedora version in ci/buildroot/Dockerfile
• PR the result

At Fedora (N) GA

Ship rebased testing

• Ship testing
• Set a new update barrier for the final release of N-1 on testing. In the barrier entry set a link to the docs. See discussion

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).

Disable the fedora-candidate-compose repo

• Remove from the manifest.yaml of next-devel the fedora-candidate-compose repo

After Fedora (N) GA

Ship rebased stable

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

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
echo > untaglist # create or empty out file
for build in $(koji list-tagged --quiet coreos-pool | cut -f1 -d' '); do
    if koji buildinfo $build | grep $key 1>/dev/null; then
        echo "Adding $build to untag list"
        echo "${build}" >> untaglist
    fi
done

Now we have a list of builds to untag. But we need a few more sanity checks.

• Make sure none of the builds are used in N based FCOS. Check by running:

f32key=12c944d0
key=$f32key
podman run -it --rm quay.io/fedora/fedora-coreos:testing-devel rpm -qai | grep -B 9 $key
podman rmi quay.io/fedora/fedora-coreos:testing-devel

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.

• For any RPMS still used by N-1 based FCOS let's remove them from the untaglist. Check by running:

f32key=12c944d0
key=$f32key
podman run -it --rm quay.io/fedora/fedora-coreos:stable rpm -qai | grep -B 9 $key
podman rmi quay.io/fedora/fedora-coreos:stable

NOTE: This assumes stable is still on N-1.

Remove any entries from the untaglist file that are still being used.

• After verifying the list looks good, untag:

# use xargs so we don't exhaust bash string limit
cat untaglist | xargs -L50 koji untag-build coreos-pool

• 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"

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

[aaradhak]

• signing-keys: add Fedora 40 key coreos-installer#1264

[aaradhak]

• [rawhide] manifest: rawhide is now F40 fedora-coreos-config#2548

[aaradhak]

• [branched] manifest: bump to F39 fedora-coreos-config#2549
• config: enable branched stream fedora-coreos-pipeline#904

[dustymabe]

• config: enable next-devel fedora-coreos-pipeline#908
• [next-devel] manifest: bump to f39 fedora-coreos-config#2592

Edit Prestist

• config: disable branched stream fedora-coreos-pipeline#909

[dustymabe]

As we have done in the past we will be fast-tracking packages in next-devel/next to ensure no upgrade transition will ever include downgraded packages.

[dustymabe]

• first next release on F39:
  • next: new release on 2023-09-19 (39.20230916.1.1) fedora-coreos-streams#767
• PR with barrier set for last f38 next stream release:
  • Roll out stable 38.20230902.3.0, testing 38.20230918.2.0, next 39.20230916.1.1 fedora-coreos-streams#768

[dustymabe]

PR to promote last next to testing:

• [testing] tree: promote changes from next at 1a3b193 fedora-coreos-config#2710

PR to add a barrier for the last F38 testing release:

• Add barrier for last F38 testing stream release fedora-coreos-streams#801

[dustymabe]

In 38.20231027.2.0 it was the last 38 release of testing. it also happens to be the first release with the zincati problem. To avoid this problem we'll make the 38->39 update barrier (the one that satisfies https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/) be 38.20231014.2.0 rather than 38.20231027.2.0.

[dustymabe]

disabled next-devel in coreos/fedora-coreos-pipeline#945

shipped rebased stable in coreos/fedora-coreos-streams#822

[dustymabe]

• config.yaml: bump current fedora to Fedora 39 repo-templates#198

[dustymabe]

• [next-devel] disable candidate-compose repo fedora-coreos-config#2813

[travier]

Prepared a part of "Update fedora-coreos-cincinnati" earlier but forgot to link it here: coreos/fedora-coreos-cincinnati#95 (the follow-up steps are linked from the PR).

[c4rt0]

Miscellaneous container updates:
coreos-assembler Dockerfile already using F39 ✅

[c4rt0]

Coreos-koji-tagger ansible PR

[c4rt0]

coreos-ostree-importer PR