This is a new feature in openQA that prevents worker hosts
picking up new jobs if their load average is above a certain
threshold. It defaults to 40. Our big worker hosts tend to run
above this, so let's bump it on those.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
openqa-x86-worker03 seems to be a bit poorly lately, it quite
often fails jobs in 'hardware blip' looking ways, even after a
reboot. It's also the equal-worst hardware in the worker host
pool with 05. So let's swap 03 and 06 so prod has most of the
best hardware, and lab has the poorly box. Also while doing a
quick hardware survey I noticed 05 is equally as underpowered
as 03 (it has 2x E5-2680v3, total 24 physical CPUs, all the
other hosts aside from those two have 2x16 core CPUs), so this
cuts its worker count to the same as 03 (and makes the comment
more accurate for both). Added comments to inventory with the
CPU info for each box for future reference.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Some of the openqa workers are encrypted and some aren't (this is a bit of a
mess that's partly a result of all the redeployments we did around
https://bugzilla.redhat.com/show_bug.cgi?id=2009585 ). We should only run
the nbde_client role on workers which are encrypted. Hopefully this gets that
right.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We don't need it for diagnosing a kernel bug any more, so take it
out of the special 'onebox' setup.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Using the machine's own hostname works for the ansible delegate
stuff but doesn't work for openQA itself (if you try and access
the DB by hostname like this, postgres denies access; you have
to use 'localhost' for postgres to allow it). Using 'localhost'
works for postgres but doesn't do the right thing for delegation.
Let's use 'localhost' and split the two play steps into
delegated and non-delegated versions.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is an attempt to add a group that'll set openqa-x86-worker05
as a one-box openQA instance which doesn't report results. This
is to try and help with debugging
https://bugzilla.redhat.com/show_bug.cgi?id=2009585 : the idea is
to have a disposable openQA instance where we don't care if all
the tests fail, so we can try out various things to resolve that
bug on it. Debugging on lab is awkward because we do actually
care about lab's results, especially since it's the only instance
testing Rawhide updates.
This requires quite a lot of surgery to get around various
assumptions in the existing groups and plays (no reporting of
results, no NFS...) and make the box its own postgresql server.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
