openqa-cli POST Examples¶
This page will provide a brief overview of some basic
System / Access Requirements¶
To complete any of the examples please complete the API
POST Access steps outlined in the openQA - Access document.
POST can be used for any of the default test suites for the various Rocky Linux media that are made available. The following examples show some of these standard
POSTs that are commonly used by our team and will be used to demonstrate how some minor variations.
POST is the most basic, simply providing the minimal set of variables required to trigger the standard test suite for the Rocky Linux 9.1 boot ISO on openqa workers for the
x86_64 architecture. All tests of the test suite are predetermined and configure on the openQA server. Since the boot ISO doesn't contain any packages this test suite is effectively a network install from standard Rocky Linux repository servers and/or mirrors.
$ openqa-cli api -X POST isos ISO=Rocky-9.1-x86_64-boot.iso ARCH=x86_64 \ DISTRI=rocky FLAVOR=boot-iso VERSION=9.1 CURRREL=9 BUILD=20230409-Rocky-9.1-x86_64.0
POST demonstrates how a different media type, in this case the minimal ISO, for an alternate Rocky Linux version, in this case Rocky Linux 8.7, can be triggered. As can be seen by this and the previous
BUILD variable will typically be designate the date, version and architecture of the test suite. Since the minimal ISO contains all packages required to conduct a minimal install of Rocky Linux that is the behavior of this test suite.
$ openqa-cli api -X POST isos ISO=Rocky-8.7-x86_64-minimal.iso ARCH=x86_64 \ DISTRI=rocky FLAVOR=minimal-iso VERSION=8.7 CURRREL=8 BUILD=20230409-Rocky-8.7-x86_64.0
POST demonstrates specification of the final normal media type, the dvd ISO, along with what is called a
FLAVOR, in this case
package-set for the
x86_64 architecture and Rocky Linux 9.1. Since the dvd ISO contains all of the packages available at release of a specific version or Rocky Linux the
package-set test suite will test installation of all primary installation types of Rocky Linux not included in the
minimal-iso test suite above.
$ openqa-cli api -X POST isos ISO=Rocky-9.1-20221214.1-x86_64-dvd.iso ARCH=x86_64 \ DISTRI=rocky FLAVOR=package-set VERSION=9.1 CURRREL=9 BUILD=20230409-Rocky-9.1-x86_64.0
These three test suites provide for the minimal testing of all ISOs produced for a given release of Rocky Linux.
In addition to the Basic POSTs described above there are additional default test suites that use the dvd ISO media and include substantially more test cases. Those include:
- installing in graphical, text and serial console
- installation for standard BIOS and UEFI
- validation of the Anaconda help system
- disk layout variations including LVM, RAID, partition shrink and/or grow, iSCSI and LUKS
- PXE installation from various network sources
- installation in various languages
POSTs for these test suites is very similar to the basic POSTs above and are shown below...
$ openqa-cli api -X POST isos ISO=Rocky-9.1-20221214.1-x86_64-dvd.iso ARCH=x86_64 \ DISTRI=rocky FLAVOR=dvd-iso VERSION=9.1 CURRREL=9 BUILD=20230409-Rocky-9.1-x86_64.0
$ openqa-cli api -X POST isos ISO=Rocky-9.1-20221214.1-x86_64-dvd.iso ARCH=x86_64 \ DISTRI=rocky FLAVOR=universal VERSION=9.1 CURRREL=9 BUILD=20230409-Rocky-9.1-x86_64.0
Collection of test suites by BUILD¶
A feature of openQA is that for a given job group test suites which use the same
BUILD identifier are collected into a single view in the web UI.
Thus, the examples show above which all use
BUILD=20230409-Rocky-9.1-x86_64.0 are all shown in a single view. Additionally, that view is accessible via a predictable URI, for example
https://openqa.rockylinux.org/tests/overview?build=20230409-Rocky-9.1-x86_64.0 as shown below...
If you have questions with respect to this content or to report concerns regarding the use or misuse content please do not hesitate to contact us at firstname.lastname@example.org.
Rocky Linux and the Rocky Enterprise Software Foundation (RESF) does not make any express or implied warranties, including but not limited to the warranties of non-infringement of any third party intellectual property rights. RESF does not warrant that any pending trademark applications for trademarks of RESF will result in any granted trademark protection. RESF shall not be liable for any claims relating to user's activities falling within the scope of the permission and user hereby agrees to indemnify, defend and hold RESF and its contributors harmless against any such claim.
This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.