* Add test to check module defaults.
* Add whitelist download.
* Fix install test to include selected profile to be on the safe side.
* Add test into templates.
Fedora stopped supporting big-endian ppc64 and producing images
for it after F28, which is now EOL. So we can drop all these
bits for it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This reverts commit 5bc343fd7e.
Turns out this created a new job group, which I wasn't really
meaning to do. I'll tweak checkwiki to not choke on this.
We stopped building Atomic Host images from F30 onwards, so we
shouldn't expect to run tests for any version other than 29 any
more (28 is EOL).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We can run these tests much like support_server - have a test
which boots from the support_server disk image but with the ISO
to be tested attached, then mounts it and runs the scripts.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
...install_default_upload is now the same thing, since you
cannot create a user during install any more.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Some tests on Rawhide started failing back in April due to
insufficient space. I dug into it for an hour or two but can't
find any big smoking guns where unnecessary packages got added
to groups or some package suddenly got bigger or anything, so I
can't find any real bugs to report here; we're just gonna have
to bump the sizes.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This, for some reason, made the test fail on x86_64 but not on
ppc64le. I do not understand computers.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is covering the NFSISO_variation test as per:
https://fedoraproject.org/wiki/QA:Testcase_install_repository_NFSISO_variation
Change support_server to use support_5 disk image in templates
supposed to be previously created by updated createhdds tool
required for new test.
Signed-off-by: Guy Menanteau <menantea@linux.vnet.ibm.com>
This should not be set here; it is set in the 'product' (i.e.
the flavor), so it's set to 'gnome' for Workstation live flavor,
'kde' for KDE live flavor. Setting here overrides that and makes
it always 'gnome', we don't want that.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is the magic variable to disable openQA's "cancel whole
cluster on child failure" behaviour that I'm adding in
https://github.com/os-autoinst/openQA/pull/2017 . We want it
set for all parallel parent suites in Fedora.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is using the two tests previously added by
"Test upgrade of FreeIPA server and client deployment"
Signed-off-by: Michel Normand <normand@linux.vnet.ibm.com>
Obviously an installer image may work fine for a BIOS install
but fail for a UEFI install, so we should test it both ways.
This requires the invention of a new (terribly named, but I
couldn't think of anything better...) variable to allow us to
use the 'run test on machine A after test run on machine B'
mechanism without just hardcoding '64bit' as the machine name
in the START_AFTER setting (which would break if we ever wanted
to run update tests on any *other* arch).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This adds a test which builds a netinst image potentially with
the package(s) from the update, and uploads that image. It also
adds a test which runs a default install using that image. This
is intended to check whether the update breaks the creation or
use of install images; particularly this will let us test
anaconda etc. updates. We also update the minimal disk image
name, as we have to make it bigger to accommodate this test,
and making it bigger changes its name - the actual change to
the disk image itself is in createhdds. We also have to redo a
bunch of installer needles for F28 fonts, after I removed them
a month or so back...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Today's Workstation live doesn't boot at all without enforcing=0.
We *still* want to see how subsequent tests run, so let's work
around this for now.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is known to not work at present as it's not implemented in
DNF yet; failing on it every day isn't proving much. Once it's
implemented (expected by end Jan) we can turn it back on again.
See https://bugzilla.redhat.com/show_bug.cgi?id=1616167
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We weren't using the gpt-labelled one, so I took it out of
createhdds; that makes the name of the mbr-labelled one lose
its label tag, so we need to update that name here.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
fd files don't work on aarch64, it seems. Drop BIOS even though
it's probably not breaking anything as I don't intend to move
aarch64 to prod until prod is up to new openQA, so no need to
stay compatible.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
In recent os-autoinst the old 'stuff it all in HDDMODEL' doesn't
work and tells you to do it like this. This way does work in the
older os-autoinst currently on prod too, so this should be fine.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We're about to deploy recent os-autoinst to staging. The UEFI
stuff got rewritten since the version we currently have, and
this is now the recommended way to handle UEFI firmware. The
new vars shouldn't confuse the old code still deployed on prod,
it should just ignore these vars and keep working off the old
'UEFI=1' (which causes it to autodetect the file locations).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We updated the dispatcher code, but not the templates...so we
didn't have any actual tests to run on Silverblue images. Let's
fix that. Note this means we won't test F28 and earlier images
that still have 'AtomicWorkstation' as their subvariant any
more, unless I set up some sorta workaround in the dispatcher.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Time for the great video driver merry-go-round again...lately
we're having some issues with vt corruption and rendering over
the boot splash, let's try using 'std' driver to see if it
helps a bit. stg has been set up this way for a couple of days
and it's not blowing up at least.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
They can't be in universal as there's no install_default_upload
for them to run after. Let's just run on the Server DVD install
like we do many other post-install tests.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This adds a set of jobs to test FreeIPA replication. We deploy
a server, deploy a replica of that server, then enrol a client
against the replica and run the client tests.
At first I was planning to add the replica testing into the
main set of FreeIPA tests, but the test ordering/blocking (via
mutexes and barriers and what-have-you) just turns into a big
nightmare that way. This way seems rather simpler to deal with.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
qemu 2.11.2 fixes#1403343, so we can go back to using qxl for
x86_64 VMs. Also, setting QEMUVGA doesn't actually do anything
on aarch64 (os-autoinst ignores it and sets up virtio graphics
instead), so let's not set it to avoid confusion.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
...to try and avoid running into RHBZ#1572916, which is killing
Rawhide tests it seems. Let's hope this doesn't result in host
entropy starvation. If it does I might try patching os-autoinst
to seed virtio-rng from /dev/urandom, not /dev/random...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This adds the FreeIPA server and client upgrade tests to a new
updates-server-upgrade flavor which fedora_openqa will schedule
for updates. This way, we can test whether updates break
FreeIPA upgrades, which is a request the FreeIPA team made to
me. This has been deployed on staging for the last week or so
and appears to work fine.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
KDE package set install constantly runs into #1541433. While
that's not being fixed, let's bump the disk size so we can see
if the install actually works.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Tweaking aarch64 settings a bit to try and improve reliability.
I'm going to cut down to 3 workers per box along with this.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This reduces duplication, but it also means that if the FreeIPA
web UI module fails, the password change module will pick up
from a point where Firefox is set up and won't fail in a bogus
way because it isn't.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
