-
Notifications
You must be signed in to change notification settings - Fork 21
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
testing: release 31.20191211.1 #35
Comments
Promotion from |
One more time (because the previous one short-circuited): https://jenkins-fedora-coreos.apps.ci.centos.org/job/fedora-coreos/job/fedora-coreos-fedora-coreos-pipeline/10721/ |
https://pagure.io/releng/issue/9094 (I've also sanity checked again that it resolves coreos/fedora-coreos-tracker#322). |
OSTree commit imported. Confirmed that a local VM can upgrade to the signed commit:
|
Release job completed, |
Rollout PR: #36 |
Sync'd to S3. Download page is updated. Edges are showing up in Cincinnati. Rollout started. |
I unstuck my canary and posted the instructions to ML and to the tracker: coreos/fedora-coreos-tracker#322 (comment). It correctly auto-updated and rebooted. |
This is properly rolling (around 50% done right now) with no major issues so far. Closing this ticket. |
First, verify that you meet all the prerequisites
Pre-release
Promote testing-devel changes
From the checkout for
fedora-coreos-config
(replaceupstream
below withwhichever remote name tracks
coreos/
):git fetch upstream
git checkout testing
git reset --hard upstream/testing
/path/to/fedora-coreos-releng-automation/scripts/promote-config.sh testing-devel
git show
testing
branch on https://github.com/coreos/fedora-coreos-configBuild
testing
, and fill in version number using theN.YYYYMMDD.P
format, pending finalization of Version numbering for OS releases fedora-coreos-tracker#81)Sanity-check the build
Using the the build browser for the
testing
stream:testing
release (in the future, we'll want to integrate this check in the release job)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.Importing OSTree commit
In the future, the OSTree commit import will be integrated in the release job.
cosa run -d /path/to/previous.qcow2
) and verifying thatrpm-ostree upgrade
works andrpm-ostree status
shows a valid signature.Run the release job
testing
and the new version IDAt 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:
updates/testing.json
:rollout
has astart_percentage
of 100) and set itsversion
to the most recent completed rolloutversion
field to the new versionstart_epoch
field to a future timestamp for the rollout start (e.g.date -d '2019/09/10 14:30UTC' +%s
)start_percentage
field to0.0
duration_minutes
field to a reasonable rollout window (e.g.2880
for 48h)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 runningdate -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 @{}
.NOTE: In the future, most of these steps will be automated and a syncer will push the updated metadata to S3.
The text was updated successfully, but these errors were encountered: