Drop the HDDSIZEGB change as it was no use (we're constrained by
the size of the support server disk image here, not the second
disk, that's only used for something else). Let's try symlinking
the relevant contents of the disc image to the directory we share
out via NFS, rather than rsyncing them. This should save space
and time.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We need to disable these sockets as well or resolved pops right
back up and interferes with dnsmasq, now.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Previously the name of the application was ExtremeTuxRacer,
but it was changed to extremetuxracer. The application could
not be installed, so this should fix it.
As requested by @kparal in
https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/417 ,
this matches the modified test case by creating the EFI system
partition and /boot partition on RAID devices, as well as the
root partition. Also let's make them a bit bigger; if we leave
the value at 512 they actually get created 511MB big (dunno why)
and anaconda complains. Anyway, bigger sizes are prudent these
days.
We also need to create a BIOS boot partition on the second disk
in the BIOS test now. Apparently if /boot is RAID-ed, there has
to be a BIOS boot partition on each disk. This is a bit of an
ugly implementation, oh well.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
INSTALL_RETRY was introduced to try and retry live installs five
times to mitigate the effects of
https://bugzilla.redhat.com/show_bug.cgi?id=2329581 . That bug is
fixed, but we *do* still have some flakiness in live install
tests; we still occasionally hit the thing where install just
stalls for no obvious reason, we sometimes hit
https://bugzilla.redhat.com/show_bug.cgi?id=2402533 , and
(especially on KDE due to
https://bugzilla.redhat.com/show_bug.cgi?id=2404262 ) we sometimes
get failures caused by mistyping in language select or user
creation.
So let's keep INSTALL_RETRY around, and use it on more tests -
these are all webUI install tests that run on the live images -
but drop it to 1, 5 is probably overkill for the current known
issues.
Also, let's define it for all flavors. In the initial commit I
wrote that if it was not defined, RETRY would be set empty, but
that's not true. What actually happens is RETRY gets set to the
literal string %INSTALL_RETRY%, which is goofy. openQA still
seems to interpret it as "don't retry", which is good, but let's
avoid it.
Also move the workstation_live_iso definition into the flavors
with all the others, I don't know/remember why only that one
was in products.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The previous needle commit did not solve the situation with
routing, the error seems to be there still. However, the search
test was failing because of expired needles. This commit adds
the replacements to make that test finally pass.
Just accepting page 2 isn't enough to fix the test, as lots of
later parts of it expect that we're on page 1. So let's try and
handle that.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It seems to prevent notifications appearing in openQA tests,
probably because we're rate-limited. I checked that I *do* get
notifications in a local VM.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Sigh, tests are failing on GNOME now - we're seeing the DBX
update even though we mask lvfs. Software must be catching it
before we mask lvfs or something. So let's wipe the plugin for
GNOME too. And use a somewhat more robust way of doing it, I
hope.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
So I'm really remembering all the fwupd/lvfs issues now. When
there's a UEFI DBX update available, we'll see it. This can cause
different issues. Right now on KDE, we're trying to install it,
but LVFS is blocking the download because it thinks we're spamming
it. So that's making tests fail.
We really need to go back to just nerfing LVFS. I think I found a
way to do it on KDE that works with current Discover: just wipe
Discover's lvfs plugin entirely. This will break if the filename
changes.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
With French install testing on lives, we *might* have a French
layout loaded when we get to the postinstall stuff we do at a
root console. Let's defend against that. If we don't, running
"loqdkeys" will fail harmlessly.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Sigh. So we stopped masking fwupd becuase it caused Discover to
blow up, but now I remember why we started doing it in the first
place: fwupd can cause another 'type' of update to appear in
GNOME Software, with an identical "Restart & Update" button,
which openQA will happily click on instead of the one for
"System Updates" which we *want* it to click on. See
https://openqa.fedoraproject.org/tests/3880370#step/desktop_update_graphical/36
So...let's go back to masking fwupd, but only on GNOME. This
should make everyone happy.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
For some reason typing 'abrt' now launches Partition Manager(?!),
so we need to type 'problem' instead, and do checkstart ourselves.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This adds a test for remote connection. It consists of a server part
in which Gnome RDP connection is set up, enabled, and the server is run,
and the client part that uses Connections as a client to connect to the
server.
The test is considered successful when the connection is established
and the user has logged into the system.
Fixes: https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/333
This allows us to set defaults for settings in ProductDefaults
and have the settings dicts in individual products merge with
them, not overwrite them.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
As of yesterday, all the *-packages.yaml files are gone. Listing
all the files that have packages: blocks in them is a pain, and
common.yaml now exists on all current branches, so let's just do
that sub in common.yaml, it should work.
Also, common.yaml no longer uses `ref: fedora/` but
`ref: ${distro}/`, so that substitution broke, which is why the
test is now failing when building the installer image (we can't
find the ostree under the ref we're expecting). Fix that.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This reverts commit 8a657904d0.
We already had a tweak in _ostree_build to put python3-rpm in the
ostree; the real problem is that had broken with changes to
workstation-ostree-config. The next commit solves it properly.
This started failing in install_default_update_ostree
_advisory_post because the ostree no longer has python3-rpm baked
in, by the looks of it. Moving the execution of updvercheck.py
into a toolbox container *should* fix it with no undesirable side
effects, I hope. It looks like /tmp should be shared between the
host and the container so the file location should be OK.
The use of `toolbox run --` as a wrapper instead of interactive
toolbox entry/exit was suggested by Gemini PR review:
https://github.com/AdamWill/os-autoinst-distri-fedora-ai-test/pull/26#discussion_r2431461670
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Assisted-by: Google Gemini Code Assist
We are missing a check that the expected keyboard layout is used
at the desktop, for non-switched layouts (e.g. French). This is
actually broken for Workstation live installs at present, so we
really ought to be testing it. Along the way, let's clean up the
conditionals a bit, and let's do the actual input testing at a
console not the overview, since we want to do it on KDE as well
as GNOME now, and KDE's kicker menu is a pain to type in.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Also add keyboard layout selection handling for webUI, natively
for the KDE live, via GNOME settings for Workstation live.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We don't used switched keyboard layout for this test yet because
unfortunately it's just completely broken on the webUI path.
There's no viable way to set up the correct layout configuration
during install at present. So this is just a translation test
currently.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The bug causes a crash at boot on Silverblue installer, we need
the fix to stop all Rawhide Silverblue tests failing.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
3G is really tight these days. We were limiting this because the
old worker hosts didn't have a ton of RAM, but the new ones have
plenty.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This reverts commit 1a8f7e466c.
Current Plasma Discover complains if fwupd is masked. I just hope
tests don't start failing on fwupd errors again now. Sigh.
FreeIPA team bumped the F41 NVR past the F42 one, so now upgrade
tests from F41 to F42 are broken. To workaround this we need
bumped rebuilds for F42, F43 and F44, because if only do F42 the
problem moves to F42->F43 upgrades, etc.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I did this to check the size of an image built with a lorax
scratch build I was testing, but then figured heck, why not also
do it permanently?
Signed-off-by: Adam Williamson <awilliam@redhat.com>
81d5d2f408 inadvertently dropped
this, then I carried that change over in the profile group
rewrite. I never intended to turn it off on KDE, though - it was
likely just a git rebase mishap or something. So let's turn it
on for KDE by using the "updates-desktops" profile group like we
do for all the others.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The top panel stays in the application and does not hide. I might be
caused by the mouse being in top area which normally invokes the
panel to appear. Let's move the mouse and click into the middle
of the screen to free the top area.
For some reason, the login name is filled in double time.
Let's fix it with adding more wait time and also an extra
delete key to wipe the field properly.
