srbala/os-autoinst-distri-fedora
1
0
Fork 0
mirror of https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git synced 2024-09-21 22:47:22 +00:00
Code Issues Releases Activity
e0fb862233
os-autoinst-distri-fedora/tests/_installer_build.pm

57 lines
2.5 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");
Adjust live and installer build for Rawhide support We need to tweak various things when building live and installer images for Rawhide. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-04-26 17:41:23 +00:00
my $rawrel = get_var("RAWREL");
my $repo = $version eq $rawrel ? "fedora-rawhide.repo" : "fedora.repo";
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");
Run update package version check on installer environments As discussed in https://pagure.io/releng/failed-composes/issue/6538 we noticed a gap in openQA coverage here. We don't check the versions of packages lorax installs to the installer environment, and those packages do not make it to the installed system, so if there's a dep issue that prevents a package in the update from being included in the installer environment, but the same dep issue isn't caught on any other path, we miss the problem. This wires the updvercheck.py script into the _installer_build and _ostree_build tests to catch this kind of problem, and makes it capable of parsing pylorax.log files into its preferred format to enable that. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-02 20:27:52 +00:00
# python3-dnf is for updvercheck.py
my $packages = "python3-dnf lorax";
installer_build: install hfsplus-tools on ppc64le We need this on ppc64le. Never tried running this test on it before. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-09-06 23:43:36 +00:00
$packages .= " hfsplus-tools" if ($arch eq "ppc64le");
assert_script_run "dnf -y install $packages", 120;
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";
Always use rootfs size of 3GiB in installer build test This is how our Pungi config has been set up since F32, so we should match it here to be accurate. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2021-02-09 19:19:43 +00:00
# Fedora pungi config always sets rootfs size to 3GiB since F32
Add `--squashfs-only` to lorax args We started using this in real composes a year or two back, so openQA should do the same. It drops the nesting of an ext4 fs image inside a squashfs image, just using a single squashfs image instead. This results in smaller images - missing this is why the images built by openQA were coming out larger than the real ones. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-12-07 22:03:19 +00:00
my $cmd = "lorax -p Fedora -v ${version} -r ${version} --repo=/etc/yum.repos.d/${repo} --rootfs-size 3 --squashfs-only";
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";
}
update testing: use a concurrent script to download packages This uses a Python script which implements concurrent downloads (via asyncio) to download workaround and update packages and configure the repos. This should speed up the process for large multi-package updates. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-06 00:22:01 +00:00
$cmd .= " --repo=/etc/yum.repos.d/workarounds.repo" if (get_workarounds);
Use buildroot repo for Rawhide image builds also We recently started using the buildroot repo for Rawhide update tests, but weren't including it in the image build tests. This should include it in all the image build tests. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-12-10 17:25:29 +00:00
$cmd .= " --repo=/etc/yum.repos.d/koji-rawhide.repo" if ($version eq $rawrel);
Enable testing of COPRs, fix some issues, enable package checks This works more or less like testing side tags. We also fix up some flow problems with this path (that also affect the side tag case), and enable the package checks on this path - it's not too hard really, we just need to write the updatepkgs file when we set up the repo, which we can do with dnf repoquery. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-04-30 20:45:32 +00:00
$cmd .= " --repo=/etc/yum.repos.d/advisory.repo" unless (get_var("TAG") || get_var("COPR"));
$cmd .= " --repo=/etc/yum.repos.d/openqa-testtag.repo" if (get_var("TAG") || get_var("COPR"));
Use buildroot repo for Rawhide image builds also We recently started using the buildroot repo for Rawhide update tests, but weren't including it in the image build tests. This should include it in all the image build tests. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-12-10 17:25:29 +00:00
$cmd .= " ./results";
_installer_build: give lorax a bit longer to run It timed out on some Rawhide update tests. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-05-06 21:05:41 +00:00
assert_script_run $cmd, 2400;
Run update package version check on installer environments As discussed in https://pagure.io/releng/failed-composes/issue/6538 we noticed a gap in openQA coverage here. We don't check the versions of packages lorax installs to the installer environment, and those packages do not make it to the installed system, so if there's a dep issue that prevents a package in the update from being included in the installer environment, but the same dep issue isn't caught on any other path, we miss the problem. This wires the updvercheck.py script into the _installer_build and _ostree_build tests to catch this kind of problem, and makes it capable of parsing pylorax.log files into its preferred format to enable that. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-02 20:27:52 +00:00
# do a package version check on the packages installed to the
# installer environment - see
# https://pagure.io/releng/failed-composes/issue/6538#comment-917347
assert_script_run 'curl --retry-delay 10 --max-time 30 --retry 5 -o updvercheck.py https://pagure.io/fedora-qa/os-autoinst-distri-fedora/raw/lorax-check-packages/f/updvercheck.py', timeout => 180;
my $advisory = get_var("ADVISORY");
my $cmd = 'python3 ./updvercheck.py /mnt/updatepkgs.txt pylorax.log';
$cmd .= " $advisory" if ($advisory);
my $ret = script_run $cmd;
acnp_handle_output($ret, 0, 1);
Upload pylorax.log when done building installer image Handy to have it around to check for oddities. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-09-15 21:54:44 +00:00
# good to have the log around for checks
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
upload_logs "pylorax.log", failok => 1;
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";
installer_build: fix image upload on non-x86_64 Let's not hardcode the arch in the upload_asset call! Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-09-07 00:24:35 +00:00
upload_asset "./${advortask}-netinst-${arch}.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 {
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};
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
}
1;
# vim: set sw=4 et:
Reference in New Issue Copy Permalink