Right now we run a script on all builders once a minute to update the
api/auth ip's for osbuild. This has a number of problems:
* Sometimes osbuild jobs land on s390x builders that have no internet
access and hang or fail.
* Sometimes the update script hangs or takes a long time to run because
the builder is heavily loaded with builds, resulting in locking emails
to sysadmin-main folks.
So, in this commit we:
* make a new koji channel called 'osbuild' with all the buildhw-x86's in
it. They are usually not too overloaded and there are 16 of them so it
should be available all the time.
* Leave the cron job on all builders for now in case, but make them only
update once a day since they won't be getting jobs. If this works out
we can remove it entirely there.
* Make the buildhw-x86s only update every 5min. This opens a larger
window for it being wrong, but it's still pretty small and should
reduce the number of emails for stalled processes we get.
See https://pagure.io/fedora-infrastructure/issue/10982
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This reverts commit 3437042944.
This doesn't work on rhel8 machines:
/etc/crypto-policies/back-ends/opensshserver.config: line 1: Bad configuration option: CRYPTO_POLICY
/etc/crypto-policies/back-ends/opensshserver.config: terminating, 1 bad configuration options
EL6 and EL7 have a limited set of algorithms, but EL8 and Fedora use
system configs set in a different file. Added an elif to better try
and show this.
Signed-off-by: Stephen Smoogen <ssmoogen@redhat.com>
Javascript and CSS dependencies for Anitya are now managed by npm. Let's reflect
this in Anitya buildconfig.
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
fas, openshift kerneltest and the old openshift console/api are no more.
Remove them now to fix up reverseproxy templates.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
I think the recent git builds are good and I want them everywhere
so I can merge a bunch of things and clean up before the weekend.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Upgraded proxies and builders to f37. We have a reduced timeframe to get
this done before the holidays, so this time we just upgraded them in
place. Usually we do a full reinstall. We will try and do that next
cycle.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
New waiverdb container image starts 8 gunicorn web worker processes by
default using WEB_CONCURRENCY environment variable. This causes memory
to spike (over 500MiB) and workers to get terminated.
Instead of increasing memory limits, a better solution is to decrease
the number of processes and increase number of threads since the app
mostly waits on DB requests to finish and waiverdb workers themselves
are thread-safe.
