testing/os-autoinst-distri-rocky
11
0
Fork 0
mirror of https://github.com/rocky-linux/os-autoinst-distri-rocky.git synced 2024-11-09 15:01:23 +00:00
Code Issues Packages Projects Releases Wiki Activity
ae573f5cc8
os-autoinst-distri-rocky/templates.fif.json

1809 lines
67 KiB
JSON
Raw Normal View History

Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
{
"Machines": {
Change machine name from 64bit to bios
2024-07-01 09:57:51 +00:00
"bios": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"backend": "qemu",
"settings": {
"ARCH_BASE_MACHINE": "64bit",
"PART_TABLE_TYPE": "mbr",
"QEMUCPU": "Nehalem",
"QEMUCPUS": "2",
"QEMURAM": "2048",
support os-autoinst/openqa updates from upstream (#139)
2022-12-09 00:38:57 +00:00
"QEMU_VIDEO_DEVICE": "virtio-vga",
"XRES": "1024",
"YRES": "768",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"QEMU_VIRTIO_RNG": "1",
"WORKER_CLASS": "qemu_x86_64"
}
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"aarch64": {
"backend": "qemu",
"settings": {
"ARCH_BASE_MACHINE": "aarch64",
"PART_TABLE_TYPE": "gpt",
"QEMU": "aarch64",
"QEMUCPU": "host",
"QEMUCPUS": "2",
"QEMUMACHINE": "virt,gic-version=max",
update aarch64 machine
2024-01-24 05:10:17 +00:00
"QEMURAM": 4096,
"QEMU_MAX_MIGRATION_TIME": "480",
"QEMU_VIDEO_DEVICE": "virtio-gpu-pci",
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"QEMU_VIRTIO_RNG": "1",
"SERIALDEV": "ttyAMA0",
"TIMEOUT_SCALE": "1.5",
"UEFI": "1",
"UEFI_PFLASH_CODE": "/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw",
"UEFI_PFLASH_VARS": "/usr/share/edk2/aarch64/vars-template-pflash.raw",
"WORKER_CLASS": "qemu_aarch64"
}
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"s390x": {
"backend": "qemu",
"settings": {
"ARCH_BASE_MACHINE": "s390x",
"PART_TABLE_TYPE": "mbr",
"QEMU": "s390x",
"QEMU_APPEND": "bios /usr/share/qemu/390-ccw.img -boot once=cd0",
"QEMUMACHINE": "s390-ccw-virtio",
"QEMURAM": 4096,
"QEMU_VIDEO_DEVICE": "virtio-gpu",
"QEMU_MAX_MIGRATION_TIME": "480",
"QEMU_NO_KVM": "1",
"WORKER_CLASS": "qemu_s390x"
}
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"ppc64le": {
"backend": "qemu",
"settings": {
"ARCH_BASE_MACHINE": "ppc64le",
"OFW": 1,
"PART_TABLE_TYPE": "mbr",
"QEMU": "ppc64",
"QEMUCPU": "host",
"QEMURAM": 4096,
"QEMU_VIDEO_DEVICE": "VGA",
"QEMU_MAX_MIGRATION_TIME": "480",
"QEMU_VIRTIO_RNG": "1",
"WORKER_CLASS": "qemu_ppc64le"
}
},
Default secure boot
2024-07-03 11:22:56 +00:00
"uefx": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"backend": "qemu",
"settings": {
"ARCH_BASE_MACHINE": "64bit",
"PART_TABLE_TYPE": "gpt",
"QEMUCPU": "Nehalem",
"QEMUCPUS": "2",
"QEMURAM": "2048",
support os-autoinst/openqa updates from upstream (#139)
2022-12-09 00:38:57 +00:00
"QEMU_VIDEO_DEVICE": "virtio-vga",
"XRES": "1024",
"YRES": "768",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"QEMU_VIRTIO_RNG": "1",
"UEFI": "1",
"UEFI_PFLASH_CODE": "/usr/share/edk2/ovmf/OVMF_CODE.fd",
"UEFI_PFLASH_VARS": "/usr/share/edk2/ovmf/OVMF_VARS.fd",
"WORKER_CLASS": "qemu_x86_64"
}
secure boot machine uesb
2024-07-02 13:09:40 +00:00
},
Default secure boot
2024-07-03 11:22:56 +00:00
"uefi": {
secure boot machine uesb
2024-07-02 13:09:40 +00:00
"backend": "qemu",
"settings": {
"ARCH_BASE_MACHINE": "64bit",
"PART_TABLE_TYPE": "gpt",
"QEMUCPU": "Nehalem",
"QEMUCPUS": "2",
"QEMURAM": "3072",
"QEMU_VIDEO_DEVICE": "virtio-vga",
"XRES": "1024",
"YRES": "768",
"QEMUMACHINE": "q35,smm=on",
"QEMU_APPEND": "global driver=cfi.pflash01,property=secure,value=on",
"QEMU_MAX_MIGRATION_TIME": "480",
"QEMU_VIRTIO_RNG": "1",
"UEFI": "1",
"UEFI_PFLASH_CODE": "/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd",
"UEFI_PFLASH_VARS": "/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd",
"UEFI_SECURE": "1",
"WORKER_CLASS": "qemu_x86_64"
}
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"Products": {
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*": {
"arch": "x86_64",
"distri": "rocky",
"flavor": "GenericCloud_Base-qcow2-qcow2",
"settings": {
"BOOTFROM": "c",
"DEPLOY_UPLOAD_TEST": "",
"+HDD_1": "%HDD_2%",
"ISO": "cloudinit.iso",
"ROOT_PASSWORD": "weakpassword",
"TEST_TARGET": "HDD_1"
},
"version": "*"
},
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*": {
"arch": "x86_64",
"distri": "rocky",
"flavor": "GenericCloud_LVM-qcow2-qcow2",
"settings": {
"BOOTFROM": "c",
"DEPLOY_UPLOAD_TEST": "",
"+HDD_1": "%HDD_2%",
"ISO": "cloudinit.iso",
"ROOT_PASSWORD": "weakpassword",
"TEST_TARGET": "HDD_1"
},
"version": "*"
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-boot-iso-s390x-*": {
"arch": "s390x",
"distri": "rocky",
"flavor": "boot-iso",
"settings": {
"GRUB": "ip=dhcp",
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-boot-iso-ppc64le-*": {
"arch": "ppc64le",
"distri": "rocky",
"flavor": "boot-iso",
"settings": {
"GRUB": "ip=dhcp",
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
Provide tests for SIG/HPC slurm packages This MR provides a very, very basic test suite for the Slurm packages built by the HPC SIG. It checks the following: - Necessary packages for a single-node Slurm instance install successfully from the SIG/HPC repository - A job can be scheduled and executed to completion - A job can be scheduled and then cancelled ``` ./fifloader.py --clean --load templates.fif.json openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.8 CURRREL=8 BUILD=-${date +%Y%d%m}.0-slurm-8.8 TEST=slurm22,slurm23 openqa-cli api -X POST isos ISO=Rocky-9.2-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=9.2 CURRREL=9 BUILD=-${date +%Y%d%m}.0-slurm-9.2 TEST=slurm22,slurm23 ``` - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] Any dependent changes have been merged and published in downstream modules
2023-07-25 20:04:07 +00:00
"rocky-boot-iso-aarch64-*": {
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"arch": "aarch64",
"distri": "rocky",
"flavor": "boot-iso",
"settings": {
connect network during boot (#66) - updated configuration for boot-iso in templates.fif.json. NOTE: If you provide GRUB="value" during POST you must include "ip=dhcp" along with your custom GRUB settings. - short circuit _anaconda_network_enable.pm to check for connection at start of test. - provide needle to detect connected network interface using Network Spoke icon instead of Installation Source text. NOTE: While not required with minimal-iso or dvd-iso flavors specifying GRUB="ip=dhcp" will also connect the network interface at boot and bypass _anaconda_network_enable.
2021-12-03 00:18:43 +00:00
"GRUB": "ip=dhcp",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
},
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"rocky-boot-iso-x86_64-*": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"arch": "x86_64",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"distri": "rocky",
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"flavor": "boot-iso",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"settings": {
connect network during boot (#66) - updated configuration for boot-iso in templates.fif.json. NOTE: If you provide GRUB="value" during POST you must include "ip=dhcp" along with your custom GRUB settings. - short circuit _anaconda_network_enable.pm to check for connection at start of test. - provide needle to detect connected network interface using Network Spoke icon instead of Installation Source text. NOTE: While not required with minimal-iso or dvd-iso flavors specifying GRUB="ip=dhcp" will also connect the network interface at boot and bypass _anaconda_network_enable.
2021-12-03 00:18:43 +00:00
"GRUB": "ip=dhcp",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"+QEMURAM": 3072,
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-minimal-iso-s390x-*": {
"arch": "s390x",
"distri": "rocky",
"flavor": "minimal-iso",
"settings": {
"DEPLOY_UPLOAD_TEST": "install_minimal_upload",
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-minimal-iso-ppc64le-*": {
"arch": "ppc64le",
"distri": "rocky",
"flavor": "minimal-iso",
"settings": {
"DEPLOY_UPLOAD_TEST": "install_minimal_upload",
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-minimal-iso-aarch64-*": {
"arch": "aarch64",
"distri": "rocky",
"flavor": "minimal-iso",
"settings": {
"DEPLOY_UPLOAD_TEST": "install_minimal_upload",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
},
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"rocky-minimal-iso-x86_64-*": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"arch": "x86_64",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"distri": "rocky",
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"flavor": "minimal-iso",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"settings": {
Try harder to apply that 3GiB RAM setting Seems it may need the magic override... Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-17 19:44:54 +00:00
"+QEMURAM": 3072,
add install_minimal_upload test suite
2021-08-18 01:23:52 +00:00
"DEPLOY_UPLOAD_TEST": "install_minimal_upload",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*": {
"arch": "s390x",
"distri": "rocky",
"flavor": "dvd-iso",
"settings": {
"DEPLOY_UPLOAD_TEST": "install_default_upload",
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*": {
"arch": "ppc64le",
"distri": "rocky",
"flavor": "dvd-iso",
"settings": {
"DEPLOY_UPLOAD_TEST": "install_default_upload",
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*": {
"arch": "aarch64",
"distri": "rocky",
"flavor": "dvd-iso",
"settings": {
"DEPLOY_UPLOAD_TEST": "install_default_upload",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
},
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"rocky-dvd-iso-x86_64-*": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"arch": "x86_64",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"distri": "rocky",
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"flavor": "dvd-iso",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"settings": {
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"DEPLOY_UPLOAD_TEST": "install_default_upload",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-package-set-s390x-*": {
"arch": "s390x",
"distri": "rocky",
"flavor": "package-set",
"settings": {
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-package-set-ppc64le-*": {
"arch": "ppc64le",
"distri": "rocky",
"flavor": "package-set",
"settings": {
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-package-set-aarch64-*": {
"arch": "aarch64",
"distri": "rocky",
"flavor": "package-set",
"settings": {
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
},
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
"rocky-package-set-x86_64-*": {
"arch": "x86_64",
"distri": "rocky",
"flavor": "package-set",
"settings": {
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*": {
"arch": "s390x",
"distri": "rocky",
"flavor": "universal",
"settings": {
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*": {
"arch": "ppc64le",
"distri": "rocky",
"flavor": "universal",
"settings": {
"HDDSIZEGB": "15",
"TEST_TARGET": "ISO"
},
"version": "*"
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*": {
"arch": "aarch64",
"distri": "rocky",
"flavor": "universal",
"settings": {
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"rocky-universal-x86_64-*": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"arch": "x86_64",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"distri": "rocky",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"flavor": "universal",
"settings": {
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"TEST_TARGET": "ISO"
},
"version": "*"
}
},
"Profiles": {
Change machine name from 64bit to bios
2024-07-01 09:57:51 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": {
"machine": "bios",
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"product": "rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*"
},
Change machine name from 64bit to bios
2024-07-01 09:57:51 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": {
"machine": "bios",
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"product": "rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*"
},
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": {
"machine": "uefi",
"product": "rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*"
},
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": {
"machine": "uefi",
"product": "rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*"
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-boot-iso-s390x-*-s390x": {
"machine": "s390x",
fix copy-paste error in product for s390x
2024-01-29 00:17:15 +00:00
"product": "rocky-boot-iso-s390x-*"
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-boot-iso-ppc64le-*-ppc64le": {
"machine": "ppc64le",
"product": "rocky-boot-iso-ppc64le-*"
},
Provide tests for SIG/HPC slurm packages This MR provides a very, very basic test suite for the Slurm packages built by the HPC SIG. It checks the following: - Necessary packages for a single-node Slurm instance install successfully from the SIG/HPC repository - A job can be scheduled and executed to completion - A job can be scheduled and then cancelled ``` ./fifloader.py --clean --load templates.fif.json openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.8 CURRREL=8 BUILD=-${date +%Y%d%m}.0-slurm-8.8 TEST=slurm22,slurm23 openqa-cli api -X POST isos ISO=Rocky-9.2-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=9.2 CURRREL=9 BUILD=-${date +%Y%d%m}.0-slurm-9.2 TEST=slurm22,slurm23 ``` - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] Any dependent changes have been merged and published in downstream modules
2023-07-25 20:04:07 +00:00
"rocky-boot-iso-aarch64-*-aarch64": {
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"machine": "aarch64",
"product": "rocky-boot-iso-aarch64-*"
},
Change machine name from 64bit to bios
2024-07-01 09:57:51 +00:00
"rocky-boot-iso-x86_64-*-bios": {
"machine": "bios",
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"product": "rocky-boot-iso-x86_64-*"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"rocky-boot-iso-x86_64-*-uefi": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"machine": "uefi",
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"product": "rocky-boot-iso-x86_64-*"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-minimal-iso-s390x-*-s390x": {
"machine": "s390x",
fix copy-paste error in product for s390x
2024-01-29 00:17:15 +00:00
"product": "rocky-minimal-iso-s390x-*"
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-minimal-iso-ppc64le-*-ppc64le": {
"machine": "ppc64le",
"product": "rocky-minimal-iso-ppc64le-*"
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-minimal-iso-aarch64-*-aarch64": {
"machine": "aarch64",
"product": "rocky-minimal-iso-aarch64-*"
},
minimal-iso uefi profile
2024-07-13 13:30:20 +00:00
"rocky-minimal-iso-x86_64-*-uefi": {
"machine": "uefi",
"product": "rocky-minimal-iso-x86_64-*"
},
Change machine name from 64bit to bios
2024-07-01 09:57:51 +00:00
"rocky-minimal-iso-x86_64-*-bios": {
"machine": "bios",
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"product": "rocky-minimal-iso-x86_64-*"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": {
"machine": "s390x",
fix copy-paste error in product for s390x
2024-01-29 00:17:15 +00:00
"product": "rocky-dvd-iso-s390x-*"
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": {
"machine": "ppc64le",
"product": "rocky-dvd-iso-ppc64le-*"
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": {
"machine": "aarch64",
"product": "rocky-dvd-iso-aarch64-*"
},
Change machine name from 64bit to bios
2024-07-01 09:57:51 +00:00
"rocky-dvd-iso-x86_64-*-bios": {
"machine": "bios",
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"product": "rocky-dvd-iso-x86_64-*"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"rocky-dvd-iso-x86_64-*-uefi": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"machine": "uefi",
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"product": "rocky-dvd-iso-x86_64-*"
Automate the Anaconda_Save_Traceback_to_Bugzilla_Text test case. This PR adds a new test that automates the above mentioned test case. It starts the installation in text mode using the `install_text` test case, which it interrupts using the Anaconda crash trigger. When the crash happens, it goes through the process of reporting the bug to Bugzilla, checks that Bugzilla sends a positive confirmation of the action, but also performs some REST API calls to do a proper check and then it closes the bug to clean up.
2021-04-27 11:02:53 +00:00
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-package-set-s390x-*-s390x": {
"machine": "s390x",
fix copy-paste error in product for s390x
2024-01-29 00:17:15 +00:00
"product": "rocky-package-set-s390x-*"
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-package-set-ppc64le-*-ppc64le": {
"machine": "ppc64le",
"product": "rocky-package-set-ppc64le-*"
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-package-set-aarch64-*-aarch64": {
"machine": "aarch64",
"product": "rocky-package-set-aarch64-*"
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
},
Change machine name from 64bit to bios
2024-07-01 09:57:51 +00:00
"rocky-package-set-x86_64-*-bios": {
"machine": "bios",
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
"product": "rocky-package-set-x86_64-*"
},
"rocky-package-set-x86_64-*-uefi": {
package-set uefi is machine uefi
2024-07-01 14:54:42 +00:00
"machine": "uefi",
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
"product": "rocky-package-set-x86_64-*"
},
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": {
"machine": "s390x",
fix copy-paste error in product for s390x
2024-01-29 00:17:15 +00:00
"product": "rocky-universal-s390x-*"
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
},
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": {
"machine": "ppc64le",
"product": "rocky-universal-ppc64le-*"
},
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": {
"machine": "aarch64",
"product": "rocky-universal-aarch64-*"
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
},
Change machine name from 64bit to bios
2024-07-01 09:57:51 +00:00
"rocky-universal-x86_64-*-bios": {
"machine": "bios",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"product": "rocky-universal-x86_64-*"
Automate the Anaconda_Save_Traceback_to_Bugzilla_Text test case. This PR adds a new test that automates the above mentioned test case. It starts the installation in text mode using the `install_text` test case, which it interrupts using the Anaconda crash trigger. When the crash happens, it goes through the process of reporting the bug to Bugzilla, checks that Bugzilla sends a positive confirmation of the action, but also performs some REST API calls to do a proper check and then it closes the bug to clean up.
2021-04-27 11:02:53 +00:00
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"rocky-universal-x86_64-*-uefi": {
Automate the Anaconda_Save_Traceback_to_Bugzilla_Text test case. This PR adds a new test that automates the above mentioned test case. It starts the installation in text mode using the `install_text` test case, which it interrupts using the Anaconda crash trigger. When the crash happens, it goes through the process of reporting the bug to Bugzilla, checks that Bugzilla sends a positive confirmation of the action, but also performs some REST API calls to do a proper check and then it closes the bug to clean up.
2021-04-27 11:02:53 +00:00
"machine": "uefi",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"product": "rocky-universal-x86_64-*"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"TestSuites": {
Automate the QA:Testcase_Anaconda_help. This PR automates the mentioned testcase to test that Help can be displayed in Anaconda during the installation. It navigates through the available Help screens and if it can see it, it finishes. This test runs after `install_default_upload` to override the installation defaults defined for all primary tests. Delete a duplicated needle. Reformat list extensions to make it nicer. Get rid of wrong export and an empty line. Delete empty line. Use _boot_to_anaconda for booting and move subroutine accordingly. Add variable to templates.fif.json Delete trailing whitespace. Fix calling the pretest. Move help checking to another place.
2021-05-03 15:37:46 +00:00
"anaconda_help": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Automate the QA:Testcase_Anaconda_help. This PR automates the mentioned testcase to test that Help can be displayed in Anaconda during the installation. It navigates through the available Help screens and if it can see it, it finishes. This test runs after `install_default_upload` to override the installation defaults defined for all primary tests. Delete a duplicated needle. Reformat list extensions to make it nicer. Get rid of wrong export and an empty line. Delete empty line. Use _boot_to_anaconda for booting and move subroutine accordingly. Add variable to templates.fif.json Delete trailing whitespace. Fix calling the pretest. Move help checking to another place.
2021-05-03 15:37:46 +00:00
},
"settings": {
"ENTRYPOINT": "_boot_to_anaconda anaconda_help",
"HELPCHECK": "1"
}
},
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"base_reboot_unmount": {
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": 30,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "base_reboot_unmount",
"ROOT_PASSWORD": "weakpassword",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"USER_LOGIN": "false"
}
},
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"base_system_logging": {
base tests: run on Cloud, add one on aarch64, clean up priorities This adds new variant test suites for several of the base tests to run them on Cloud disk images. We can't re-use the existing test suites because they have `START_AFTER_TEST` defined and there's no viable way to undefine it (there are things you can do to override the value, but you can't just unset it). Also add a stray test we weren't running on aarch64, and correct some priorities. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-06-17 22:18:21 +00:00
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": 30,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
base tests: run on Cloud, add one on aarch64, clean up priorities This adds new variant test suites for several of the base tests to run them on Cloud disk images. We can't re-use the existing test suites because they have `START_AFTER_TEST` defined and there's no viable way to undefine it (there are things you can do to override the value, but you can't just unset it). Also add a stray test we weren't running on aarch64, and correct some priorities. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-06-17 22:18:21 +00:00
"POSTINSTALL": "base_system_logging",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"ROOT_PASSWORD": "weakpassword",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"USER_LOGIN": "false"
}
},
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"base_update_cli": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": 30,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
base tests: run on Cloud, add one on aarch64, clean up priorities This adds new variant test suites for several of the base tests to run them on Cloud disk images. We can't re-use the existing test suites because they have `START_AFTER_TEST` defined and there's no viable way to undefine it (there are things you can do to override the value, but you can't just unset it). Also add a stray test we weren't running on aarch64, and correct some priorities. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-06-17 22:18:21 +00:00
"POSTINSTALL": "base_update_cli",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"ROOT_PASSWORD": "weakpassword",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"USER_LOGIN": "false"
}
},
Add testcase to test the Package_install_remove testcase.
2021-03-15 17:40:42 +00:00
"base_package_install_remove": {
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": 30,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 40
Add testcase to test the Package_install_remove testcase.
2021-03-15 17:40:42 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Add testcase to test the Package_install_remove testcase.
2021-03-15 17:40:42 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "base_package_install_remove",
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false"
}
},
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"base_services_start": {
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": 30,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "base_services_start",
"ROOT_PASSWORD": "weakpassword",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"USER_LOGIN": "false"
}
},
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"base_selinux": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": 30,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
base tests: run on Cloud, add one on aarch64, clean up priorities This adds new variant test suites for several of the base tests to run them on Cloud disk images. We can't re-use the existing test suites because they have `START_AFTER_TEST` defined and there's no viable way to undefine it (there are things you can do to override the value, but you can't just unset it). Also add a stray test we weren't running on aarch64, and correct some priorities. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-06-17 22:18:21 +00:00
"POSTINSTALL": "base_selinux",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"ROOT_PASSWORD": "weakpassword",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"USER_LOGIN": "false"
}
},
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"base_service_manipulation": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": 30,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
base tests: run on Cloud, add one on aarch64, clean up priorities This adds new variant test suites for several of the base tests to run them on Cloud disk images. We can't re-use the existing test suites because they have `START_AFTER_TEST` defined and there's no viable way to undefine it (there are things you can do to override the value, but you can't just unset it). Also add a stray test we weren't running on aarch64, and correct some priorities. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-06-17 22:18:21 +00:00
"POSTINSTALL": "base_service_manipulation",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"ROOT_PASSWORD": "weakpassword",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"USER_LOGIN": "false"
}
},
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"cloud_autocloud": {
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_Base-qcow2-qcow2-x86_64-*-uefi": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-bios": 31,
add support for GenericCloud image testing
2023-01-26 18:07:42 +00:00
"rocky-GenericCloud_LVM-qcow2-qcow2-x86_64-*-uefi": 30
},
"settings": {
"POSTINSTALL": "autocloud"
}
},
Provide tests for SIG/HPC slurm packages This MR provides a very, very basic test suite for the Slurm packages built by the HPC SIG. It checks the following: - Necessary packages for a single-node Slurm instance install successfully from the SIG/HPC repository - A job can be scheduled and executed to completion - A job can be scheduled and then cancelled ``` ./fifloader.py --clean --load templates.fif.json openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.8 CURRREL=8 BUILD=-${date +%Y%d%m}.0-slurm-8.8 TEST=slurm22,slurm23 openqa-cli api -X POST isos ISO=Rocky-9.2-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=9.2 CURRREL=9 BUILD=-${date +%Y%d%m}.0-slurm-9.2 TEST=slurm22,slurm23 ``` - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] Any dependent changes have been merged and published in downstream modules
2023-07-25 20:04:07 +00:00
"install_resize_lvm": {
Add to templates.
2020-05-11 13:55:16 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Device root resize changes
2024-07-30 15:00:46 +00:00
"rocky-dvd-iso-x86_64-*-bios": 41,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 40
Add to templates.
2020-05-11 13:55:16 +00:00
},
"settings": {
feat: set DESKTOP=false and PACKAGE_SET=minimal for dvd-iso
2022-07-19 00:18:59 +00:00
"DESKTOP": "false",
"PACKAGE_SET": "minimal",
Finish the post review changes.
2020-05-28 09:40:34 +00:00
"PARTITIONING": "custom_resize_lvm",
Add an installation test using LVM partitioning as asset for resize tests. When Fedora went to BTRFS as a default, we lost the LVM based image to run LVM resize tests with. This PR introduces the `install_lvm.pm` installation test that creates an LVM based qcow2 image to be used by follow-up tests.
2020-11-18 12:44:05 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
Add to templates.
2020-05-11 13:55:16 +00:00
"INSTALL": "1",
Add an installation test using LVM partitioning as asset for resize tests. When Fedora went to BTRFS as a default, we lost the LVM based image to run LVM resize tests with. This PR introduces the `install_lvm.pm` installation test that creates an LVM based qcow2 image to be used by follow-up tests.
2020-11-18 12:44:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "install_lvm_ext4"
Add to templates.
2020-05-11 13:55:16 +00:00
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"install_anaconda_text": {
Enable several desktop tests on Workstation aarch64 disk image Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-11-03 00:34:43 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 20
Enable several desktop tests on Workstation aarch64 disk image Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-11-03 00:34:43 +00:00
},
"settings": {
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"ANACONDA_TEXT": "1"
Enable several desktop tests on Workstation aarch64 disk image Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-11-03 00:34:43 +00:00
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"install_arabic_language": {
Enable several desktop tests on Workstation aarch64 disk image Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-11-03 00:34:43 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"DESKTOP": "gnome",
"ENCRYPT_PASSWORD": "weakpassword",
"LANGUAGE": "arabic",
support language tests in aarch64 - aarch64 doesn't have workstation-product-environment so switch to graphical-server-environment
2024-05-27 20:53:44 +00:00
"PACKAGE_SET": "graphical-server",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"POSTINSTALL": "_console_login",
"QEMU_DISABLE_SNAPSHOTS": "1",
"REPOSITORY_VARIATION": "%LOCATION%",
"ROOT_PASSWORD": "weakpassword",
"SWITCHED_LAYOUT": "1",
"USER_LOGIN": "qwerty"
}
},
"install_asian_language": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"DESKTOP": "gnome",
"ENCRYPT_PASSWORD": "weakpassword",
"INPUT_METHOD": "1",
"LANGUAGE": "japanese",
support language tests in aarch64 - aarch64 doesn't have workstation-product-environment so switch to graphical-server-environment
2024-05-27 20:53:44 +00:00
"PACKAGE_SET": "graphical-server",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"POSTINSTALL": "_console_login",
"QEMU_DISABLE_SNAPSHOTS": "1",
"REPOSITORY_VARIATION": "%LOCATION%",
"ROOT_PASSWORD": "weakpassword",
"USER_LOGIN": "qwerty"
}
},
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
"install_custom_gui_lvm_ext4": {
Add a new testcase to test creation of LVM with ext4 using Blivet. This PR adds a test that uses the Blivet interface to create an LVM layout with ext4 filesystem as well as a postinstall test that checks that the LVM layout has been created correctly.
2020-12-08 10:14:40 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-dvd-iso-x86_64-*-bios": 41,
"rocky-dvd-iso-x86_64-*-uefi": 40
Add a new testcase to test creation of LVM with ext4 using Blivet. This PR adds a test that uses the Blivet interface to create an LVM layout with ext4 filesystem as well as a postinstall test that checks that the LVM layout has been created correctly.
2020-12-08 10:14:40 +00:00
},
"settings": {
feat: set DESKTOP=false and PACKAGE_SET=minimal for dvd-iso
2022-07-19 00:18:59 +00:00
"DESKTOP": "false",
"PACKAGE_SET": "minimal",
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
"PARTITIONING": "custom_gui_lvm_ext4",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "15",
Add a new testcase to test creation of LVM with ext4 using Blivet. This PR adds a test that uses the Blivet interface to create an LVM layout with ext4 filesystem as well as a postinstall test that checks that the LVM layout has been created correctly.
2020-12-08 10:14:40 +00:00
"POSTINSTALL": "disk_custom_lvm_ext4_postinstall",
"ROOT_PASSWORD": "weakpassword"
}
},
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
"install_custom_gui_standard_partition_ext4": {
Create Blivet standard partitioning with ext4 testcase. This PR introduces a test case that uses the Blivet partitioning tool to create a standard partitioning layout with / and /boot (and specific partitions for UEFI and ARM64) using ext4 as the selected filesystem. It also adds a postinstallation test to check that the partitions have been created correctly.
2020-12-07 12:33:37 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-dvd-iso-x86_64-*-bios": 41,
"rocky-dvd-iso-x86_64-*-uefi": 40
Create Blivet standard partitioning with ext4 testcase. This PR introduces a test case that uses the Blivet partitioning tool to create a standard partitioning layout with / and /boot (and specific partitions for UEFI and ARM64) using ext4 as the selected filesystem. It also adds a postinstallation test to check that the partitions have been created correctly.
2020-12-07 12:33:37 +00:00
},
"settings": {
feat: set DESKTOP=false and PACKAGE_SET=minimal for dvd-iso
2022-07-19 00:18:59 +00:00
"DESKTOP": "false",
"PACKAGE_SET": "minimal",
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
"PARTITIONING": "custom_gui_standard_partition_ext4",
Add 'with swap' tests, drop swap parts from other tests (#180) In Fedora 33, we generally no longer include a disk-based swap partition by default (instead swap-on-ZRAM is used, see https://fedoraproject.org/wiki/Changes/SwapOnZRAM ). This tweaks our tests to account for that. In tests that aren't to do with swap at all, we stop including a swap partition in order to be closer to the default layout. We replace the old _no_swap blivet and custom tests with _with_swap tests that, as the name implies, *explicitly include* a swap partition, and adjust the postinstall test to check the disk swap partition is there. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-08-11 20:34:37 +00:00
"ROOT_PASSWORD": "weakpassword"
}
},
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
"install_custom_gui_software_raid": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 41,
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"NUMDISKS": "2",
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
"PARTITIONING": "custom_gui_software_raid",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"POSTINSTALL": "disk_custom_software_raid_postinstall",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
"install_custom_gui_xfs": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 41,
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
Replace blivet tests with custom GUI tests (#51) * Our default partitioning scheme includes swap, so omit these tests * Remove redundant test suites The suites removed from this commit are functionally identical to the test suites with the same name but omitting the word "blivet". * Add needles for custom partitioning GUI * Replace install_blivet_lvm_ext4 with install_custom_gui_lvm_ext4 - Add subroutine for adding a partition using the "Custom" GUI - Replace references to blivet with custom_gui in FIF template - Define test suite for the "Custom" GUI * syntax fix * Needle fixes per feedback from lumarel * Needle reorg * Replace mouse actions with keypresses * A few comments * Replace blivet_standard_partition suites with custom_gui_standard_partition suites * Rewrite XFS partitioning suite for custom-gui * Fix filesystem for swap * Add test suite and needles for RAID using the custom-gui partitioner * Make raidlevel parameter less confusing * Fix needles
2021-10-26 15:56:01 +00:00
"PARTITIONING": "custom_gui_xfs",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"POSTINSTALL": "disk_custom_xfs_postinstall",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_cyrillic_language": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"DESKTOP": "gnome",
"ENCRYPT_PASSWORD": "weakpassword",
"LANGUAGE": "russian",
support language tests in aarch64 - aarch64 doesn't have workstation-product-environment so switch to graphical-server-environment
2024-05-27 20:53:44 +00:00
"PACKAGE_SET": "graphical-server",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"POSTINSTALL": "_console_login",
"QEMU_DISABLE_SNAPSHOTS": "1",
"REPOSITORY_VARIATION": "%LOCATION%",
"ROOT_PASSWORD": "weakpassword",
"SWITCHED_LAYOUT": "1",
"USER_LOGIN": "qwerty"
}
},
"install_default": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-boot-iso-s390x-*-s390x": 10,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-boot-iso-ppc64le-*-ppc64le": 10,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-boot-iso-aarch64-*-aarch64": 10,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-boot-iso-x86_64-*-bios": 11,
"rocky-boot-iso-x86_64-*-uefi": 10,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 11,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 11,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 11,
remove refs to platform specific media
2021-08-10 04:55:18 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 11
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
Test Suite: install_default on rocky-8.5-[minimal|boot|dvd]-iso-x86_64 (#77) Merging per testing team conversation meeting. * Correctly check for default packagesets for each flavor * FIF updates for default packagesets - Set DESKTOP=gnome to trigger graphical_wait_login instead of console_wait_login - Increase virtual disk size to account for default packagesets * Correctly check for minimal-iso default packageset * Updated needles for issue 16 * Update templates.fif.json with package set test suites Package sets tested per ISO will follow these conventions: - Test suites will not be duplicated between the boot and dvd ISOs - All default package sets will be tested against dvd-iso - Boot ISO will be considered valid if `minimal` package set installs cleanly * Do not add updated needle with changed hostname
2022-03-31 23:23:01 +00:00
"DESKTOP": "gnome",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"PACKAGE_SET": "default",
"POSTINSTALL": "_collect_data"
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"install_minimal": {
"profiles": {
Add network install to comply with QA:Testcase Minimal Installation
2024-05-06 11:50:22 +00:00
"rocky-boot-iso-s390x-*-s390x": 10,
"rocky-boot-iso-ppc64le-*-ppc64le": 10,
"rocky-boot-iso-aarch64-*-aarch64": 10,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-boot-iso-x86_64-*-bios": 11,
"rocky-boot-iso-x86_64-*-uefi": 10,
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-minimal-iso-s390x-*-s390x": 10,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-minimal-iso-ppc64le-*-ppc64le": 10,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-minimal-iso-aarch64-*-aarch64": 10,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-minimal-iso-x86_64-*-uefi": 10,
"rocky-minimal-iso-x86_64-*-bios": 11
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
},
"settings": {
"PACKAGE_SET": "minimal",
"POSTINSTALL": "_collect_data"
}
},
add install_minimal_upload test suite
2021-08-18 01:23:52 +00:00
"install_minimal_upload": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-minimal-iso-s390x-*-s390x": 10,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-minimal-iso-ppc64le-*-ppc64le": 10,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-minimal-iso-aarch64-*-aarch64": 10,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-minimal-iso-x86_64-*-uefi": 10,
"rocky-minimal-iso-x86_64-*-bios": 11
add install_minimal_upload test suite
2021-08-18 01:23:52 +00:00
},
"settings": {
"PACKAGE_SET": "minimal",
"POSTINSTALL": "_collect_data",
"STORE_HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2"
}
},
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"install_default_upload": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 10,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 10,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 10,
Remove inconsistencies
2024-07-15 15:36:27 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 10
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
FEATURE: Add `DNF_CONTENTDIR` override support (#119) * add dnf_contentdir library function and implement is sample tests * Short circuit auto addition of _console_wait_login for tests without DESKTOP * support use of REPOSITORY_GRAPHICAL and ADD_REPOSITORY_GRAPHICAL test variables * deprecate addition of dnf_contentdir lib function * create and use get_version_major utility function * resolve mismatch of login type caused by incorrect template entries * add and use _staging_repos_enable post-install test * add install_package_set_* tests only to package-set flavor * fix variable re-declaration warning/error * add rocky-getting-started-tour needles * release rocky-repos content require switch from mirrorlist to baseurl * implement DNF_CONTENTDIR swap as post-install action before reboot/login * temp disable _staging_repos_enable * incomplete fix for _graphical_wait_login - get_release_number is used heavily in our openQA but makes no sense in Rocky. Multiple possible solutions but this one allows `_graphical_wait_login` to pass. NEEDS_WORK
2022-07-10 21:05:04 +00:00
"DESKTOP": "gnome",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"PACKAGE_SET": "default",
"POSTINSTALL": "_collect_data",
"STORE_HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2"
}
},
"install_delete_partial": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 30,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 31,
"rocky-universal-x86_64-*-uefi": 30
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"HDD_1": "disk_full_%PART_TABLE_TYPE%.img",
"PARTITIONING": "guided_delete_partial",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_delete_pata": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 20,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 21,
"rocky-universal-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"HDDMODEL": "ide-hd",
"HDD_1": "disk_full_mbr.img",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "20",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"PARTITIONING": "guided_delete_all",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_european_language": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"DESKTOP": "gnome",
"ENCRYPT_PASSWORD": "weakpassword",
"LANGUAGE": "french",
"NO_UEFI_POST": "1",
support language tests in aarch64 - aarch64 doesn't have workstation-product-environment so switch to graphical-server-environment
2024-05-27 20:53:44 +00:00
"PACKAGE_SET": "graphical-server",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"POSTINSTALL": "_console_login",
"QEMU_DISABLE_SNAPSHOTS": "1",
"REPOSITORY_VARIATION": "%LOCATION%",
"ROOT_PASSWORD": "weakpassword",
"USER_LOGIN": "qwerty"
}
},
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"install_iscsi": {
"profiles": {
"rocky-universal-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-universal-x86_64-*-bios": 40
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"ANACONDA_STATIC": "172.16.2.111",
"INSTALL_UNLOCK": "support_ready",
"NICTYPE": "tap",
"PARALLEL_WITH": "support_server",
"PARTITIONING": "custom_iscsi",
"ROOT_PASSWORD": "weakpassword",
"WORKER_CLASS": "tap"
}
},
"install_kickstart_nfs": {
"profiles": {
"rocky-universal-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-universal-x86_64-*-bios": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"GRUB": "inst.ks=nfs:172.16.2.110:/export/root-user-crypted-net.ks",
"INSTALL_UNLOCK": "support_ready",
"KICKSTART": "1",
"NICTYPE": "tap",
"PARALLEL_WITH": "support_server",
"ROOT_PASSWORD": "111111",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"install_lvmthin": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 41,
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"PARTITIONING": "custom_lvmthin",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
Add an installation test using LVM partitioning as asset for resize tests. When Fedora went to BTRFS as a default, we lost the LVM based image to run LVM resize tests with. This PR introduces the `install_lvm.pm` installation test that creates an LVM based qcow2 image to be used by follow-up tests.
2020-11-18 12:44:05 +00:00
"install_lvm_ext4": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Device root resize changes
2024-07-30 15:00:46 +00:00
"rocky-dvd-iso-x86_64-*-bios": 41,
Remove inconsistencies
2024-07-15 15:36:27 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 40
Add an installation test using LVM partitioning as asset for resize tests. When Fedora went to BTRFS as a default, we lost the LVM based image to run LVM resize tests with. This PR introduces the `install_lvm.pm` installation test that creates an LVM based qcow2 image to be used by follow-up tests.
2020-11-18 12:44:05 +00:00
},
"settings": {
feat: set DESKTOP=false and PACKAGE_SET=minimal for dvd-iso
2022-07-19 00:18:59 +00:00
"DESKTOP": "false",
"PACKAGE_SET": "minimal",
Add a new testcase to test creation of LVM with ext4 using Blivet. This PR adds a test that uses the Blivet interface to create an LVM layout with ext4 filesystem as well as a postinstall test that checks that the LVM layout has been created correctly.
2020-12-08 10:14:40 +00:00
"PARTITIONING": "custom_lvm_ext4",
Add an installation test using LVM partitioning as asset for resize tests. When Fedora went to BTRFS as a default, we lost the LVM based image to run LVM resize tests with. This PR introduces the `install_lvm.pm` installation test that creates an LVM based qcow2 image to be used by follow-up tests.
2020-11-18 12:44:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"STORE_HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2"
}
},
Add an installation test using Standard partitioning with ext4. This PR add the installation test which uses Standard partitioning with an ext4 filesystem to cover one of the new requirements as described in issue #202. Fixed after a review
2020-11-24 13:19:04 +00:00
"install_standard_partition_ext4": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 30,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-dvd-iso-x86_64-*-bios": 31,
"rocky-dvd-iso-x86_64-*-uefi": 30
Add an installation test using Standard partitioning with ext4. This PR add the installation test which uses Standard partitioning with an ext4 filesystem to cover one of the new requirements as described in issue #202. Fixed after a review
2020-11-24 13:19:04 +00:00
},
"settings": {
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Add an installation test using Standard partitioning with ext4. This PR add the installation test which uses Standard partitioning with an ext4 filesystem to cover one of the new requirements as described in issue #202. Fixed after a review
2020-11-24 13:19:04 +00:00
"PARTITIONING": "custom_standard_partition_ext4",
"ROOT_PASSWORD": "weakpassword"
}
},
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"install_mirrorlist_graphical": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
Mirrorlist test changes for Issue #146
2023-03-11 14:15:58 +00:00
"MIRRORLIST_GRAPHICAL": "1",
"PACKAGE_SET": "server"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_multi": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 20,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 21,
"rocky-universal-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"HDD_2": "disk_full_mbr.img",
"NUMDISKS": "2",
"PARTITIONING": "guided_multi",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_multi_empty": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 30,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 31,
"rocky-universal-x86_64-*-uefi": 30
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"NUMDISKS": "2",
"PARTITIONING": "guided_multi_empty_all",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
Add 'with swap' tests, drop swap parts from other tests (#180) In Fedora 33, we generally no longer include a disk-based swap partition by default (instead swap-on-ZRAM is used, see https://fedoraproject.org/wiki/Changes/SwapOnZRAM ). This tweaks our tests to account for that. In tests that aren't to do with swap at all, we stop including a swap partition in order to be closer to the default layout. We replace the old _no_swap blivet and custom tests with _with_swap tests that, as the name implies, *explicitly include* a swap partition, and adjust the postinstall test to check the disk swap partition is there. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-08-11 20:34:37 +00:00
"install_with_swap": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 50,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 50,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 50,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 51,
"rocky-universal-x86_64-*-uefi": 50
Add 'with swap' tests, drop swap parts from other tests (#180) In Fedora 33, we generally no longer include a disk-based swap partition by default (instead swap-on-ZRAM is used, see https://fedoraproject.org/wiki/Changes/SwapOnZRAM ). This tweaks our tests to account for that. In tests that aren't to do with swap at all, we stop including a swap partition in order to be closer to the default layout. We replace the old _no_swap blivet and custom tests with _with_swap tests that, as the name implies, *explicitly include* a swap partition, and adjust the postinstall test to check the disk swap partition is there. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-08-11 20:34:37 +00:00
},
"settings": {
"PARTITIONING": "custom_with_swap",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add 'with swap' tests, drop swap parts from other tests (#180) In Fedora 33, we generally no longer include a disk-based swap partition by default (instead swap-on-ZRAM is used, see https://fedoraproject.org/wiki/Changes/SwapOnZRAM ). This tweaks our tests to account for that. In tests that aren't to do with swap at all, we stop including a swap partition in order to be closer to the default layout. We replace the old _no_swap blivet and custom tests with _with_swap tests that, as the name implies, *explicitly include* a swap partition, and adjust the postinstall test to check the disk swap partition is there. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-08-11 20:34:37 +00:00
}
},
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
"install_package_set_minimal": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"profiles": {
Resolve conflicts due merge #219
2024-07-24 13:57:02 +00:00
"rocky-package-set-aarch64-*-aarch64": 30,
Reapply bios to uefi changes
2024-07-25 07:17:56 +00:00
"rocky-package-set-x86_64-*-uefi": 30
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
FEATURE: Add `DNF_CONTENTDIR` override support (#119) * add dnf_contentdir library function and implement is sample tests * Short circuit auto addition of _console_wait_login for tests without DESKTOP * support use of REPOSITORY_GRAPHICAL and ADD_REPOSITORY_GRAPHICAL test variables * deprecate addition of dnf_contentdir lib function * create and use get_version_major utility function * resolve mismatch of login type caused by incorrect template entries * add and use _staging_repos_enable post-install test * add install_package_set_* tests only to package-set flavor * fix variable re-declaration warning/error * add rocky-getting-started-tour needles * release rocky-repos content require switch from mirrorlist to baseurl * implement DNF_CONTENTDIR swap as post-install action before reboot/login * temp disable _staging_repos_enable * incomplete fix for _graphical_wait_login - get_release_number is used heavily in our openQA but makes no sense in Rocky. Multiple possible solutions but this one allows `_graphical_wait_login` to pass. NEEDS_WORK
2022-07-10 21:05:04 +00:00
"DESKTOP": "false",
"PACKAGE_SET": "minimal"
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
}
},
"install_package_set_server": {
"profiles": {
Resolve conflicts due merge #219
2024-07-24 13:57:02 +00:00
"rocky-package-set-aarch64-*-aarch64": 30,
Reapply bios to uefi changes
2024-07-25 07:17:56 +00:00
"rocky-package-set-x86_64-*-uefi": 30
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
},
"settings": {
FEATURE: Add `DNF_CONTENTDIR` override support (#119) * add dnf_contentdir library function and implement is sample tests * Short circuit auto addition of _console_wait_login for tests without DESKTOP * support use of REPOSITORY_GRAPHICAL and ADD_REPOSITORY_GRAPHICAL test variables * deprecate addition of dnf_contentdir lib function * create and use get_version_major utility function * resolve mismatch of login type caused by incorrect template entries * add and use _staging_repos_enable post-install test * add install_package_set_* tests only to package-set flavor * fix variable re-declaration warning/error * add rocky-getting-started-tour needles * release rocky-repos content require switch from mirrorlist to baseurl * implement DNF_CONTENTDIR swap as post-install action before reboot/login * temp disable _staging_repos_enable * incomplete fix for _graphical_wait_login - get_release_number is used heavily in our openQA but makes no sense in Rocky. Multiple possible solutions but this one allows `_graphical_wait_login` to pass. NEEDS_WORK
2022-07-10 21:05:04 +00:00
"DESKTOP": "false",
"PACKAGE_SET": "server"
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
}
},
"install_package_set_graphical-server": {
"profiles": {
Resolve conflicts due merge #219
2024-07-24 13:57:02 +00:00
"rocky-package-set-aarch64-*-aarch64": 30,
Reapply bios to uefi changes
2024-07-25 07:17:56 +00:00
"rocky-package-set-x86_64-*-uefi": 30
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
},
"settings": {
"DESKTOP": "gnome",
FEATURE: Add `DNF_CONTENTDIR` override support (#119) * add dnf_contentdir library function and implement is sample tests * Short circuit auto addition of _console_wait_login for tests without DESKTOP * support use of REPOSITORY_GRAPHICAL and ADD_REPOSITORY_GRAPHICAL test variables * deprecate addition of dnf_contentdir lib function * create and use get_version_major utility function * resolve mismatch of login type caused by incorrect template entries * add and use _staging_repos_enable post-install test * add install_package_set_* tests only to package-set flavor * fix variable re-declaration warning/error * add rocky-getting-started-tour needles * release rocky-repos content require switch from mirrorlist to baseurl * implement DNF_CONTENTDIR swap as post-install action before reboot/login * temp disable _staging_repos_enable * incomplete fix for _graphical_wait_login - get_release_number is used heavily in our openQA but makes no sense in Rocky. Multiple possible solutions but this one allows `_graphical_wait_login` to pass. NEEDS_WORK
2022-07-10 21:05:04 +00:00
"PACKAGE_SET": "graphical-server"
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
}
},
"install_package_set_workstation": {
"profiles": {
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-package-set-x86_64-*-uefi": 30
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
},
"settings": {
"DESKTOP": "gnome",
FEATURE: Add `DNF_CONTENTDIR` override support (#119) * add dnf_contentdir library function and implement is sample tests * Short circuit auto addition of _console_wait_login for tests without DESKTOP * support use of REPOSITORY_GRAPHICAL and ADD_REPOSITORY_GRAPHICAL test variables * deprecate addition of dnf_contentdir lib function * create and use get_version_major utility function * resolve mismatch of login type caused by incorrect template entries * add and use _staging_repos_enable post-install test * add install_package_set_* tests only to package-set flavor * fix variable re-declaration warning/error * add rocky-getting-started-tour needles * release rocky-repos content require switch from mirrorlist to baseurl * implement DNF_CONTENTDIR swap as post-install action before reboot/login * temp disable _staging_repos_enable * incomplete fix for _graphical_wait_login - get_release_number is used heavily in our openQA but makes no sense in Rocky. Multiple possible solutions but this one allows `_graphical_wait_login` to pass. NEEDS_WORK
2022-07-10 21:05:04 +00:00
"PACKAGE_SET": "workstation"
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
}
},
"install_package_set_virtualization-host": {
"profiles": {
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-package-set-x86_64-*-uefi": 30
Needles for `_graphical_wait_login` allowing English language Gnome environments to Getting Started (#49) * add needles for _graphical_wait_login * remove install_package_set_kde * add new test suites and job group to simplify package_set testing * modify _software_selection for pre-selected graphical-server case * restore non-Gnome installs to package-set test suite
2021-09-30 02:18:45 +00:00
},
"settings": {
FEATURE: Add `DNF_CONTENTDIR` override support (#119) * add dnf_contentdir library function and implement is sample tests * Short circuit auto addition of _console_wait_login for tests without DESKTOP * support use of REPOSITORY_GRAPHICAL and ADD_REPOSITORY_GRAPHICAL test variables * deprecate addition of dnf_contentdir lib function * create and use get_version_major utility function * resolve mismatch of login type caused by incorrect template entries * add and use _staging_repos_enable post-install test * add install_package_set_* tests only to package-set flavor * fix variable re-declaration warning/error * add rocky-getting-started-tour needles * release rocky-repos content require switch from mirrorlist to baseurl * implement DNF_CONTENTDIR swap as post-install action before reboot/login * temp disable _staging_repos_enable * incomplete fix for _graphical_wait_login - get_release_number is used heavily in our openQA but makes no sense in Rocky. Multiple possible solutions but this one allows `_graphical_wait_login` to pass. NEEDS_WORK
2022-07-10 21:05:04 +00:00
"DESKTOP": "false",
"PACKAGE_SET": "virtualization-host"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_pxeboot": {
"profiles": {
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-uefi": 30,
"rocky-universal-x86_64-*-bios": 31
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"+ISO": "",
"DELAYED_START": "1",
"KICKSTART": "1",
"NICTYPE": "tap",
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"PARALLEL_WITH": "support_server@bios",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"PXEBOOT": "once",
"ROOT_PASSWORD": "111111",
"TEST_TARGET": "COMPOSE",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"install_repository_http_graphical": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"REPOSITORY_GRAPHICAL": "%LOCATION%",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_repository_http_variation": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"REPOSITORY_VARIATION": "%LOCATION%",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"install_repository_nfs_graphical": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 30,
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"INSTALL_UNLOCK": "support_ready",
"NICTYPE": "tap",
"PARALLEL_WITH": "support_server",
"REPOSITORY_GRAPHICAL": "nfs:nfsvers=4:172.16.2.110:/repo",
"WORKER_CLASS": "tap"
}
},
"install_repository_nfs_variation": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"INSTALL_UNLOCK": "support_ready",
"NICTYPE": "tap",
"PARALLEL_WITH": "support_server",
"REPOSITORY_VARIATION": "nfs:nfsvers=4:172.16.2.110:/repo",
"WORKER_CLASS": "tap"
}
},
"install_repository_nfsiso_variation": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"INSTALL_UNLOCK": "support_ready",
"NICTYPE": "tap",
"PARALLEL_WITH": "support_server",
"REPOSITORY_VARIATION": "nfs:nfsvers=4:172.16.2.110:/iso/image.iso",
"WORKER_CLASS": "tap"
}
},
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"install_rescue_encrypted": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 31,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 31,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 31,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 32,
"rocky-universal-x86_64-*-uefi": 31
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"BOOTFROM": "d",
"ENTRYPOINT": "rescue_mode_encrypted",
"HDD_1": "disk_%MACHINE%_encrypted.qcow2",
"START_AFTER_TEST": "install_simple_encrypted"
}
},
"install_sata": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 20,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 21,
"rocky-universal-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"ATACONTROLLER": "ich9-ahci",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"HDDMODEL": "ide-hd,bus=ahci0.0",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_scsi_updates_img": {
"profiles": {
Provide tests for SIG/HPC slurm packages This MR provides a very, very basic test suite for the Slurm packages built by the HPC SIG. It checks the following: - Necessary packages for a single-node Slurm instance install successfully from the SIG/HPC repository - A job can be scheduled and executed to completion - A job can be scheduled and then cancelled ``` ./fifloader.py --clean --load templates.fif.json openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.8 CURRREL=8 BUILD=-${date +%Y%d%m}.0-slurm-8.8 TEST=slurm22,slurm23 openqa-cli api -X POST isos ISO=Rocky-9.2-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=9.2 CURRREL=9 BUILD=-${date +%Y%d%m}.0-slurm-9.2 TEST=slurm22,slurm23 ``` - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] Any dependent changes have been merged and published in downstream modules
2023-07-25 20:04:07 +00:00
"rocky-universal-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-universal-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"CDMODEL": "scsi-cd",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"GRUB": "inst.updates=https://fedorapeople.org/groups/qa/updates/updates-openqa.img",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"HDDMODEL": "scsi-hd",
"SCSICONTROLLER": "virtio-scsi-pci",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"TEST_UPDATES": "1",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_serial_console": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 30,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-universal-aarch64-*-aarch64": 30
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"ANACONDA_TEXT": "1",
"NO_UEFI_POST": "1",
"SERIAL_CONSOLE": "1",
"VIRTIO_CONSOLE_NUM": "2"
}
},
"install_shrink_ext4": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Device root resize changes
2024-07-30 15:00:46 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"HDD_1": "disk_shrink_ext4.img",
"PARTITIONING": "guided_shrink",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_shrink_ntfs": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Device root resize changes
2024-07-30 15:00:46 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"HDD_1": "disk_shrink_ntfs.img",
"PARTITIONING": "guided_shrink",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_simple_encrypted": {
"profiles": {
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 31,
"rocky-universal-x86_64-*-uefi": 30
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"ENCRYPT_PASSWORD": "weakpassword",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"STORE_HDD_1": "disk_%MACHINE%_encrypted.qcow2",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_simple_free_space": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 30,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 31,
"rocky-universal-x86_64-*-uefi": 30
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"HDD_1": "disk_freespace_%PART_TABLE_TYPE%.img",
8.6 release fixes (#92) * Handle the "reclaim space" dialog Adds handling for the "Reclaim Space" dialog, which can appear after the user clicks "Done" in the partitioning spoke. * Fix indentations * Set default HDD size to 15GB * Remove redundant HDDSIZEGB definitions * Add more GiBs * Workaround for #82 * Needle with new security policy spoke icon * Add new needles to fix cockpit tests in 8.6 * Add contribution SOP to README * Words * Script fixes (#99) * Increment version * Fix this header * Fix URL for updates.img (#98) * --- title: [8.6 Release Issues] Test Suite: install_delete_partial and install_custom_gui_lvm_ext4 on rocky 8.6 labels: 'test suite' assignees: '@akatch' --- # Description Running openQA test suite `install_delete_partial` as above throws `Test died: no candidate needle with tag(s) 'anaconda_install_destination_reclaim_space_btn' matched` at module `disk_guided_delete_partial`. At this stage, the "Reclaim Space" button in the lower right corner of the dialog is disabled. Additionally, the dialog shows that 5GB will be reclaimed by the steps taken to that point in the test, but installation requires around 9GB. Do we need to reclaim enough space for installation in order to enable that button? _Yes, the button is enabled when enough space to install is reclaimed._ Just adding HDDSIZEGB=20 to `templates.fif.json` did not increase volume size shown in the dialog. Do we need to recreate the img file? _Yes, recreating the img file using createhdds.py against a larger size in hdds.json resolved this error._ The Reclaim Space dialog claimed 9.06GB was required to perform installation, and after doubling the size of disk_full_XXX.img we got past the Reclaim Space dialog. However, `_do_install_and_reboot` failed to install citing not enough disk space. Fixes #80 when merged. # How Has This Been Tested? ``` # NOTE: was not able to reproduce for install_custom_gui_lvm_ext4 openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.6 BUILD=8.6_dvd-iso_$(date +%Y%m%d.%H%M%S).0 TEST=install_custom_gui_lvm_ext4 PACKAGE_SET=graphical-server openqa-cli api -X POST isos ISO=Rocky-8.6-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.6 BUILD=8.6_universal_$(date +%Y%m%d.%H%M%S).0 TEST=install_delete_partial PACKAGE_SET=graphical-server ``` All tests must pass `_do_install_and_reboot`. NOTE: These tests will fail at `_console_wait_login` with the issue in #81. # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] Any dependent changes have been merged and published in downstream modules * Add new needle to mitigate the changed default for install source on the network from http to https Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-06-09 23:15:17 +00:00
"HDDSIZEGB": "20",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"PARTITIONING": "guided_free_space",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
"install_software_raid": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 30,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 31,
"rocky-universal-x86_64-*-uefi": 30
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"NUMDISKS": "2",
"PARTITIONING": "custom_software_raid",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"install_updates_nfs": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 40
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"GRUB": "inst.stage2=nfs:nfsvers=4:172.16.2.110:/repo",
"INSTALL_UNLOCK": "support_ready",
"NICTYPE": "tap",
"PARALLEL_WITH": "support_server",
"QEMURAM": "3072",
"TEST_UPDATES": "1",
"WORKER_CLASS": "tap"
}
},
"install_vnc_client": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 40
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"DESKTOP": "gnome",
Some image pointer corrections
2022-01-30 15:49:16 +00:00
"HDD_1": "disk_rocky%CURRREL%_desktop_%ARCH%.qcow2",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"INSTALL": "1",
"NICTYPE": "tap",
"PARALLEL_WITH": "install_vnc_server",
"PREINSTALL": "_vnc_client_connect_pre _graphical_wait_login _vnc_client_connect",
"VNC_CLIENT": "1",
"WORKER_CLASS": "tap"
}
},
"install_vnc_server": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 40
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"GRUB": "inst.vnc net.ifnames=0 biosdevname=0 ip=172.16.2.114::172.16.2.2:255.255.255.0:vnc001.test.openqa.rockylinux.org:eth0:off",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"NICTYPE": "tap",
"VNC_SERVER": "1",
"WORKER_CLASS": "tap"
}
},
"install_vncconnect_client": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 40
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"DESKTOP": "gnome",
Some image pointer corrections
2022-01-30 15:49:16 +00:00
"HDD_1": "disk_rocky%CURRREL%_desktop_%ARCH%.qcow2",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"INSTALL": "1",
"NICTYPE": "tap",
"PREINSTALL": "_vncconnect_client_setup_pre _graphical_wait_login _vncconnect_client_setup",
"VNC_CLIENT": "1",
"WORKER_CLASS": "tap"
}
},
"install_vncconnect_server": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 40
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"GRUB": "inst.vnc inst.vncconnect=172.16.2.117:5500 net.ifnames=0 biosdevname=0 ip=172.16.2.116::172.16.2.2:255.255.255.0:vnc003.test.openqa.rockylinux.org:eth0:off",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"INSTALL_UNLOCK": "vncconnect_client_ready",
"NICTYPE": "tap",
"PARALLEL_WITH": "install_vncconnect_client",
"VNC_SERVER": "1",
"WORKER_CLASS": "tap"
}
},
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"install_xfs": {
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 40,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-universal-x86_64-*-bios": 41,
"rocky-universal-x86_64-*-uefi": 40
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"PARTITIONING": "custom_xfs",
Add minimal and desktop false to all incorrect tests in universal (#125) Co-authored-by: lumarel <lumarel@users.noreply.github.com>
2022-07-23 04:29:05 +00:00
"ROOT_PASSWORD": "weakpassword",
"PACKAGE_SET": "minimal",
"DESKTOP": "false"
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"memtest": {
Add QA:Testcase_Clevis test (TPM-based automatic decryption) This adds a test that automates https://fedoraproject.org/wiki/QA:Testcase_Clevis. It requires os-autoinst-4.6-18.20200623git5038d8c or newer, and a worker host in the 'tpm' class which is set up to have an instance of swtpm running at /tmp/mytpmX , where X is the worker instance number, for each worker. The Fedora infrastructure ansible plays have been updated to handle this via an instantiated systemd service, which other instances can also adopt. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-06-19 21:14:57 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-universal-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-universal-ppc64le-*-ppc64le": 30,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-universal-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-universal-x86_64-*-bios": 30
Add QA:Testcase_Clevis test (TPM-based automatic decryption) This adds a test that automates https://fedoraproject.org/wiki/QA:Testcase_Clevis. It requires os-autoinst-4.6-18.20200623git5038d8c or newer, and a worker host in the 'tpm' class which is set up to have an instance of swtpm running at /tmp/mytpmX , where X is the worker instance number, for each worker. The Fedora infrastructure ansible plays have been updated to handle this via an instantiated systemd service, which other instances can also adopt. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-06-19 21:14:57 +00:00
},
"settings": {
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"ENTRYPOINT": "memtest"
Add QA:Testcase_Clevis test (TPM-based automatic decryption) This adds a test that automates https://fedoraproject.org/wiki/QA:Testcase_Clevis. It requires os-autoinst-4.6-18.20200623git5038d8c or newer, and a worker host in the 'tpm' class which is set up to have an instance of swtpm running at /tmp/mytpmX , where X is the worker instance number, for each worker. The Fedora infrastructure ansible plays have been updated to handle this via an instantiated systemd service, which other instances can also adopt. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-06-19 21:14:57 +00:00
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"modularity_tests": {
Create test for IoT Greenboot. Finish test and add necessary needles. Create IOT needle directory and move needles in it. Delete needle as required by the review. Add to templates.
2020-05-27 12:49:22 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 30,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 30,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 30
Create test for IoT Greenboot. Finish test and add necessary needles. Create IOT needle directory and move needles in it. Delete needle as required by the review. Add to templates.
2020-05-27 12:49:22 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
Create test for IoT Greenboot. Finish test and add necessary needles. Create IOT needle directory and move needles in it. Delete needle as required by the review. Add to templates.
2020-05-27 12:49:22 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"POSTINSTALL": "modularity_module_list modularity_enable_disable_module modularity_install_module",
Create test for IoT Greenboot. Finish test and add necessary needles. Create IOT needle directory and move needles in it. Delete needle as required by the review. Add to templates.
2020-05-27 12:49:22 +00:00
"ROOT_PASSWORD": "weakpassword",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false"
Create test for IoT Greenboot. Finish test and add necessary needles. Create IOT needle directory and move needles in it. Delete needle as required by the review. Add to templates.
2020-05-27 12:49:22 +00:00
}
},
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"realmd_join_cockpit": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"+HDD_1": "disk_%MACHINE%_cockpit.qcow2",
"+START_AFTER_TEST": "server_cockpit_default",
"BOOTFROM": "c",
"NICTYPE": "tap",
"PARALLEL_WITH": "server_role_deploy_domain_controller",
"POSTINSTALL": "realmd_join_cockpit freeipa_webui freeipa_password_change freeipa_client",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.102 client002.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"realmd_join_sssd": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_WITH": "server_role_deploy_domain_controller",
"POSTINSTALL": "realmd_join_sssd freeipa_client",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.103 client003.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"release_identification": {
Automate the IoT rpm-ostree package layering test case.
2020-05-28 12:43:52 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 40,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 40,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 40,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 40
Add QA:Testcase_RpmOstree_Rebase for iot testing (#167) Signed-off-by: Paul Whalen <pwhalen@fedoraproject.org>
2020-06-04 18:00:32 +00:00
},
"settings": {
"BOOTFROM": "c",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"ENTRYPOINT": "text_login_gui rocky_release os_release",
Add QA:Testcase_RpmOstree_Rebase for iot testing (#167) Signed-off-by: Paul Whalen <pwhalen@fedoraproject.org>
2020-06-04 18:00:32 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add QA:Testcase_RpmOstree_Rebase for iot testing (#167) Signed-off-by: Paul Whalen <pwhalen@fedoraproject.org>
2020-06-04 18:00:32 +00:00
"USER_LOGIN": "false"
}
},
Add secure_boot_fallback test
2024-07-05 15:23:51 +00:00
"secure_boot_fallback": {
"profiles": {
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 10
Add secure_boot_fallback test
2024-07-05 15:23:51 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "_secure_boot_fallback",
"ROOT_PASSWORD": "weakpassword",
"+START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false"
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"server_cockpit_basic": {
"profiles": {
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 30
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-15 21:56:32 +00:00
},
"settings": {
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"+HDD_1": "disk_%MACHINE%_cockpit.qcow2",
"+START_AFTER_TEST": "server_cockpit_default",
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-15 21:56:32 +00:00
"BOOTFROM": "c",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"POSTINSTALL": "server_cockpit_basic",
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-15 21:56:32 +00:00
"ROOT_PASSWORD": "weakpassword",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"USER_LOGIN": "false"
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-15 21:56:32 +00:00
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"server_cockpit_default": {
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-15 21:56:32 +00:00
"profiles": {
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-15 21:56:32 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "_setup_browser server_cockpit_default",
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-15 21:56:32 +00:00
"ROOT_PASSWORD": "weakpassword",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"STORE_HDD_1": "disk_%MACHINE%_cockpit.qcow2",
"USER_LOGIN": "false"
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our *own* Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-07-15 21:56:32 +00:00
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"server_cockpit_updates": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"profiles": {
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 30
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"+HDD_1": "disk_%MACHINE%_cockpit.qcow2",
"+START_AFTER_TEST": "server_cockpit_default",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"BOOTFROM": "c",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"POSTINSTALL": "server_cockpit_updates server_cockpit_autoupdate",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"ROOT_PASSWORD": "weakpassword",
"USER_LOGIN": "false"
}
},
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"server_database_client": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_WITH": "server_role_deploy_database_server",
"POSTINSTALL": "database_client",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.105 dbclient.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"server_filesystem_default": {
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"BOOTFROM": "c",
Specify DESKTOP=gnome for installs with a GUI
2022-10-16 04:20:02 +00:00
"DESKTOP": "gnome",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "server_filesystem_default",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"ROOT_PASSWORD": "weakpassword",
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"USER_LOGIN": "false"
}
},
vastly decrease scope of configuration
2021-08-09 10:04:29 +00:00
"server_firewall_default": {
Re-enable memory_check test (on Everything, with WS packages) We were only running this test on the Workstation boot ISO... then that was removed, and so we actually never ran this test at all any more. We should run it on at least one image as check- compose uses the output to check whether installer memory usage has increased. I initially ran it on Workstation as that installs the most packages; so let's run it on Everything but use the Workstation package set. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-25 15:11:17 +00:00
"profiles": {
add s390x machine, product(s) and assign test suites
2024-01-24 05:25:49 +00:00
"rocky-dvd-iso-s390x-*-s390x": 20,
add ppc64le machine, product(s) and assign test suites
2024-01-24 05:24:13 +00:00
"rocky-dvd-iso-ppc64le-*-ppc64le": 20,
Add aarch64 to templates (#41) * Add aarch64 to templates * Fix _do_install_and_reboot on aarch64 On aarch64 the _do_install_and_reboot test runs the "consoletty0" action, which has a command with the string "fedora". This causes the command to fail with "No such file or directory". This patch changes "fedora" to "rocky" to which allows _do_install_and_reboot to pass.
2021-10-07 21:26:42 +00:00
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "server_firewall_default",
Unify base tests across normal, Cloud and arm We have variant versions of several of the base tests which exist to account for differences in required variable settings to run essentially the same test in different situations. By twiddling the variables a little, including inventing a new variable defined in the flavors and substituted into the test suites so the same test suite can have a different START_AFTER_TEST when run on different flavors, I think we can unite them all and make this a lot simpler. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-10-30 22:21:49 +00:00
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
"USER_LOGIN": "false"
}
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"server_freeipa_replication_client": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"FREEIPA_REPLICA_CLIENT": "1",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_WITH": "server_freeipa_replication_replica",
"POSTINSTALL": "realmd_join_sssd freeipa_client",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.108 client005.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"server_freeipa_replication_master": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"FREEIPA_REPLICA_MASTER": "1",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_CANCEL_WHOLE_CLUSTER": "0",
"POSTINSTALL": "role_deploy_domain_controller role_deploy_domain_controller_check",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.106 ipa002.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"server_freeipa_replication_replica": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 30,
Correction of inconsistensies in priority.
2024-07-24 10:36:06 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 30
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"FREEIPA_REPLICA": "1",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_CANCEL_WHOLE_CLUSTER": "0",
"PARALLEL_WITH": "server_freeipa_replication_master",
"POSTINSTALL": "realmd_join_sssd",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.107 ipa003.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"server_realmd_join_kickstart": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"GRUB": "inst.ks=hd:vdb1:/freeipaclient.ks",
Supporting fix for createhdds#11
2022-09-15 22:07:47 +00:00
"HDD_2": "disk_ks-%CURRREL%.img",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"INSTALL_UNLOCK": "freeipa_ready",
"KICKSTART": "1",
"NICTYPE": "tap",
"NUMDISKS": "2",
"PARALLEL_WITH": "server_role_deploy_domain_controller",
"POSTINSTALL": "freeipa_client",
"ROOT_PASSWORD": "anaconda",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"server_remote_logging_client": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_WITH": "server_remote_logging_server",
"POSTINSTALL": "server_remote_logging_client",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.113 rsyslogclient.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"server_remote_logging_server": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_CANCEL_WHOLE_CLUSTER": "0",
"POSTINSTALL": "server_remote_logging_server",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.112 rsyslogserver.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"server_role_deploy_database_server": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_CANCEL_WHOLE_CLUSTER": "0",
"POSTINSTALL": "role_deploy_database_server",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.104 db.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
"server_role_deploy_domain_controller": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 20,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 20
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"NICTYPE": "tap",
"PARALLEL_CANCEL_WHOLE_CLUSTER": "0",
"POSTINSTALL": "role_deploy_domain_controller role_deploy_domain_controller_check",
replace fedoraproject.org with rockylinux.org - refs in templates.fif.json and code changed (typically hostnames in multi-worker tests) - refs in documentation left for historical / context purposes
2023-03-17 17:04:54 +00:00
"POST_STATIC": "172.16.2.100 ipa001.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
},
Provide tests for SIG/HPC slurm packages This MR provides a very, very basic test suite for the Slurm packages built by the HPC SIG. It checks the following: - Necessary packages for a single-node Slurm instance install successfully from the SIG/HPC repository - A job can be scheduled and executed to completion - A job can be scheduled and then cancelled ``` ./fifloader.py --clean --load templates.fif.json openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.8 CURRREL=8 BUILD=-${date +%Y%d%m}.0-slurm-8.8 TEST=slurm22,slurm23 openqa-cli api -X POST isos ISO=Rocky-9.2-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=9.2 CURRREL=9 BUILD=-${date +%Y%d%m}.0-slurm-9.2 TEST=slurm22,slurm23 ``` - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] Any dependent changes have been merged and published in downstream modules
2023-07-25 20:04:07 +00:00
"slurm22": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 10,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 10
Provide tests for SIG/HPC slurm packages This MR provides a very, very basic test suite for the Slurm packages built by the HPC SIG. It checks the following: - Necessary packages for a single-node Slurm instance install successfully from the SIG/HPC repository - A job can be scheduled and executed to completion - A job can be scheduled and then cancelled ``` ./fifloader.py --clean --load templates.fif.json openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.8 CURRREL=8 BUILD=-${date +%Y%d%m}.0-slurm-8.8 TEST=slurm22,slurm23 openqa-cli api -X POST isos ISO=Rocky-9.2-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=9.2 CURRREL=9 BUILD=-${date +%Y%d%m}.0-slurm-9.2 TEST=slurm22,slurm23 ``` - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] Any dependent changes have been merged and published in downstream modules
2023-07-25 20:04:07 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "slurm",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"ROOT_PASSWORD": "weakpassword",
"USER_LOGIN": "false",
"SLURM_VERSION": "22"
}
},
"slurm23": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 10,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 10
Provide tests for SIG/HPC slurm packages This MR provides a very, very basic test suite for the Slurm packages built by the HPC SIG. It checks the following: - Necessary packages for a single-node Slurm instance install successfully from the SIG/HPC repository - A job can be scheduled and executed to completion - A job can be scheduled and then cancelled ``` ./fifloader.py --clean --load templates.fif.json openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=8.8 CURRREL=8 BUILD=-${date +%Y%d%m}.0-slurm-8.8 TEST=slurm22,slurm23 openqa-cli api -X POST isos ISO=Rocky-9.2-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=dvd-iso VERSION=9.2 CURRREL=9 BUILD=-${date +%Y%d%m}.0-slurm-9.2 TEST=slurm22,slurm23 ``` - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] Any dependent changes have been merged and published in downstream modules
2023-07-25 20:04:07 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "slurm",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"ROOT_PASSWORD": "weakpassword",
"USER_LOGIN": "false",
"SLURM_VERSION": "23"
}
},
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"support_server": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 10,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-dvd-iso-x86_64-*-bios": 10,
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"rocky-universal-aarch64-*-aarch64": 10,
Adopt uefi secure boot as standard test basis
2024-07-18 09:56:34 +00:00
"rocky-universal-x86_64-*-bios": 10
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
},
"settings": {
"BOOTFROM": "c",
Some image pointer corrections
2022-01-30 15:49:16 +00:00
"HDD_1": "disk_rocky%CURRREL%_support_%ARCH%.qcow2",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"NICTYPE": "tap",
"NUMDISKS": "2",
"PARALLEL_CANCEL_WHOLE_CLUSTER": "0",
"POSTINSTALL": "_support_server",
use domain configured for dnsmasq in support server
2022-02-19 03:10:14 +00:00
"POST_STATIC": "172.16.2.110 support.test.openqa.rockylinux.org",
Adding most of the inter server tests back
2022-01-30 13:50:42 +00:00
"ROOT_PASSWORD": "weakpassword",
"TEST_TARGET": "NONE",
"USER_LOGIN": "false",
"WORKER_CLASS": "tap"
}
Add toolbox test as POC
2024-02-09 00:21:57 +00:00
},
"toolbox": {
"profiles": {
"rocky-dvd-iso-aarch64-*-aarch64": 10,
Adopt uefi secure boot as standard
2024-07-13 13:17:09 +00:00
"rocky-dvd-iso-x86_64-*-uefi": 10
Add toolbox test as POC
2024-02-09 00:21:57 +00:00
},
"settings": {
"BOOTFROM": "c",
"HDD_1": "disk_%FLAVOR%_%MACHINE%.qcow2",
"POSTINSTALL": "toolbox",
"START_AFTER_TEST": "%DEPLOY_UPLOAD_TEST%",
"ROOT_PASSWORD": "weakpassword",
"USER_LOGIN": "false"
}
Add a whole intermediate template format ('FIF') and tools I and @lruzicka (and I think @jskladan and @jsedlak and @michelmno and everyone else who's ever touched it...) are being gradually driven nuts by manually editing the test templates. The bigger the files get the more awkward it is to keep them straight and be sure we're doing it right. Upstream doesn't do things the same way we do (they mostly edit in the web UI and dump to file for the record), but we do still think making changes in the repo and posting to the web UI is the right way around to do it, we just wish the format was saner. Upstream has actually recently introduced a YAML-based approach to storing job templates which tries to condense things a bit, and you can dump to that format with dump-templates --json, but @lruzicka and I agree that that format is barely better for hand editing in a text editor than the older one our templates currently use. So, this commit introduces...Fedora Intermediate Format (FIF) - an alternative format for representing job templates - and some tools for working with it. It also contains our existing templates in this new format, and removes the old template files. The format is documented in the docstrings of the tools, but briefly, it keeps Machines, Products and TestSuites but improves their format a bit (by turning dicts-of-lists into dicts-of- dicts), and adds Profiles, which are combinations of Machines and Products. TestSuites can indicate which Profiles they should be run on. The intermediate format converter (`fifconverter`) converts existing template data (in JSON format; use tojson.pm to convert our perl templates to JSON) to the intermediate format and writes it out. As this was really intended only for one-time use (the idea is that after one-time conversion, we will edit the templates in the intermediate format from now on), its operation is hardcoded and relies on specific filenames. The intermediate format loader (`fifloader`) generates JobTemplates from the TestSuites and Profiles, reverses the quality-of-life improvements of the intermediate format, and produces template data compatible with the upstream loader, then can write it to disk and/or call the upstream loader directly. The check script (`fifcheck`) runs existing template data through both the converter and the loader, then checks that the result is equivalent to the input. Again this was mostly written for one- time use so is fairly rough and hard-coded, but I'm including it in the commit so others can check the work and so on. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-23 14:20:10 +00:00
}
}
Re-enable memory_check test (on Everything, with WS packages) We were only running this test on the Workstation boot ISO... then that was removed, and so we actually never ran this test at all any more. We should run it on at least one image as check- compose uses the output to check whether installer memory usage has increased. I initially ran it on Workstation as that installs the most packages; so let's run it on Everything but use the Workstation package set. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-25 15:11:17 +00:00
}
Reference in New Issue Copy Permalink