The reposplit cron job runs on the first day of the month and deletes
anything older than 30 days old at that time. However this has caused
a disk crunch on centos stream as each day is 195 GB of data and 60
days of traffic was over 8TB. The cron job is now to run every Sunday
and remove any data older than 14 days.
The same is done for the RHEL splitter as its space was growing also.
Signed-off-by: Stephen Smoogen <ssmoogen@redhat.com>
koji upstream added a inactivity check for sidetag-cleanup. Since we
don't specify it, we get the default (10days). Thats a bit short, so we
explicitly set it to 21 days for now and can adjust it more later.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This will allow abrt-java-connector to be built directly from the fork. For now
only allowed on staging to test first.
See https://pagure.io/fedora-infrastructure/issue/9728
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
The httpd wasn't able to open a new socket for connecting to identity server,
this fix will allow that.
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This kinda goes along with:
https://github.com/fedora-infra/bodhi/pull/4759
but neatly, we don't need to wait for that to be merged or
deployed, we can do it right away and it'll work fine now but
also DTRT when we switch to grouped mode in Bodhi. This splits the
greenwave policies for openQA update tests into groups according
to the test flavors, and has each grouped policy apply to what
will be the correct decision contexts for Bodhi's grouped critpath
support. We *also* have each grouped policy apply to the existing
non-grouped contexts, so as long as Bodhi is running in
non-grouped mode, things should behave exactly the same: all
critpath updates will be gated on all the tests.
We ensure every critpath group is listed in the null policies,
to make sure we don't get errors when Bodhi queries against them.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
300G doesn't seem like enough when we have candidate composes
alongside Rawhide and Branched, we're getting incomplete tests
because assets are being removed.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Prevent these jobs from running so long that new jobs can get started
meanwhile. batcave has been observed to run sometimes dozens of old
list-vms-per-host processes under unusual but not rare circumstances.
