os-autoinst-distri-rocky-mi.../tests/upgrade_run.pm

use base "installedtest";
use strict;
use testapi;
use utils;

sub run {
    my $self = shift;
    my $release = lc(get_var("VERSION"));
    # disable screen blanking (download can take a long time)
    script_run "setterm -blank 0";

    # use compose repo
    repo_setup();
    my $params = "-y --releasever=${release}";
    if ($release eq "rawhide") {
        $params .= " --nogpgcheck";
    }
    assert_script_run "dnf ${params} system-upgrade download", 6000;

    upload_logs "/var/log/dnf.log";
    upload_logs "/var/log/dnf.rpm.log";

    script_run "dnf system-upgrade reboot", 0;
    # fail immediately if we see a DNF error message
    die "DNF reported failure" if (check_screen "upgrade_fail", 15);
    if (get_var("ENCRYPT_PASSWORD")) {
        boot_decrypt(60);
    }
    # in encrypted case we need to wait a bit so postinstall test
    # doesn't bogus match on the encryption prompt we just completed
    # before it disappears from view
    if (get_var("ENCRYPT_PASSWORD")) {
        sleep 5;
    }
}


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:
add comments and documentation Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D481 2015-08-05 06:23:59 +00:00			`use base "installedtest";`
Add fedup_minimal test Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D358 2015-05-13 11:00:46 +00:00			`use strict;`
			`use testapi;`
Move all remaining utility functions into exporter modules Summary: This adds a couple of new exporter modules, renames main_common to utils (this is a better name: openSUSE's main_common is functions used in main.pm, utils is what they call their module full of miscellaneous commonly-used functions), and moves a bunch of utility functions that were previously needlessly implemented as instance methods in base classes into the exporter modules. That means we can get rid of all the annoying $self-> syntax for calling them. We get rid of `fedorabase` entirely, as it's no longer useful for anything. Other base classes keep the 'standard' methods (like `post_fail_hook`) and methods which actually need to be methods (like `root_console`, whose behaviour is different in anacondatest and installedtest). Test Plan: Do a full test suite run and check everything lines up. There should be no functional differences from before at all, this is just a re-org. Reviewers: jskladan, garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Reviewed By: garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Subscribers: tflink Differential Revision: https://phab.qa.fedoraproject.org/D1080 2017-01-18 07:15:44 +00:00			`use utils;`
Add fedup_minimal test Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D358 2015-05-13 11:00:46 +00:00
			`sub run {`
remember to shift when we use $self... 2016-01-28 05:40:07 +00:00			`my $self = shift;`
fix upgrade test (broken by recent nogpgcheck commit) in the recent commit to always use nogpgcheck I inadvertently broke the upgrade tests, by dropping the `--releasever` from the `dnf system-upgrade download` command. So fix that. 2016-08-12 17:08:46 +00:00			`my $release = lc(get_var("VERSION"));`
upgrade: disable screen blanking before long-running commands Summary: Updating the stable release prior to doing the update can take a long time if the image hasn't been updated for a while, and the upgrade download process itself can take a long time. If the screen blanks out in either case, either the following needle match may fail (if we're waiting for a needle) or 'still screen' may be detected early (if we're waiting for a still screen), so let's disable screen blanking to avoid it. Test Plan: Run the upgrade tests and see if they work. Reviewers: garretraziel, jskladan Reviewed By: jskladan Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D628 2015-10-27 01:02:22 +00:00			`# disable screen blanking (download can take a long time)`
use validate_script_output instead of typing and needles matching Use validate_script_output and regex matching instead of type_string and needles. Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D637 2015-11-04 13:38:36 +00:00			`script_run "setterm -blank 0";`
upgrade: disable screen blanking before long-running commands Summary: Updating the stable release prior to doing the update can take a long time if the image hasn't been updated for a while, and the upgrade download process itself can take a long time. If the screen blanks out in either case, either the following needle match may fail (if we're waiting for a needle) or 'still screen' may be detected early (if we're waiting for a still screen), so let's disable screen blanking to avoid it. Test Plan: Run the upgrade tests and see if they work. Reviewers: garretraziel, jskladan Reviewed By: jskladan Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D628 2015-10-27 01:02:22 +00:00
use compose repository (not master repo) for most tests Summary: we have a long-standing problem with all the tests that hit the repositories. The tests are triggered as soon as a compose completes. At this point in time, the compose is not synced to the mirrors, where the default 'fedora' repo definition looks; the sync happens after the compose completes, and there is also a metadata sync step that must happen after that before any operation that uses the 'fedora' repository definition will actually use the packages from the new compose. Thus all net install tests and tests that installed packages have been effectively testing the previous compose, not the current one. We have some thoughts about how to fix this 'properly' (such that the openQA tests wouldn't have to do anything special, but their 'fedora' repository would somehow reflect the compose under test), but none of them is in place right now or likely to happen in the short term, so in the mean time this should deal with most of the issues. With this change, everything but the default_install tests for the netinst images should use the compose-under-test's Everything tree instead of the 'fedora' repository, and thus should install and test the correct packages. This relies on a corresponding change to openqa_fedora_tools to set the LOCATION openQA setting (which is simply the base location of the compose under test). Test Plan: Do a full test run, check (as far as you can) tests run sensibly and use appropriate repositories. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D989 2016-09-01 15:22:59 +00:00			`# use compose repo`
Move all remaining utility functions into exporter modules Summary: This adds a couple of new exporter modules, renames main_common to utils (this is a better name: openSUSE's main_common is functions used in main.pm, utils is what they call their module full of miscellaneous commonly-used functions), and moves a bunch of utility functions that were previously needlessly implemented as instance methods in base classes into the exporter modules. That means we can get rid of all the annoying $self-> syntax for calling them. We get rid of `fedorabase` entirely, as it's no longer useful for anything. Other base classes keep the 'standard' methods (like `post_fail_hook`) and methods which actually need to be methods (like `root_console`, whose behaviour is different in anacondatest and installedtest). Test Plan: Do a full test suite run and check everything lines up. There should be no functional differences from before at all, this is just a re-org. Reviewers: jskladan, garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Reviewed By: garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Subscribers: tflink Differential Revision: https://phab.qa.fedoraproject.org/D1080 2017-01-18 07:15:44 +00:00			`repo_setup();`
use compose repository (not master repo) for most tests Summary: we have a long-standing problem with all the tests that hit the repositories. The tests are triggered as soon as a compose completes. At this point in time, the compose is not synced to the mirrors, where the default 'fedora' repo definition looks; the sync happens after the compose completes, and there is also a metadata sync step that must happen after that before any operation that uses the 'fedora' repository definition will actually use the packages from the new compose. Thus all net install tests and tests that installed packages have been effectively testing the previous compose, not the current one. We have some thoughts about how to fix this 'properly' (such that the openQA tests wouldn't have to do anything special, but their 'fedora' repository would somehow reflect the compose under test), but none of them is in place right now or likely to happen in the short term, so in the mean time this should deal with most of the issues. With this change, everything but the default_install tests for the netinst images should use the compose-under-test's Everything tree instead of the 'fedora' repository, and thus should install and test the correct packages. This relies on a corresponding change to openqa_fedora_tools to set the LOCATION openQA setting (which is simply the base location of the compose under test). Test Plan: Do a full test run, check (as far as you can) tests run sensibly and use appropriate repositories. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D989 2016-09-01 15:22:59 +00:00			`my $params = "-y --releasever=${release}";`
			`if ($release eq "rawhide") {`
			`$params .= " --nogpgcheck";`
			`}`
			`assert_script_run "dnf ${params} system-upgrade download", 6000;`
Add fedup_minimal test Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D358 2015-05-13 11:00:46 +00:00
convert upgrade tests to dnf-plugin-system-upgrade Summary: This is a first cut which more or less works for now. Issues: 1) We're not really testing the BUILD, here. All the test does is try and upgrade to the specified VERSION - so it'll be using the latest 'stable' for the given VERSION at the time the test runs. This isn't really that terrible, but especially for TC/RC validation, we might want to make things a bit more elaborate and set up the repo for the actual BUILD (and disable the main repos). 2) We'd actually need --nogpgcheck for non-Rawhide, at one specific point in the release cycle - after Branching but before Bodhi activation (which is when we can be sure all packages are signed). This won't matter until 24 branches, and maybe releng will have it fixed by then...if not, I'll tweak it. 3) We don't really test that the upgrade actually happened for desktop, at the moment - the only thing in the old test that really checked that was where we checked for the fedup boot menu entry, but that has no analog in dnf. What we should probably do is check that GUI login works, then switch to a console and check /etc/fedora-release just as the minimal test does. Test Plan: Run the tests. Note that creating the desktop disk image doesn't work ATM, so I can't verify the desktop test works, but the minimal one seems to (with D565). There'll be a matching diff for openqa_fedora_tools to update the test case names there. Reviewers: jskladan, garretraziel Reviewed By: jskladan, garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D567 2015-09-10 21:49:13 +00:00			`upload_logs "/var/log/dnf.log";`
			`upload_logs "/var/log/dnf.rpm.log";`
Add fedup_minimal test Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D358 2015-05-13 11:00:46 +00:00
don't wait for `dnf system-upgrade reboot` command to return because it won't. 2016-10-22 00:42:28 +00:00			`script_run "dnf system-upgrade reboot", 0;`
add a comment explaining a perl-ism this was requested by jskladan in D650, I forgot to add it before committing. 2015-12-07 23:46:20 +00:00			`# fail immediately if we see a DNF error message`
add encrypted workstation upgrade tests (current and previous) Summary: This requires us to handle decryption each time we reboot in the upgrade process, so factor that little block out into the base class so we don't have to keep pasting it. It's also a bit tricky to integrate into the 'catch a boot loop' code we have to deal with #1349721, but I think this should work. There is a matching openqa_fedora_tools diff to generate the disk image. Test Plan: Run the tests, check that they work, run the other upgrade and encrypted install tests and check they still work properly too. Reviewers: garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D922 2016-07-08 15:56:57 +00:00			`die "DNF reported failure" if (check_screen "upgrade_fail", 15);`
			`if (get_var("ENCRYPT_PASSWORD")) {`
Call `boot_decrypt` properly (function not method) Noticed in e.g. https://openqa.fedoraproject.org/tests/58798 we're doing this wrong, `boot_decrypt` was moved into utils as a function, but we were still calling it as a method... 2017-03-02 22:32:17 +00:00			`boot_decrypt(60);`
add encrypted workstation upgrade tests (current and previous) Summary: This requires us to handle decryption each time we reboot in the upgrade process, so factor that little block out into the base class so we don't have to keep pasting it. It's also a bit tricky to integrate into the 'catch a boot loop' code we have to deal with #1349721, but I think this should work. There is a matching openqa_fedora_tools diff to generate the disk image. Test Plan: Run the tests, check that they work, run the other upgrade and encrypted install tests and check they still work properly too. Reviewers: garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D922 2016-07-08 15:56:57 +00:00			`}`
			`# in encrypted case we need to wait a bit so postinstall test`
			`# doesn't bogus match on the encryption prompt we just completed`
			`# before it disappears from view`
			`if (get_var("ENCRYPT_PASSWORD")) {`
			`sleep 5;`
			`}`
Add fedup_minimal test Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D358 2015-05-13 11:00:46 +00:00			`}`


			`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:`