2019-01-29 14:56:01 +00:00
use base "installedtest" ;
use strict ;
use testapi ;
use utils ;
sub run {
my $ self = shift ;
my $ version = get_var ( "VERSION" ) ;
2022-04-26 17:41:23 +00:00
my $ rawrel = get_var ( "RAWREL" ) ;
my $ branch ;
my $ repoks ;
my $ releasever ;
2023-08-09 21:27:38 +00:00
my $ mockver ;
2022-04-26 17:41:23 +00:00
if ( $ version eq $ rawrel ) {
$ branch = "main" ;
$ repoks = "fedora-repo-rawhide.ks" ;
$ releasever = "Rawhide" ;
2023-08-09 21:26:02 +00:00
$ mockver = "rawhide" ;
2022-04-26 17:41:23 +00:00
}
else {
$ branch = "f${version}" ;
$ repoks = "fedora-repo-not-rawhide.ks" ;
$ releasever = $ version ;
2023-08-09 21:26:02 +00:00
$ mockver = $ version ;
2022-04-26 17:41:23 +00:00
}
2019-01-29 14:56:01 +00:00
my $ advortask = get_var ( "ADVISORY_OR_TASK" ) ;
my $ arch = get_var ( "ARCH" ) ;
my $ subv = get_var ( "SUBVARIANT" ) ;
my $ lcsubv = lc ( $ subv ) ;
Revert to having tests, not the scheduler, download packages (#108)
This effectively reverts 97618193 - but had to be done manually
and adjusted to maintain support for testing side tags and for
testing multiple tasks, since those features were added since
the update ISO change.
The 'scheduler injects ISOs of packages into the tests' approach
was intended to speed things up, especially for large updates,
and it did, but it had a few drawbacks. It means restarting
older tests from the web UI doesn't work as the ISOs get garbage
collected (you have to re-schedule in this case). And it has the
rather large problem that you can now only schedule tests from
the openQA server (or at least a machine with the openQA asset
share mounted), because the package download and ISO creation
just happen wherever the scheduler is running and assume that
the openQA asset share that will be used by the tests is at
/var/lib/openqa/share in that filesystem.
That's too big of a drawback to continue with this approach, IMO,
so this reverts back to the old way of doing things, with a bit
of refactoring to clean up the flow a little, and with support
for testing side tags and multiple tasks maintained.
As a follow-up I'm going to see if I can replace
_download_packages with a much more efficient downloader script
to mitigate the time this process takes on each test, especially
for large updates.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-05 19:41:50 +00:00
my $ tag = get_var ( "TAG" ) ;
2020-05-06 04:12:12 +00:00
if ( get_var ( "NUMDISKS" ) > 2 ) {
Revert to having tests, not the scheduler, download packages (#108)
This effectively reverts 97618193 - but had to be done manually
and adjusted to maintain support for testing side tags and for
testing multiple tasks, since those features were added since
the update ISO change.
The 'scheduler injects ISOs of packages into the tests' approach
was intended to speed things up, especially for large updates,
and it did, but it had a few drawbacks. It means restarting
older tests from the web UI doesn't work as the ISOs get garbage
collected (you have to re-schedule in this case). And it has the
rather large problem that you can now only schedule tests from
the openQA server (or at least a machine with the openQA asset
share mounted), because the package download and ISO creation
just happen wherever the scheduler is running and assume that
the openQA asset share that will be used by the tests is at
/var/lib/openqa/share in that filesystem.
That's too big of a drawback to continue with this approach, IMO,
so this reverts back to the old way of doing things, with a bit
of refactoring to clean up the flow a little, and with support
for testing side tags and multiple tasks maintained.
As a follow-up I'm going to see if I can replace
_download_packages with a much more efficient downloader script
to mitigate the time this process takes on each test, especially
for large updates.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-05 19:41:50 +00:00
# put /var/lib/mock on the third disk, so we don't run out of
# space on the main disk. The second disk will have already
# been claimed for the update repo.
2020-05-06 04:12:12 +00:00
assert_script_run "echo 'type=83' | sfdisk /dev/vdc" ;
assert_script_run "mkfs.ext4 /dev/vdc1" ;
assert_script_run "echo '/dev/vdc1 /var/lib/mock ext4 defaults 1 2' >> /etc/fstab" ;
assert_script_run "mkdir -p /var/lib/mock" ;
assert_script_run "mount /var/lib/mock" ;
}
2019-01-29 14:56:01 +00:00
# install the tools we need
2023-09-19 19:47:35 +00:00
assert_script_run "dnf -y install mock git pykickstart tar" , 300 ;
2019-09-23 23:00:08 +00:00
# base mock config on original
2023-08-09 21:26:02 +00:00
assert_script_run "echo \"include('/etc/mock/fedora-${mockver}-${arch}.cfg')\" > /etc/mock/openqa.cfg" ;
2020-09-15 21:44:34 +00:00
# make the side and workarounds repos and the serial device available inside the mock root
2019-09-23 23:00:08 +00:00
assert_script_run 'echo "config_opts[\'plugin_conf\'][\'bind_mount_enable\'] = True" >> /etc/mock/openqa.cfg' ;
Revert to having tests, not the scheduler, download packages (#108)
This effectively reverts 97618193 - but had to be done manually
and adjusted to maintain support for testing side tags and for
testing multiple tasks, since those features were added since
the update ISO change.
The 'scheduler injects ISOs of packages into the tests' approach
was intended to speed things up, especially for large updates,
and it did, but it had a few drawbacks. It means restarting
older tests from the web UI doesn't work as the ISOs get garbage
collected (you have to re-schedule in this case). And it has the
rather large problem that you can now only schedule tests from
the openQA server (or at least a machine with the openQA asset
share mounted), because the package download and ISO creation
just happen wherever the scheduler is running and assume that
the openQA asset share that will be used by the tests is at
/var/lib/openqa/share in that filesystem.
That's too big of a drawback to continue with this approach, IMO,
so this reverts back to the old way of doing things, with a bit
of refactoring to clean up the flow a little, and with support
for testing side tags and multiple tasks maintained.
As a follow-up I'm going to see if I can replace
_download_packages with a much more efficient downloader script
to mitigate the time this process takes on each test, especially
for large updates.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-05 19:41:50 +00:00
assert_script_run 'echo "config_opts[\'plugin_conf\'][\'bind_mount_opts\'][\'dirs\'].append((\'/mnt/update_repo\', \'/mnt/update_repo\'))" >> /etc/mock/openqa.cfg' unless ( $ tag ) ;
assert_script_run 'echo "config_opts[\'plugin_conf\'][\'bind_mount_opts\'][\'dirs\'].append((\'/mnt/workarounds_repo\', \'/mnt/workarounds_repo\'))" >> /etc/mock/openqa.cfg' ;
2019-01-29 14:56:01 +00:00
assert_script_run 'echo "config_opts[\'plugin_conf\'][\'bind_mount_opts\'][\'dirs\'].append((\'/dev/' . $ serialdev . '\', \'/dev/' . $ serialdev . '\'))" >> /etc/mock/openqa.cfg' ;
2023-07-04 20:13:15 +00:00
my $ repos = 'config_opts[\'dnf.conf\'] += \"\"\"\n' ;
# add the update repo or tag repo to the config
Revert to having tests, not the scheduler, download packages (#108)
This effectively reverts 97618193 - but had to be done manually
and adjusted to maintain support for testing side tags and for
testing multiple tasks, since those features were added since
the update ISO change.
The 'scheduler injects ISOs of packages into the tests' approach
was intended to speed things up, especially for large updates,
and it did, but it had a few drawbacks. It means restarting
older tests from the web UI doesn't work as the ISOs get garbage
collected (you have to re-schedule in this case). And it has the
rather large problem that you can now only schedule tests from
the openQA server (or at least a machine with the openQA asset
share mounted), because the package download and ISO creation
just happen wherever the scheduler is running and assume that
the openQA asset share that will be used by the tests is at
/var/lib/openqa/share in that filesystem.
That's too big of a drawback to continue with this approach, IMO,
so this reverts back to the old way of doing things, with a bit
of refactoring to clean up the flow a little, and with support
for testing side tags and multiple tasks maintained.
As a follow-up I'm going to see if I can replace
_download_packages with a much more efficient downloader script
to mitigate the time this process takes on each test, especially
for large updates.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-05 19:41:50 +00:00
$ repos . = '[advisory]\nname=Advisory repo\nbaseurl=file:///mnt/update_repo\nenabled=1\nmetadata_expire=3600\ngpgcheck=0\n' unless ( $ tag ) ;
2023-07-04 20:13:15 +00:00
$ repos . = '[openqa-testtag]\nname=Tag test repo\nbaseurl=https://kojipkgs.fedoraproject.org/repos/' . "${tag}/latest/${arch}" . '\nenabled=1\nmetadata_expire=3600\ngpgcheck=0\n' if ( $ tag ) ;
Revert to having tests, not the scheduler, download packages (#108)
This effectively reverts 97618193 - but had to be done manually
and adjusted to maintain support for testing side tags and for
testing multiple tasks, since those features were added since
the update ISO change.
The 'scheduler injects ISOs of packages into the tests' approach
was intended to speed things up, especially for large updates,
and it did, but it had a few drawbacks. It means restarting
older tests from the web UI doesn't work as the ISOs get garbage
collected (you have to re-schedule in this case). And it has the
rather large problem that you can now only schedule tests from
the openQA server (or at least a machine with the openQA asset
share mounted), because the package download and ISO creation
just happen wherever the scheduler is running and assume that
the openQA asset share that will be used by the tests is at
/var/lib/openqa/share in that filesystem.
That's too big of a drawback to continue with this approach, IMO,
so this reverts back to the old way of doing things, with a bit
of refactoring to clean up the flow a little, and with support
for testing side tags and multiple tasks maintained.
As a follow-up I'm going to see if I can replace
_download_packages with a much more efficient downloader script
to mitigate the time this process takes on each test, especially
for large updates.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-05 19:41:50 +00:00
# and the workaround repo
$ repos . = '\n[workarounds]\nname=Workarounds repo\nbaseurl=file:///mnt/workarounds_repo\nenabled=1\nmetadata_expire=3600\ngpgcheck=0\n' ;
2022-12-10 17:25:29 +00:00
# also the buildroot repo, for Rawhide
if ( $ version eq $ rawrel ) {
2023-08-02 08:10:55 +00:00
$ repos . = '\n[koji-rawhide]\nname=Buildroot repo\nbaseurl=https://kojipkgs.fedoraproject.org/repos/f' . $ version . '-build/latest/\$basearch/\nenabled=1\nmetadata_expire=3600\ngpgcheck=0\nskip_if_unavailable=1\n' ;
2022-12-10 17:25:29 +00:00
}
$ repos . = '\"\"\"' ;
assert_script_run 'printf "' . $ repos . '" >> /etc/mock/openqa.cfg' ;
2019-08-15 20:36:25 +00:00
# replace metalink with mirrorlist so we don't get slow mirrors
2022-12-10 17:25:29 +00:00
repos_mirrorlist ( "/etc/mock/templates/*.tpl" ) ;
2019-01-29 14:56:01 +00:00
# upload the config so we can check it's OK
upload_logs "/etc/mock/openqa.cfg" ;
# now check out the kickstarts
assert_script_run 'git clone https://pagure.io/fedora-kickstarts.git' ;
assert_script_run 'cd fedora-kickstarts' ;
2022-04-26 17:41:23 +00:00
assert_script_run "git checkout ${branch}" ;
2023-07-04 20:13:15 +00:00
# now add the side repo or tag repo to the appropriate repo ks
Revert to having tests, not the scheduler, download packages (#108)
This effectively reverts 97618193 - but had to be done manually
and adjusted to maintain support for testing side tags and for
testing multiple tasks, since those features were added since
the update ISO change.
The 'scheduler injects ISOs of packages into the tests' approach
was intended to speed things up, especially for large updates,
and it did, but it had a few drawbacks. It means restarting
older tests from the web UI doesn't work as the ISOs get garbage
collected (you have to re-schedule in this case). And it has the
rather large problem that you can now only schedule tests from
the openQA server (or at least a machine with the openQA asset
share mounted), because the package download and ISO creation
just happen wherever the scheduler is running and assume that
the openQA asset share that will be used by the tests is at
/var/lib/openqa/share in that filesystem.
That's too big of a drawback to continue with this approach, IMO,
so this reverts back to the old way of doing things, with a bit
of refactoring to clean up the flow a little, and with support
for testing side tags and multiple tasks maintained.
As a follow-up I'm going to see if I can replace
_download_packages with a much more efficient downloader script
to mitigate the time this process takes on each test, especially
for large updates.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-05 19:41:50 +00:00
assert_script_run 'echo "repo --name=advisory --baseurl=file:///mnt/update_repo" >> ' . $ repoks unless ( $ tag ) ;
2023-07-04 20:13:15 +00:00
assert_script_run 'echo "repo --name=openqa-testtag --baseurl=https://kojipkgs.fedoraproject.org/repos/' . "${tag}/latest/${arch}" . '" >> ' . $ repoks if ( $ tag ) ;
2020-09-15 21:21:07 +00:00
# and the workarounds repo
Revert to having tests, not the scheduler, download packages (#108)
This effectively reverts 97618193 - but had to be done manually
and adjusted to maintain support for testing side tags and for
testing multiple tasks, since those features were added since
the update ISO change.
The 'scheduler injects ISOs of packages into the tests' approach
was intended to speed things up, especially for large updates,
and it did, but it had a few drawbacks. It means restarting
older tests from the web UI doesn't work as the ISOs get garbage
collected (you have to re-schedule in this case). And it has the
rather large problem that you can now only schedule tests from
the openQA server (or at least a machine with the openQA asset
share mounted), because the package download and ISO creation
just happen wherever the scheduler is running and assume that
the openQA asset share that will be used by the tests is at
/var/lib/openqa/share in that filesystem.
That's too big of a drawback to continue with this approach, IMO,
so this reverts back to the old way of doing things, with a bit
of refactoring to clean up the flow a little, and with support
for testing side tags and multiple tasks maintained.
As a follow-up I'm going to see if I can replace
_download_packages with a much more efficient downloader script
to mitigate the time this process takes on each test, especially
for large updates.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-01-05 19:41:50 +00:00
assert_script_run 'echo "repo --name=workarounds --baseurl=file:///mnt/workarounds_repo" >> ' . $ repoks ;
2022-12-10 17:25:29 +00:00
# and the buildroot repo, for Rawhide
if ( $ version eq $ rawrel ) {
2023-07-28 17:31:32 +00:00
assert_script_run 'echo "repo --name=koji-rawhide --baseurl=https://kojipkgs.fedoraproject.org/repos/f' . $ version . '-build/latest/\$basearch/" >> ' . $ repoks ;
2022-12-10 17:25:29 +00:00
}
2019-01-29 14:56:01 +00:00
# now flatten the kickstart
assert_script_run "ksflatten -c fedora-live-${lcsubv}.ks -o openqa.ks" ;
2024-01-04 23:01:15 +00:00
# FIXME: we need to hack this back out till a compose with the new
# group has run, remove after next Rawhide compose
if ( $ version eq $ rawrel && $ lcsubv eq "kde" ) {
assert_script_run "sed -i -e '/kde-spin-initial-setup/d' openqa.ks" ;
}
2019-01-29 14:56:01 +00:00
# upload the kickstart so we can check it
upload_logs "openqa.ks" ;
# now install the tools into the mock
2023-02-03 17:04:48 +00:00
assert_script_run "mock -r openqa --isolation=simple --install bash coreutils glibc-all-langpacks lorax-lmc-novirt selinux-policy-targeted shadow-utils util-linux" , 900 ;
2019-01-29 14:56:01 +00:00
# now make the image build directory inside the mock root and put the kickstart there
2021-03-10 00:02:06 +00:00
assert_script_run 'mock -r openqa --isolation=simple --chroot "mkdir -p /chroot_tmpdir"' ;
assert_script_run "mock -r openqa --isolation=simple --copyin openqa.ks /chroot_tmpdir" ;
2023-07-28 22:10:37 +00:00
# make sure volume ID isn't too long (for multiple Koji task cases)
my $ aot28 = substr ( $ advortask , 0 , 28 ) ;
my $ volid = "FWL-${aot28}" ;
2019-01-29 14:56:01 +00:00
# PULL SOME LEVERS! PULL SOME LEVERS!
2023-07-28 22:10:37 +00:00
assert_script_run "mock -r openqa --enable-network --isolation=simple --chroot \"/sbin/livemedia-creator --ks /chroot_tmpdir/openqa.ks --logfile /chroot_tmpdir/lmc-logs/livemedia-out.log --no-virt --resultdir /chroot_tmpdir/lmc --project Fedora-${subv}-Live --make-iso --volid ${volid} --iso-only --iso-name Fedora-${subv}-Live-${arch}-${advortask}.iso --releasever ${releasever} --macboot\"" , 7200 ;
2022-08-19 19:23:36 +00:00
unless ( script_run "mock -r openqa --isolation=simple --copyout /chroot_tmpdir/lmc-logs/livemedia-out.log ." , 90 ) {
2019-01-29 14:56:01 +00:00
upload_logs "livemedia-out.log" ;
}
2022-08-19 19:23:36 +00:00
unless ( script_run "mock -r openqa --isolation=simple --copyout /chroot_tmpdir/lmc-logs/anaconda/ anaconda" , 90 ) {
2019-01-29 14:56:01 +00:00
assert_script_run "tar cvzf anaconda.tar.gz anaconda/" ;
upload_logs "anaconda.tar.gz" ;
}
2022-08-19 19:23:36 +00:00
assert_script_run "mock -r openqa --isolation=simple --copyout /chroot_tmpdir/lmc/Fedora-${subv}-Live-${arch}-${advortask}.iso ." , 180 ;
2019-01-29 14:56:01 +00:00
upload_asset "./Fedora-${subv}-Live-${arch}-${advortask}.iso" ;
}
sub test_flags {
2022-07-28 20:32:57 +00:00
return { fatal = > 1 } ;
2019-01-29 14:56:01 +00:00
}
1 ;
# vim: set sw=4 et: