This should enable dist-git PR testing in prod, and make *only*
prod report status back to dist-git (staging no longer should).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
bvmhost-a64-03 has a bad memory slot, so needs to be sent back to get
fixed/replaced. In the mean time lets replace it with buildhw-a64-02,
which has the same specs.
When the fixed one comes back we can make it a new buildhw-a64-02.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We are moving 02 out to become the new bvmhost-a64-03 while that one is
shipped back for repairs. 03 will take over on secureboot.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This reverts commit db0b9e4f0c.
This is not the correct knob to adjust number of attempts.
This is number of things that have to be successfull before unlock.
1 is right here. ;(
We have 3 compose builders, but we don't really need all of them I don't
think. The rawhide composes do boot.iso for everything and server
and server dvd here, so 2 builders I think should be fine.
Lets move this one to be a general builder to try and prevent
backlogs.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Seems like there are a ton of really small connections and it starts
hitting the limit (although it never logs that it's out, I think because
they free up quickly).
See if this solves the transitory alerts we see.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This pr attempts to move sshd to port 222 on proxy01.stg and
proxy02.stg.
We want to do this (first here and then in prod) because we want to nat
in ssh from external and use haproxy to send that into
forge.fedoraproject.org. If we were using port 22 to connect here
it would conflict with forwarding it on to haproxy.
Note that we still need to actually get networking folks to make the nat
mapping and we still need to add haproxy config to send it into forge in
openshift, but this is the first step we need to get working before we
can do those things.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
See infra/tickets#13422
for details on this. It seems like rabbitmq staging has been
switch to the 'new' CA cert, and the consumers don't actually
read/trust both certs in the combined CA cert file, only the
first (old) one, so they don't trust the new one. This should
deploy and use a new file with only the new CA cert in it. We
copy it out of the private repo for convenience but it's not
actually private, hence the 0644 perms.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I'm having auth issues on openQA staging, I believe it *may* be
to do with the changes Aurelien made in
6fe8b98de21747dc16d59dcf5096da719a541296 . Let's see if using the
old key and cert helps.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This *should* configure a new queue and consumer for openQA to
report dist-git PR test results back. It's all a bit speculative
ATM, may need some tweaking. Mostly applied only on staging for
now.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
