Skip to content
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

templates/rebase: add step to delete stale Fedora versions from Greenwave policy #1739

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .github/ISSUE_TEMPLATE/rebase.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,10 @@ We prefer to disable `next-devel` when there is no difference between `testing-d
- [ ] 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](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-1247314065)

### Update CoreOS Greenwave settings

- [ ] Open an MR against https://pagure.io/fedora-infra/ansible to remove the N-1 Fedora release from the version list in [fedora.yaml](https://pagure.io/fedora-infra/ansible/blob/c636c0581319b655cdc49079bd3793eb78abbe78/f/roles/openshift-apps/greenwave/templates/fedora.yaml#_528) (see https://pagure.io/fedora-infra/ansible/pull-request/2036 for context).

### 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:
Expand Down
Loading