This sets us up for scheduling FCOS tests from messages, not
using a cron job. Also reduces some duplication of variables
between openqa-servers-common and the dispatcher role defaults.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I just enhanced the scheduler code so we can share the stock
WANTED definition (which now includes all arches) between prod
and lab, but filter the arches with a config file setting. This
means we don't have to carry and install a whole custom WANTED
file with the extra arches for lab any more, we just set the
appropriate value in the config file. Also drop some stuff from
the config file that's been useless since we switched to
fedora-messaging.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
As in fedora_openqa, drop this as it's been broken forever and
we are clearly not going to fix it. At some point I'll set up
32-bit-ARM-on-aarch64 testing. Hopefully.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is to reduce a flood of errors happening when servers the
consumers communicate with go down.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This just matches the updates to the default WANTED dict in
fedora_openqa - removing various old images that aren't produced
any more (Workstation netinst, Atomic Host, and all i386 images).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
fedora-messaging has an annoying bug where consumers get stuck
allegedly working fine but actually not handling any messages:
https://github.com/fedora-infra/fedora-messaging/issues/208
to deal with this on our openQA servers, just have the dispatcher
role install a cron job which restarts all the services nightly.
Strictly speaking this shouldn't really be part of a specific
role like this, but this is the easiest way to do it and it's
not really that "wrong".
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This adjusts the images.json.extraarches used on staging to
look for Cloud_Base qcow2 images now we want to test those too.
Prod uses the stock config baked into fedora_openqa, which has
also been adjusted.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We no longer build big-endian ppc64 images, so no point looking
for them. ppc64le remains of course.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We use a 'wanted images' config file for staging, which makes
us look for images from aarch64 and ppc64le arches; this was not
updated when AtomicWorkstation was renamed Silverblue, so we
haven't been scheduling Silverblue tests on staging at all...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It broke because python3 setup.py install installs binaries
to /usr/local/bin , not /usr/bin, so fedora-openqa is no longer
where the script expects it to be...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The correct auth bits are missing from the package so I'll ship
them here for now, and correct the config.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
These bits were still named and described as if they were ppc64
specific, even though they actually cover aarch64 too. Also I
decided I don't like the implementation of cueing *directly* off
the infra deployment type here, it feels wrong. Instead let's
just make it work from a config variable, and set that variable
to false by default and true in group_vars/openqa-stg.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
There are no fedmsg notifications for the live respin composes,
so we just try scheduling them every hour; when we've already
tested the current compose this will not create any new jobs,
and when a new compose shows up, this will test it.
We currently can't tell openQA to download the ARM kernel and
initramfs with a filename unique to the build being tested, so
they just get downloaded as `vmlinuz` and `initrd.img`, which
means that when the next compose is tested, we won't download
them again, we'll just use the existing copies (which are no
longer the right ones). Because of this our current 'F25' and
'Rawhide' ARM tests are actually still using some F24 kernel
image. Until the openQA bug which prevents us giving the files
unique names is resolved, here's a hacky workaround: a script
which wipes the files every hour if no openQA jobs are pending.