Also tweak how we do the plugin config a bit, I don't like the
whole 'do special stuff if deployment_mode is set' thing any
more.
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>
This ditches the ability to choose between fedora-messaging and
fedmsg and always uses fedora-messaging; with this, we'll switch
the prod instance to fedora-messaging also (fingers crossed).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I cargo-culted this from the Bodhi config but it's a special
Bodhi thing we don't have, so drop it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We had this for fedmsgs and it's pretty important, so let's try
and do it for fedora-messaging. The role has a generic setup,
infra-appropriate values are set in the group vars.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I thought just having it WantedBy remote-fs.target should be
enough, but in fact this mount often fails on boot, and I forget
to check all the worker boxes until a bunch of tests fail and
everyone is sad. Let's try After=network-online.target and see
if that helps.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
jcline said it'd be nice for consumers to provide more info
about themselves, so here's some more info!
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Now I've built the whole thing and it works, I feel like this
is a cleaner design: we use a lot more role variables in the
messaging config files, set defaults for them that are
appropriate for non-infra use, and set the correct values for
the infra servers in the group vars. Let's just hope I got it
all right...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
well, this just isn't working and no-one's around to debug it.
So turn it off for now. Will try and fix it tomorrow.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
env_suffix isn't actually set to .stg on openQA staging because
it's not a normal staging host. Let's not set it in case it
breaks other plays, but use a custom var instead.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The keys and certs have been created for us to use private auth
so let's do it. This tries to keep things working for non-infra
deployments somehow.
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 should really be secrets, but no-one's around to help me
set up new secrets right now, and it shouldn't matter a lot in
the short term at least.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is a big change to support fedora-messaging based consumers
instead of fedmsg ones in the openqa/dispatcher role. This needs
the fedora-messaging branch of fedora_openqa, until that is
merged to stable. For now this is all conditionalized so prod
will continue to use fedmsg. This also improves some variable
usage and documentation in the fedmsg path too.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
In ansible 2.8 the - character isn't supposed to be valid in group names.
While we could override this, might has well just bite the bullet and change it.
So, just switch all group names to use _ instead of -
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This is the config option added in the most recent openqa build
which prevents it cancelling an entire cluster of parallel jobs
if just one of the children fails. See:
https://progress.opensuse.org/issues/46295
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Hopefully this bit in tap-setup.yml can now go away, as this
approach of using ansible_ifcfg_whitelist and _disabled does the
same thing in a cleaner way.
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>
