srbala/os-autoinst-distri-fedora
1
0
Fork 0
mirror of https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git synced 2024-11-13 18:24:24 +00:00
Code Issues Releases Activity
635ff8941e
os-autoinst-distri-fedora/tests/autocloud.pm

89 lines
4.4 KiB
Perl
Raw Normal View History

Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
use base "installedtest";
use strict;
use testapi;
use utils;
sub _soft_fail_run {
my ($test, $sudo) = @_;
$sudo //= 1;
my $cmd = "";
$cmd = "sudo " if ($sudo);
$cmd .= "python3 -m unittest";
if (script_run "$cmd $test -v") {
record_soft_failure "Non-blocking test $test failed";
}
}
sub run {
Add a comment explaining what autocloud.pm does Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 22:58:53 +00:00
# This test is basically a recreation of exactly the test process
# autocloud used to use, via tunir and this tunir config:
# https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/autocloud/backend/files/fedora.txt?id=6e7c1b90593df8371fd34ed9484bd4da119236d3
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
my $self = shift;
# we need to use script_run as regular user
assert_script_run "chmod ugo+w /dev/" . $serialdev;
# let's go to another tty and login as regular user
Run update repo setup steps from a serial console This is a surprisingly large change as we want to go back to the console we were previously on after doing it. To do that we need to know what console we were on, and to know *that*, we need to port everything that currently uses (ctrl-)alt-fX to switch consoles to use select_console instead. This is primarily intended to make running setup_repos.py faster when it has to download a lot of packages (as typing in hundreds of package names is quite slow). But it actually makes the whole thing faster, even when only downloading one or two packages. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-09 18:37:57 +00:00
select_console "tty2-console";
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-07-28 20:32:57 +00:00
console_login(user => "test", password => "weakpassword");
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
assert_script_run "curl -O https://fedorapeople.org/groups/qa/tunirtests.tar.gz";
assert_script_run "tar xvf tunirtests.tar.gz";
autocloud: only run atomic test on canned (==atomic) installs It seems Python 3.12.1 changed unittests' behaviour so that all tests being skipped is now a fail not a pass. That breaks this test because TestAtomic01Status only does anything if this is an atomic system. So, let's just skip that test entirely if we aren't one. As things stand this means the test will never run, because we only test on Cloud_Base which is not atomic. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-12-23 20:04:50 +00:00
if (get_var("CANNED")) {
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.TestAtomic01Status -v";
}
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
_soft_fail_run "tunirtests.nongatingtests.TunirNonGatingtests";
_soft_fail_run "tunirtests.nongatingtests.TunirNonGatingtestBzip2";
_soft_fail_run "tunirtests.nongatingtests.TunirNonGatingtestsCpio";
_soft_fail_run "tunirtests.nongatingtests.TunirNonGatingtestDiffutills";
_soft_fail_run "tunirtests.nongatingtests.TunirNonGatingtestaudit";
_soft_fail_run "tunirtests.selinux.TestSELinux";
_soft_fail_run "tunirtests.sshkeygentest.sshkeygenTest";
_soft_fail_run "tunirtests.testumountroot.TestUmountRoot";
assert_script_run "sudo python3 -m unittest tunirtests.cloudtests.TestBase -v";
assert_script_run "sudo python3 -m unittest tunirtests.cloudtests.TestCloudtmp -v";
assert_script_run "sudo python3 -m unittest tunirtests.cloudtests.Testtmpmount -v";
assert_script_run "sudo python3 -m unittest tunirtests.cloudtests.Testnetname -v";
# this test only works properly as a regular user
_soft_fail_run "tunirtests.cloudtests.TestJournalWritten", 0;
assert_script_run "sudo python3 -m unittest tunirtests.cloudservice.TestServiceStop -v";
assert_script_run "sudo python3 -m unittest tunirtests.cloudservice.TestServiceDisable -v";
type_string "sudo reboot\n";
boot_to_login_screen(timeout => 180);
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-07-28 20:32:57 +00:00
console_login(user => "root", password => "weakpassword");
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
# we need to use script_run as regular user again
assert_script_run "sudo chmod ugo+w /dev/" . $serialdev;
# let's go to another tty and login as regular user again
Run update repo setup steps from a serial console This is a surprisingly large change as we want to go back to the console we were previously on after doing it. To do that we need to know what console we were on, and to know *that*, we need to port everything that currently uses (ctrl-)alt-fX to switch consoles to use select_console instead. This is primarily intended to make running setup_repos.py faster when it has to download a lot of packages (as typing in hundreds of package names is quite slow). But it actually makes the whole thing faster, even when only downloading one or two packages. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-09 18:37:57 +00:00
select_console "tty2-console";
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-07-28 20:32:57 +00:00
console_login(user => "test", password => "weakpassword");
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
_soft_fail_run "tunirtests.testreboot.TestReboot";
assert_script_run "sudo python3 -m unittest tunirtests.cloudservice.TestServiceManipulation -v";
# this test only works properly as a regular user
_soft_fail_run "tunirtests.cloudtests.TestJournalWrittenAfterReboot", 0;
type_string "sudo reboot\n";
boot_to_login_screen(timeout => 180);
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-07-28 20:32:57 +00:00
console_login(user => "root", password => "weakpassword");
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
# we need to use script_run as regular user again
assert_script_run "sudo chmod ugo+w /dev/" . $serialdev;
# let's go to another tty and login as regular user again
Run update repo setup steps from a serial console This is a surprisingly large change as we want to go back to the console we were previously on after doing it. To do that we need to know what console we were on, and to know *that*, we need to port everything that currently uses (ctrl-)alt-fX to switch consoles to use select_console instead. This is primarily intended to make running setup_repos.py faster when it has to download a lot of packages (as typing in hundreds of package names is quite slow). But it actually makes the whole thing faster, even when only downloading one or two packages. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-09 18:37:57 +00:00
select_console "tty2-console";
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-07-28 20:32:57 +00:00
console_login(user => "test", password => "weakpassword");
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
assert_script_run "sudo python3 -m unittest tunirtests.cloudservice.TestServiceAfter -v";
autocloud: blocking off more atomic tests on non-atomic images Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-02 22:06:35 +00:00
if (get_var("CANNED")) {
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.TestDockerInstalled -v";
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.TestDockerStorageSetup -v";
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.TestAtomicFirstBootRun -v";
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.TestAtomicCommand -v";
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.TestAtomicDockerImage -v";
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.TestRootMount -v";
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.Testreadonlymount -v";
assert_script_run "sudo python3 -m unittest tunirtests.atomictests.TestDockerDaemon -v";
}
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
}
sub test_flags {
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-07-28 20:32:57 +00:00
return {fatal => 1};
Run autocloud tests on Cloud_Base qcow2 images autocloud is dying soon. So, we want to run the tests in openQA instead. This adds a test module called 'autocloud' and a test suite called 'cloud_autocloud' which basically replicate what autocloud does (download a tarball full of tests and run each one), and the necessary template bits to run it on Cloud_Base qcow2 images. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-11-21 20:10:36 +00:00
}
1;
# vim: set sw=4 et:
Reference in New Issue Copy Permalink