-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tracker: Rebase onto Fedora 38 #1356
Comments
When updating |
In general you may see us fast-tracking packages in |
coreos-status email: https://hackmd.io/aw7c1xNLRNSxcomW63Carw |
The fix for this went into |
The last release of f37 is a barrier, but the link won't be to the signing key issue because there was another reason to do it that way. |
Fedora 38 is a Go for Tuesday April 18th. The only package that we need that isn't currently in |
Part of rebase to Fedora 38: coreos/fedora-coreos-tracker#1356
Part of rebase to Fedora 38: coreos/fedora-coreos-tracker#1356
The fix for this went into |
Part of rebase to Fedora 38: coreos/fedora-coreos-tracker#1356
Part of rebase to Fedora 38: coreos/fedora-coreos-tracker#1356
For the "Set a new update barrier for the final release of N-1 on $STREAM" we'll let the update barriers that we put in place for #1441 suffice here. |
|
The fix for this went into |
f36 based packages have been untagged from the koji pool and the f36 key has been removed using |
The only steps remaining in this one are the container updates, which have now been superseded by Fedora 39. Tracked at #1490. |
Rebase to a new version of Fedora (N=38)
At previous Fedora major release
Open tickets to track related work for this release
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
koji add-pkg --owner dustymabe f36-coreos-continuous fedora-release
fedora-release
RPM, but it could be any other.koji tag-build f${N+1}-coreos-continuous $BUILD
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
rawhide
streamEnable
branched
streambranched
stream definition.At Fedora (N) Beta
Update fedora-coreos-config
next-devel
Bump
releasever
inmanifest.yaml
Update the repos in
manifest.yaml
if neededRun
cosa fetch --dry-run --update-lockfile
bump-lockfile
runs.cosa fetch
directlyPR the result
Re-enable
next-devel
if needed (docs)Disable
branched
stream since it is no longer needed.branched
stream definition.Ship rebased
next
next
next
. In the barrier entry set a link to the docs. See discussionPreparing for Fedora (N) GA
Update fedora-coreos-config
testing-devel
releasever
inmanifest.yaml
manifest.yaml
if needednext-devel
ci/buildroot/Dockerfile
At Fedora (N) GA
Ship rebased
testing
testing
testing
. In the barrier entry set a link to the docs. See discussionDisable
branched
streambranched
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:Now we have a list of builds to untag. But we need a few more sanity checks.
N
based FCOS. Check by running: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.
N-1
based FCOS let's remove them from the untaglist. Check by running:NOTE: This assumes
stable
is still onN-1
.Remove any entries from the
untaglist
file that are still being used.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
streamWe prefer to disable
next-devel
when there is no difference betweentesting-devel
andnext-devel
. This allows us to prevent wasting a bunch of resources (bandwidth, storage, compute) for no reason. After the switch to N ifnext-devel
andtesting-devel
are in lockstep, then disablenext-devel
.next-devel
Switch upstream packages to shipping release binaries from Fedora (N)
After Fedora (N) GA
Ship rebased
stable
stable
stable
. In the barrier entry set a link to the docs. See discussionOpen ticket for the next Fedora rebase
FN
label whereN
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.
The text was updated successfully, but these errors were encountered: