mirror of
https://github.com/rocky-linux/os-autoinst-distri-rocky.git
synced 2024-11-09 23:11:24 +00:00
3e435182dd
Summary: these together test QA:Testcase_kickstart_firewall from the Server matrix. I'll have to come up with some kinda way to handle reporting that, might be tricky. Couple of tweaks to overall test flow: tests can now specify a POSTINSTALL variable which will load a post-install test following a naming convention, and tests can specify USER_LOGIN as 'false' to disable the 'log in as a user' step entirely. We could easily adjust the kickstarts to create a user so the test could log in as one, but it seems like an unnecessary step and I liked the idea of allowing the user login to be skipped. Test Plan: Schedule 'universal' tests, check the new tests run and pass or fail as they should, check no other test is broken by the logic flow changes. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D792
30 lines
900 B
Perl
30 lines
900 B
Perl
use base "installedtest";
|
|
use strict;
|
|
use testapi;
|
|
|
|
sub run {
|
|
my $self=shift;
|
|
if (not( check_screen "root_console", 0)) {
|
|
$self->root_console(tty=>3);
|
|
}
|
|
# this only succeeds if the firewall is running
|
|
assert_script_run 'firewall-cmd --state';
|
|
# these succeed if the specified service/port is allowed
|
|
assert_script_run 'firewall-cmd --query-service ftp';
|
|
assert_script_run 'firewall-cmd --query-port imap/tcp';
|
|
assert_script_run 'firewall-cmd --query-port 1234/udp';
|
|
assert_script_run 'firewall-cmd --query-port 47/tcp';
|
|
}
|
|
|
|
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:
|