You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Run the release job
Run the release job, filling in for parameters next and the new version ID
Post a link to the job as a comment to this issue
Wait for job to finish
At 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)
Wait for all releases that will be released simultaneously to reach this step in the process
Go to the rollout workflow, click "Run workflow", and fill out the form
Rollout general guidelines
Risk
Day of the week
Rollout Start Time
Time allocation
risky
Tuesday
2PM UTC
72H
common
Tuesday
2PM UTC
48H
rapid
Tuesday
2PM UTC
24H
When setting a rollout start time ask "when would be the best time to react to
any errors or regressions from updates?". Commonly we select 2PM UTC so that the
rollout's start at 10am EST(±1 for daylight savings), but these can be fluid and
adjust after talking with the fedora-coreos IRC. Note, this is impacted by the
day of the week and holidays.
The later in the week the release gets held up due to unforeseen issues the more
likely the rollout time allocation will need to shrink or the release will need
to be deferred.
Manual alternative
Make sure your fedora-coreos-stream-generator binary is up-to-date.
NOTE: In the future, most of these steps will be automated.
Housekeeping
If one doesn't already exist, open an issue in this repo for the next release in this stream. Use the approximate date of the release in the title.
Issues opened via the previous link will automatically create a linked Jira card. Assign the GitHub issue and Jira card to the next person in the rotation.
The text was updated successfully, but these errors were encountered:
plume: couldn't publish image in ap-southeast-5: couldn't grant launch permission on ami-0c3880973da8610a6: OperationNotPermitted: You can���t publicly share this image because block public access for AMIs is enabled for this account. To publicly share the image, you must call the DisableImageBlockPublicAccess API.
First, verify that you meet all the prerequisites
Edit the issue title to include today's date. Once the pipeline spits out the new version ID, you can append it to the title e.g.
(31.20191117.1.0)
.Pre-release
Promote next-devel changes to next
ok-to-promote
label to the issuenext
branch on https://github.com/coreos/fedora-coreos-configManual alternative
Sometimes you need to run the process manually like if you need to add an extra commit to change something in
manifest.yaml
. The steps for this are:git fetch upstream
git checkout next
git reset --hard upstream/next
/path/to/fedora-coreos-releng-automation/scripts/promote-config.sh next-devel
next
branch on https://github.com/coreos/fedora-coreos-configBuild
next
, leave all other defaults). This will automatically run multi-arch builds.Sanity-check the build
Using the the build browser for the
next
stream:next
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.Run the release job
next
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)
Rollout general guidelines
When setting a rollout start time ask "when would be the best time to react to
any errors or regressions from updates?". Commonly we select 2PM UTC so that the
rollout's start at 10am EST(±1 for daylight savings), but these can be fluid and
adjust after talking with the fedora-coreos IRC. Note, this is impacted by the
day of the week and holidays.
The later in the week the release gets held up due to unforeseen issues the more
likely the rollout time allocation will need to shrink or the release will need
to be deferred.
Manual alternative
fedora-coreos-stream-generator
binary is up-to-date.From a checkout of this repo:
sync-stream-metadata
job syncs the contents to S3Update graph manual check
NOTE: In the future, most of these steps will be automated.
Housekeeping
The text was updated successfully, but these errors were encountered: