mirror of
https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git
synced 2024-11-18 04:23:08 +00:00
9d8a35ed39
There's one point in the tests where we may log into cockpit for the second time in one run (it depends how a package update process goes). When this happens, we don't get prompted again for admin access, so we need to *not* expect that. Signed-off-by: Adam Williamson <awilliam@redhat.com>
50 lines
1.3 KiB
Perl
50 lines
1.3 KiB
Perl
use base "installedtest";
|
|
use strict;
|
|
use testapi;
|
|
use utils;
|
|
use packagetest;
|
|
use cockpit;
|
|
|
|
sub run {
|
|
my $self = shift;
|
|
|
|
# Start Cockpit
|
|
start_cockpit(login => 1);
|
|
|
|
# Navigate to the Update screen
|
|
select_cockpit_update();
|
|
|
|
# FIXME Workaround for RHBZ #1765685 - remove after F34 EOL (seems
|
|
# to be fixed in F35 and F36)
|
|
sleep 30;
|
|
|
|
# Switch on automatic updates
|
|
assert_and_click 'cockpit_updates_auto', '', 120;
|
|
assert_and_click 'cockpit_updates_dnf_install', '', 120;
|
|
# from 234 onwards, we get a config screen here: "no updates",
|
|
# "security updates only", "all updates"
|
|
assert_and_click 'cockpit_updates_auto_all';
|
|
assert_and_click 'cockpit_save_changes';
|
|
|
|
# Check the default automatic settings Everyday at 6 o'clock.
|
|
assert_screen 'autoupdate_planned_day';
|
|
assert_screen 'autoupdate_planned_time';
|
|
|
|
# Quit Cockpit
|
|
quit_firefox;
|
|
|
|
# Check that the dnf-automatic service has started
|
|
assert_script_run "systemctl is-active dnf-automatic-install.timer";
|
|
|
|
# Check that it is scheduled correctly
|
|
validate_script_output "systemctl show dnf-automatic-install.timer | grep TimersCalendar", sub { $_ =~ "06:00:00" };
|
|
}
|
|
|
|
sub test_flags {
|
|
return {always_rolllback => 1};
|
|
}
|
|
|
|
1;
|
|
|
|
# vim: set sw=4 et:
|