test_models.py is not packaged, so we need to use a modified
patch file with the changes to that file stripped.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
728b6c57a3 inadvertently put the
annotations in the wrong place for bodhi-celery (in spec, not in
metadata).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
See https://github.com/fedora-infra/bodhi/pull/6110 . We want to
be able to gate (only) Fedora ELN kernel updates via gating.yaml
(RemoteRule). However, if we just turned on the RemoteRule policy
for "fedora-eln", suddenly hundreds of existing gating.yamls which
specify "fedora-*" would apply to ELN, which we don't want.
To solve this, we will make Bodhi use "eln" not "fedora-eln" as
the product_version for ELN. That requires us to add "eln" to the
null policies. Let's also enable RemoteRule for "eln" at the same
time. This should not cause any existing policies to apply (unless
there are any which just specify '*', I guess) but will allow us
to add a kernel policy that applies to 'eln'.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Set DEBUG=true for staging OpenShift deployment (both the main
Deployment and the sync CronJob) to enable debug logging.
Remove the entire roles/blockerbugs/ directory which was the old
VM-based deployment (Apache/WSGI). This role has been fully
superseded by roles/openshift-apps/blockerbugs/ and is not
referenced by any playbook.
Assisted-by: Claude Opus 4.6
* nftables: (2 commits)
Cleanup nft merge. Chg osbuildapi and nft_custom_rules to use nft_table_filter.
...
Signed-off-by: James Antill <james@and.org>
We were copying in the req instead of the ca, so this messaging hook has
been broken for a long while. This is the hook that notifys on uploads.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
It seems like the alerts we have been getting have been when proxies are
near the limit rejecting things via anubis, but unable to keep up.
So, lets try and jump this up a bit and see if it solves those
alerts/slowdowns.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This had the hard coded mac address of the previous vm.
We moved to using ansible to just fill in the current mac, so fix that
here too.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We need to do this anyhow, but this will test to see if the weird alerts
we have been getting persist on f44 with the latest libvirt machine
setup.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
