tracker: Fedora 34 rebase work

[jlebon]

This is still early, but I want us to start tracking Fedora 34 changes and evaluate which are relevant to FCOS.

Fedora 34 schedule:

# https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
2020-12-29 Change Checkpoint: Proposal submission deadline (System Wide Changes)
2021-01-19 Change Checkpoint: Proposal submission deadline (Self Contained Changes)
2021-02-09 Branch Fedora 34 from Rawhide
2021-02-12 Post-branch Freeze (end date approximate)
2021-02-23 Bodhi updates-testing activation point
2021-03-16 Beta Release (Preferred Target)
2021-04-06 Final Freeze
2021-04-20 Preferred Final Target date

List of system-wide and self-contained changes available in https://fedoraproject.org/wiki/Releases/34/ChangeSet.

Offhand, going through the list, here are some changes I think we should dig a bit into:

• DNS over TLS: we should sanity-check DoT works on FCOS (need to roll back to using systemd-resolved first)
• Restart services at end of rpm transaction: should sanity-check the scriptlet approach there gracefully no-ops in the rpm-ostree scriptlet container
• Rust Crate Packages For Release Branches: should adapt workflow/checklist of our Rust-based packages

[jlebon]

Related to this, we're working on setting up the rawhide stream which will help with getting CI coverage as well for any changes we need to make.

[travier]

https://fedoraproject.org/wiki/Changes/EnableSystemdOomd > This one might impact us or OKD.

[jlebon]

We'll want to drop at least this postprocess script: coreos/fedora-coreos-config#765.

[jlebon]

Note also we should be able to drop the systemd stub-resolv.conf relabeling hack in f34 (see coreos/fedora-coreos-config#780 (comment) and #751 (comment)).

[jlebon]

SOP for rebases now also include grepping f-c-c for TODO fNN to see if there are things we should add/remove/check at rebase time. (See e.g. coreos/fedora-coreos-config#882).

[jlebon]

Note: the beta go/no-go meeting is today. If it's a go, we should look at moving next over to f34 in either the next set of releases or the one after that.

[jlebon]

Beta was no-go. So let's stick with f33 for next for this week's release.

[jlebon]

F34 rebase note: need to ensure we have this NM or newer: https://bodhi.fedoraproject.org/updates/FEDORA-2021-fb173bc82f (for this patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/770).

[jlebon]

This was discussed in today's community meeting. If the go/no-go meeting tomorrow is go, then we will rebase next to f34 in the next release.

[jlebon]

next-devel rebase: coreos/fedora-coreos-config#902

[lucab]

Apparently this induced three downgrades in 34.20210328.1.0:

    conmon 2:2.0.26-1.fc33.x86_64 → 2:2.0.22-0.9.dev.git2fbeb9f.fc34.x86_64
    containers-common 4:1-4.fc33.noarch → 1:1.2.1-28.dev.git1b813f8.fc34.x86_64
    skopeo 1:1.2.2-1.fc33.x86_64 → 1:1.2.1-28.dev.git1b813f8.fc34.x86_64

[dustymabe]

Apparently this induced three downgrades in 34.20210328.1.0:

Next iteration should resolve this: coreos/fedora-coreos-config#931

Next time we'll catch it sooner.

[jlebon]

The schedule we're leaning on based on discussions during today's IRC meeting is:

Week 0 (GA): next release with bumped content
Week 1: testing release based on last next
Week 3: stable release based on last testing

where week 0 is the week when Fedora 34 actually GAs. This may end up meaning we shift our release schedule depending on whether GA is on a release week (Apr 27th) or not (Apr 20th).

We'll also publish next releases every week until testing gets f34.

[jlebon]

F34 is no-go for Apr 20th. The new target date is thus Apr 27th: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/2UHYXZ6LDWEQ2EUEL3QUMV753JKEAUXZ/.

[dustymabe]

Was browsing and ran across #676. Maybe we should look at that this round?

[jlebon]

Was browsing and ran across #676. Maybe we should look at that this round?

I think we were sort of hoping for a declarative way to drive this via alternatives, but it doesn't look like there are any plans to address this anytime soon. So agreed we shouldn't block on that to get this done.

[bgilbert]

We need to remember to run all of the steps in the rebase SOP. Would it make sense to convert that checklist into an issue template in this repo?

I've updated the coreos-installer signing keys in coreos/coreos-installer#530.

[jlebon]

We need to remember to run all of the steps in the rebase SOP. Would it make sense to convert that checklist into an issue template in this repo?

Yeah, that makes sense to me!

[bgilbert]

Issue template PR in #806.

[bgilbert]

Checklist in #808.

[travier]

Testing moved to F34 with this week's releases

[dustymabe]

We moved the stable stream starting with 34.20210427.3.0 in mid may.

The checklist ticket (#808) still has a few items left, but we can close this out.