Also fix missing variable reference for the main role deployment
playbook.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
rh-pre-commit.version: 2.4.0
rh-pre-commit.check-secrets: ENABLED
The current updates policy has the same rules for Branched after
Beta freeze / updates-testing activation as for stable releases,
so we don't need a specific Branched policy after that point at
all. It only needs to exist for the 'preenable' state. The
'current' state is useless, so get rid of it.
The Koji config handling was actually rather wrong in a few ways.
If we ever got into a situation where FedoraBranched was true
and FedoraBranchedBodhi was 'current', we'd allow block on the
branch, which seems bad. Also, because this block wasn't
conditionalized on FedoraBranched and FedoraBranchedNumber is
0 when FedoraBranched is false, we wound up defining a policy for
tag 'f0', which is also dumb (but probably harmless). Getting
rid of 'current' solves the first, conditionalizing the policy
on FedoraBranched solves the second.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
we are now in the infrastructure freeze leading up to the Fedora 44
Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 44 Beta when it's available.
You can always check if an infrastructure freeze is in place by
checking the value of the InfraFrozen variable at:
https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone
https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml
ansible/scripts/freezelist -i inventory
Any host listed as "freezes" is frozen until 2026-03-10 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list and/or a pull-request to the infra/ansible repo.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
10 is not enough, the queue started growing again after few days on
staging. Let's set it to 15. This seems to hold.
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
See https://pagure.io/fedora-infrastructure/issue/12932.
The Bodhi needs some optimization as the processing of some messages
takes 40 seconds. We need to keep at least 10 consumers to handle the
load on staging.
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
This introduces a set of variables for managing infrastructure changes
as EPEL minor versions change over time. This should drastically
simplify our changes during EPEL mass branching. This also drops the
earlier attempt of EPELCycleNumber and EPELBootstrapNumber variables,
which are no longer used.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
