mirror of
https://github.com/rocky-linux/os-autoinst-distri-rocky.git
synced 2024-11-17 10:41:27 +00:00
b7abdf81a9
Summary: Except when running on the pre-upgrade release in the upgrade tests (where GPG check should always be OK). Currently we always need to use --nogpgcheck on Rawhide, and we must also use it on Branched prior to the Bodhi activation point. At present we don't really have any simple way to know when the Bodhi activation point has kicked in. We could assume that it's safe to do GPG checking for 'candidate' (not nightly) composes, but even that isn't 100% safe and isn't really the *right* thing to do. So I think for now it's best to just always use --nogpgcheck , until we come up with a decent way to check for Bodhi enablement, or releng figures things out so we can rely on packages being signed in Rawhide and in Branched before Bodhi enablement. Test Plan: Check the tests all still run, make sure I didn't miss any dnf calls. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D964
32 lines
1.1 KiB
Perl
32 lines
1.1 KiB
Perl
use base "installedtest";
|
|
use strict;
|
|
use testapi;
|
|
|
|
sub run {
|
|
my $self=shift;
|
|
# check cockpit appears to be enabled and running and firewall is setup
|
|
assert_script_run 'systemctl is-enabled cockpit.socket';
|
|
assert_script_run 'systemctl is-active cockpit.socket';
|
|
assert_script_run 'firewall-cmd --query-service cockpit';
|
|
# we don't want updates-testing for validation purposes
|
|
assert_script_run 'dnf config-manager --set-disabled updates-testing';
|
|
# install a desktop and firefox so we can actually try it
|
|
assert_script_run 'dnf -y --nogpgcheck groupinstall "base-x"', 300;
|
|
assert_script_run 'dnf -y --nogpgcheck install firefox', 120;
|
|
$self->start_cockpit(0);
|
|
# quit firefox (return to console)
|
|
send_key "ctrl-q";
|
|
}
|
|
|
|
sub test_flags {
|
|
# without anything - rollback to 'lastgood' snapshot if failed
|
|
# 'fatal' - whole test suite is in danger if this fails
|
|
# 'milestone' - after this test succeeds, update 'lastgood'
|
|
# 'important' - if this fails, set the overall state to 'fail'
|
|
return { fatal => 1 };
|
|
}
|
|
|
|
1;
|
|
|
|
# vim: set sw=4 et:
|