When there are critical updates available, the message differs.
This is the first time we've had critical updates since the
font change.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This caused problems (particularly with the more obscure package
install paths like cockpit and realmd) before, but I don't really
like removing it, as it differs from real-world usage. Tests are
currently failing because of a bug in this repo wiping - in
upgrade_preinstall, we should wipe the file again after the
dnf -y update --refresh call, in case that reinstalls it - but
instead of fixing that, let's try just leaving the file alone.
The risk here is that we run into problems when the repo doesn't
exist, again. In theory we should not because it has
skip_if_unavailable=True , and everything *should* respect that.
But if it does turn out to still be a problem we'll have to
revert this and fix upgrade_preinstall.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We currently use script_run (not assert_script_run) for the
catch-all update we run at the start of the test, and don't use
--best. This means that if a dependency issue happens at this
point, we don't catch it yet, we only catch it in _advisory_post.
By using assert_script_run and --best, we can fail on dep issues
at this point. We have to keep the _advisory_post check to catch
dep issues that crop up *later* in the test, including when
things like Cockpit or GNOME Software install updates and we
can't force them to use --best logic. But we can at least catch
*most* of them earlier this way.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Because of the 'can't go from > 41 to <= 41' issue, we need to
tweak the coreos rebase targets to get the tests to pass.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I think since the wayland port, sometimes clicks on
anaconda_blivet_part_drop_select are missed and don't open the
menu. So, if that happens, click it again.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
it seems like sometimes we delete the entire btrfs volume instead
of the root device we're trying to delete; I think this is
because we click delete *immediately* after clicking the device,
and that might be too fast. Let's see if a wait_still_screen
helps. See:
https://openqa.fedoraproject.org/tests/3353598https://openqa.fedoraproject.org/tests/3299570
etc.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This came up in blocker bug meeting discussion today. We really
should check that all packages are signed after a default install.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This one is only needed if we don't see another log detail title
that we usually do see, so it escaped being updated for a while.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
@lruzicka recently made this test click through the setup page,
if it sees it...but he used new needles (which he didn't commit)
even though we already have those same needles as part of the
detailed contacts app test.
This setup page always appears, we don't need to check for it,
and we don't need separate needles to identify the page and to
click on the local address book option. All we need to do is the
same as we do in aaa_setup: unconditionally look for and click
the local address book option, using the already-existing needle.
So let's do that.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The flatpak and RPM versions have different line spacings, I
think because the flatpak has an older GTK. This affects several
needles.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Seems like GNOME 48 changed window size/positioning a bit, we
have to move the text editor so it will still be visible when
the file manager window is in the front.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The current check never fails - if we don't see the details after
30 seconds, we never actually assert them. We may or may not
soft fail, but we'll never fail.
This simplifies the check (there's no need to specifically look
for the 'loading' screen) and makes it actually fail if the
details don't show up in 90 seconds total.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
These only appear in the RPM version of the test (the flatpak
uses the portal, so it gets a different file dialog).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The 'settings' menu is replaced by an 'info' panel, and *most* of
the things from 'settings' moved to 'preferences'. But Document
Type is in the 'info' panel. Just to make things fun. The grid
feature is gone. And of course all the needles needed updating
for the new font. The flatpak build is still 47 and so has the
old UI but the new font, and line spacing in it seems slightly
different, so we need conditional paths and more needles. Yay.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
