testing/os-autoinst-distri-rocky
11
0
Fork 0
mirror of https://github.com/rocky-linux/os-autoinst-distri-rocky.git synced 2024-11-05 13:31:24 +00:00
Code Issues Packages Projects Releases Wiki Activity
b117d16133
os-autoinst-distri-rocky/tests/_installer_build.pm

40 lines
1.4 KiB
Perl
Raw Normal View History

Add update tests to build and test a netinst image This adds a test which builds a netinst image potentially with the package(s) from the update, and uploads that image. It also adds a test which runs a default install using that image. This is intended to check whether the update breaks the creation or use of install images; particularly this will let us test anaconda etc. updates. We also update the minimal disk image name, as we have to make it bigger to accommodate this test, and making it bigger changes its name - the actual change to the disk image itself is in createhdds. We also have to redo a bunch of installer needles for F28 fonts, after I removed them a month or so back... Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-08-31 20:34:12 +00:00
use base "installedtest";
use strict;
use testapi;
use utils;
sub run {
my $self = shift;
my $version = get_var("VERSION");
Revise release variable handling, prerelease checks, os-release I started out trying to fix os-release for the recent change to add "Prerelease" tags to the VERSION and PRETTY_NAME fields, then things spiralled. It got me thinking about the awkward DEVELOPMENT variable we use, so I decided to get rid of it and refactor the few things that use it. I refactored the anaconda prerelease tag check, and wrote a new giant comment that gives details about exactly how anaconda decides whether to show those tags, to give context to our choices about when to expect them. This check now uses a new LABEL variable the scheduler now sets. I also wound up creating new UP1REL and UP2REL vars to define the 'source' release for upgrade tests, separate from CURRREL and PREVREL, which are now never lies - they really are the current stable and previous stable release, even for update upgrade tests. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-05-07 22:42:08 +00:00
my $currrel = get_var("CURRREL");
Handle running update tests on Koji tasks We quite often want to run the update tests on a Koji task (not a Bodhi update) for some reason - usually to test a potential fix for an issue, or at a maintainer's request to test a change before it is merged upstream and officially sent out as an update. Up till now I've always hacked up utils.pm on the staging server by hand to do this, which is horrible. Together with a commit to fedora_openqa, this should allow us to do it in a nice, sane way via the CLI. It's mostly just tweaking the "updates" repo setup in utils.pm as you'd expect, but there's a bit of subtlety to it because of the installer tests that use %ADVISORY% as a variable substitution in the disk image name; you can't do something like `%ADVISORY or KOJITASK%`, sadly, so I had to have almost-redundant variables ADVISORY, KOJITASK and ADVISORY_OR_TASK (we could kinda just live with ADVISORY_OR_TASK except I didn't want to drop ADVISORY as it's an unnecessary change from previous behavior). Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-01-29 09:06:16 +00:00
my $advortask = get_var("ADVISORY_OR_TASK");
Add update tests to build and test a netinst image This adds a test which builds a netinst image potentially with the package(s) from the update, and uploads that image. It also adds a test which runs a default install using that image. This is intended to check whether the update breaks the creation or use of install images; particularly this will let us test anaconda etc. updates. We also update the minimal disk image name, as we have to make it bigger to accommodate this test, and making it bigger changes its name - the actual change to the disk image itself is in createhdds. We also have to redo a bunch of installer needles for F28 fonts, after I removed them a month or so back... Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-08-31 20:34:12 +00:00
my $arch = get_var("ARCH");
Drop a couple of obsolete workarounds from _installer_build F28-era stuff. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-12-20 17:19:13 +00:00
assert_script_run "dnf -y install lorax", 90;
Add update tests to build and test a netinst image This adds a test which builds a netinst image potentially with the package(s) from the update, and uploads that image. It also adds a test which runs a default install using that image. This is intended to check whether the update breaks the creation or use of install images; particularly this will let us test anaconda etc. updates. We also update the minimal disk image name, as we have to make it bigger to accommodate this test, and making it bigger changes its name - the actual change to the disk image itself is in createhdds. We also have to redo a bunch of installer needles for F28 fonts, after I removed them a month or so back... Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-08-31 20:34:12 +00:00
# this 'temporary file cleanup' thing can actually wipe bits of
# the lorax install root while lorax is still running...
assert_script_run "systemctl stop systemd-tmpfiles-clean.timer";
assert_script_run "mkdir -p /root/imgbuild";
assert_script_run "pushd /root/imgbuild";
assert_script_run "setenforce Permissive";
my $cmd = "lorax -p Fedora -v ${version} -r ${version} --repo=/etc/yum.repos.d/fedora.repo";
Bump installer image rootfs size on Fedora 30 update tests https://bodhi.fedoraproject.org/updates/FEDORA-2020-1070052d10#comment-1284223 It seems the rootfs on the Fedora 30 installer images we build at present has gotten very big, so big that an update which contains some very slightly larger firmware packages causes the rootfs to be completely full (though lorax doesn't fail) and the image doesn't boot. I don't yet know when or why the rootfs got that big, but it's not really a bug in this update, so for now let's just tell lorax to use a bigger rootfs so the tests pass for this and any similar future updates, until I can maybe find time to pinpoint the culprit more precisely. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-03-18 03:00:52 +00:00
# rootfs in F30 installer images seems to have got very big at
# some point, let's work around that for now:
# https://bodhi.fedoraproject.org/updates/FEDORA-2020-1070052d10#comment-1284223
$cmd .= " --rootfs-size 3" if ($version eq 30);
Revise release variable handling, prerelease checks, os-release I started out trying to fix os-release for the recent change to add "Prerelease" tags to the VERSION and PRETTY_NAME fields, then things spiralled. It got me thinking about the awkward DEVELOPMENT variable we use, so I decided to get rid of it and refactor the few things that use it. I refactored the anaconda prerelease tag check, and wrote a new giant comment that gives details about exactly how anaconda decides whether to show those tags, to give context to our choices about when to expect them. This check now uses a new LABEL variable the scheduler now sets. I also wound up creating new UP1REL and UP2REL vars to define the 'source' release for upgrade tests, separate from CURRREL and PREVREL, which are now never lies - they really are the current stable and previous stable release, even for update upgrade tests. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-05-07 22:42:08 +00:00
unless ($version > $currrel) {
Add update tests to build and test a netinst image This adds a test which builds a netinst image potentially with the package(s) from the update, and uploads that image. It also adds a test which runs a default install using that image. This is intended to check whether the update breaks the creation or use of install images; particularly this will let us test anaconda etc. updates. We also update the minimal disk image name, as we have to make it bigger to accommodate this test, and making it bigger changes its name - the actual change to the disk image itself is in createhdds. We also have to redo a bunch of installer needles for F28 fonts, after I removed them a month or so back... Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-08-31 20:34:12 +00:00
$cmd .= " --isfinal --repo=/etc/yum.repos.d/fedora-updates.repo";
}
$cmd .= " --repo=/etc/yum.repos.d/advisory.repo ./results";
assert_script_run $cmd, 1500;
Handle running update tests on Koji tasks We quite often want to run the update tests on a Koji task (not a Bodhi update) for some reason - usually to test a potential fix for an issue, or at a maintainer's request to test a change before it is merged upstream and officially sent out as an update. Up till now I've always hacked up utils.pm on the staging server by hand to do this, which is horrible. Together with a commit to fedora_openqa, this should allow us to do it in a nice, sane way via the CLI. It's mostly just tweaking the "updates" repo setup in utils.pm as you'd expect, but there's a bit of subtlety to it because of the installer tests that use %ADVISORY% as a variable substitution in the disk image name; you can't do something like `%ADVISORY or KOJITASK%`, sadly, so I had to have almost-redundant variables ADVISORY, KOJITASK and ADVISORY_OR_TASK (we could kinda just live with ADVISORY_OR_TASK except I didn't want to drop ADVISORY as it's an unnecessary change from previous behavior). Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-01-29 09:06:16 +00:00
assert_script_run "mv results/images/boot.iso ./${advortask}-netinst-${arch}.iso";
upload_asset "./${advortask}-netinst-x86_64.iso";
Add update tests to build and test a netinst image This adds a test which builds a netinst image potentially with the package(s) from the update, and uploads that image. It also adds a test which runs a default install using that image. This is intended to check whether the update breaks the creation or use of install images; particularly this will let us test anaconda etc. updates. We also update the minimal disk image name, as we have to make it bigger to accommodate this test, and making it bigger changes its name - the actual change to the disk image itself is in createhdds. We also have to redo a bunch of installer needles for F28 fonts, after I removed them a month or so back... Signed-off-by: Adam Williamson <awilliam@redhat.com>
2018-08-31 20:34:12 +00:00
}
sub test_flags {
return { fatal => 1 };
}
1;
# vim: set sw=4 et:
Reference in New Issue Copy Permalink