{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Testing Team Wiki","text":""},{"location":"#links","title":"Links","text":""},{"location":"#responsibilities","title":"Responsibilities","text":"

The Testing Team handles testing and QA for Rocky Linux.

"},{"location":"#meetings-communications","title":"Meetings / Communications","text":""},{"location":"#members","title":"Members","text":"

For a list of our members, see the Members page.

Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"members/","title":"Members","text":"Role Name Email Mattermost Name IRC Name Testing Lead Chris Stackpole stack@rockylinux.org @stack Testing Team Al Bowles @raktajino raktajino Testing Team Trevor Cooper tcooper@rockylinux.org @tcooper Testing Team Lukas Magauer lukas@magauer.eu @lumarel Testing Team Alan Marshall @alangm alangm Testing Team Rich Alloway @ralloway Testing Team Anthony Navarro @anavarro10 Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"documentation/","title":"Documentation","text":"

This section goes over various Documentation for the Testing team. Please use the menu items to find the various pages of interest.

Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"documentation/qa_test_cases/","title":"QA:Test Cases","text":"

This page lists all test cases in work and who is working on them...

"},{"location":"documentation/qa_test_cases/#initialization-requirements","title":"Initialization Requirements","text":"Requirement Test Case Assignee Status Release-blocking images must bootRocky Linux 8 Rocky Linux 9 QA:Testcase Boot Methods Boot ISO @tcooper template exists, openQA covered (ref) Release-blocking images must bootRocky Linux 8 Rocky Linux 9 QA:Testcase Boot Methods DVD @tcooper template exists, openQA covered (ref) Basic Graphics Mode behaviorsRocky Linux 8 QA:Testcase Basic Graphics Mode @tcooper openQA TestCase VNC Graphics Mode behaviorsRocky Linux 9 QA:Testcase VNC Graphics Mode @tcooper openQA TestCase No Broken PackagesRocky Linux 8 Rocky Linux 9 QA:Testcase Media RepoclosureQA:Testcase Media File Conflicts @tcooper manual using scripts or automated in CI Repositories Must Match UpstreamRocky Linux 8 Rocky Linux 9 QA:Testcase repocompare @tcooper manual using Skip's repocompare DebrandingRocky Linux 8 Rocky Linux 9 QA:Testcase Debranding Analysis @tcooper manual using scripts or automated in CI"},{"location":"documentation/qa_test_cases/#installer-requirements","title":"Installer Requirements","text":"Requirement Test Case Assignee Status Media Consistency Verification QA:Testcase Media USB ddQA:Testcase Boot Methods Boot ISOQA:Testcase Boot Methods DVD @raktajino Packages and Installer Sources QA:Testcase Packages and Installer Sources @raktajino Implemented in openQA, document NAS (Network Attached Storage) QA:Testcase Network Attached Storage @raktajino Installation Interfaces QA:Testcase Installation Interfaces @raktajino Implemented in openQA, document Minimal Installation QA:Testcase Minimal Installation @raktajino Implemented in openQA, document Kickstart Installation QA:Testcase Kickstart Installation @raktajino Implemented in openQA, document Disk Layouts QA:Testcase Disk Layouts @raktajino Implemented in openQA, document Firmware RAID QA:Testcase Firmware RAID @raktajino Bootloader Disk Selection QA:Testcase Bootloader Disk Selection @raktajino Storage Volume Resize QA:Testcase Storage Volume Resize @raktajino Implemented in openQA, document Update Image QA:Testcase Update Image @raktajino Implemented in openQA, document Installer Help QA:Testcase Installer Help @raktajino Implemented in openQA, document Installer Translations QA:Testcase Installer Translations @raktajino Implemented in openQA, document"},{"location":"documentation/qa_test_cases/#cloud-image-requirements","title":"Cloud Image Requirements","text":"Requirement Test Case Assignee Status Images Published to Cloud Providers QA:Testcase TBD @tbd"},{"location":"documentation/qa_test_cases/#post-installation-requirements","title":"Post-Installation Requirements","text":"Requirement Test Case Assignee Status System Services QA:Testcase System Services @lumarel manual guide documented or needs new openQA testcase Keyboard Layout QA:Testcase Keyboard Layout @lumarel implemented in openQA SELinux Errors (Server) QA:Testcase SELinux Errors on Server @lumarel implemented in openQA SELinux and Crash Notifications (Desktop Only) QA:Testcase SELinux Errors on Desktop @lumarel partly implemented in openQA Default Application Functionality (Desktop Only) QA:Testcase Application Functionality @lumarel manual guide documented Default Panel Functionality (Desktop Only) QA:Testcase GNOME UI Functionality @lumarel implemented in openQA, additionally documented for manual inspection Dual Monitor Setup (Desktop Only) QA:Testcase Multimonitor Setup @lumarel manual guide documented Artwork and Assets (Server and Desktop) QA:Testcase Artwork and Assets @lumarel implemented in openQA, additionally documented for manual inspection Packages and Module Installation QA:Testcase Basic Package installsQA:Testcase Module Streams @lumarel partly implemented in openQA, manual guide documented Identity Management (FreeIPA) QA:Testcase Identity Management @lumarel manual guide documented, PR open for openQA implementation Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"documentation/QA/Testcase_Basic_Graphics_Mode/","title":"QA:Testcase Basic Graphics Mode","text":"

REFERENCED RELEASE CRITERIA IS OVERLY GENERAL AND UNTESTABLE

The associated release criteria, Release_Criteria#basic-graphics-mode-behaviors, for this test case is overly general and must be modified to specific enough to be testable.

Associated release criterion

This test case is associated with the Release_Criteria#basic-graphics-mode-behaviors release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Basic_Graphics_Mode/#description","title":"Description","text":"

This test case will verify that release-blocking installers function as intended using the generic video driver option (\u201cbasic graphics mode\u201d) on supported systems and classes of hardware.

Supported Systems and Hardware Classes x86_64aarch64ppc64s309x

TBD

TBD

TBD

TBD

"},{"location":"documentation/QA/Testcase_Basic_Graphics_Mode/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
"},{"location":"documentation/QA/Testcase_Basic_Graphics_Mode/#how-to-test","title":"How to test","text":"
  1. Boot the system from the prepared optical, USB media or virtual device attachment.
  2. In the boot menu select the appropriate option to boot the installer.
  3. In the installer select the appropriate option to intall in basic graphics mode.
  4. Proceed with installation on the test system.Depending on installer choices this MAY destroy all the data on the test system.

DATA LOSS

If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Basic_Graphics_Mode/#expected-results","title":"Expected Results","text":"
  1. Selection of basic graphics mode in the Anaconda installer is possible.
  2. Anaconda installer presents a usable graphical intallation environment.
  3. System under test can be installed normally.
  4. After reboot system boots into graphical environment.
  5. After login user is able to operate the graphical environment.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Boot_Methods_Boot_Iso/","title":"QA:Testcase Boot Methods Boot Iso","text":"

Associated release criterion

This test case is associated with the Release_Criteria#initialization-requirements release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Boot_Methods_Boot_Iso/#description","title":"Description","text":"

This is to verify that the Anaconda installer starts correctly when booting from the Rocky Linux boot.iso.

"},{"location":"documentation/QA/Testcase_Boot_Methods_Boot_Iso/#setup","title":"Setup","text":"
  1. Prepare your system for booting the boot.iso image. This may involve writing the image to a USB key or burning it to an optical disk. Additionally, attaching the boot.iso to a virtual machine instance as a Virtual Optical Disk or mounting the boot.iso to server via baseboard management controller virtual media attach should be possible but is not expressly required.
"},{"location":"documentation/QA/Testcase_Boot_Methods_Boot_Iso/#how-to-test","title":"How to test","text":"
  1. Boot the system from the prepared optical, USB media or virtual device attachment.
  2. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Boot_Methods_Boot_Iso/#expected-results","title":"Expected Results","text":"
  1. Graphical boot menu is displayed for users to select install options. Navigating the menu and selecting entries must work. If no option is selected, the installer should load after a reasonable timeout.
  2. System boots into the Anaconda installer.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Boot_Methods_Dvd/","title":"QA:Testcase Boot Methods DVD","text":"

Associated release criterion

This test case is associated with the Release_Criteria#initialization-requirements release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Boot_Methods_Dvd/#description","title":"Description","text":"

This is to verify that the Anaconda installer starts correctly when booting from DVD.iso.

"},{"location":"documentation/QA/Testcase_Boot_Methods_Dvd/#setup","title":"Setup","text":"
  1. Prepare your system for booting the DVD.iso image. This may involve writing the image to a USB key or burning it to an optical disk of sufficient capacity. Additionally, attaching the DVD.iso to a virtual machine instance as a Virtual Optical Disk or mounting the DVD.iso to server via baseboard management controller virtual media attach should be possible but is not expressly required.
"},{"location":"documentation/QA/Testcase_Boot_Methods_Dvd/#how-to-test","title":"How to test","text":"
  1. Boot the system from the prepared optical, USB media or virtual device attachment.
  2. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Boot_Methods_Dvd/#expected-results","title":"Expected Results","text":"
  1. Graphical boot menu is displayed for users to select install options. Navigating the menu and selecting entries must work. If no option is selected, the installer should load after a reasonable timeout.
  2. System boots into the Anaconda installer.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Bootloader_Disk_Selection/","title":"QA:Testcase Bootloader Disk Selection","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Bootloader Disk Selection release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Bootloader_Disk_Selection/#description","title":"Description","text":"

This test case verifies that the user is able to select an alternative disk on which to install the bootloader. It also verifies that, if the user is so inclined, they may choose not to install a bootloader at all.

DATA LOSS

Depending on installer choices this MAY destroy all the data on the test system. If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Bootloader_Disk_Selection/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Bootloader_Disk_Selection/#how-to-test","title":"How to test","text":"
  1. In the Installation Destination spoke, select the disk(s) to install to, then click the \"Full disk summary and bootl loader...\" button at the bottom of the screen:
  2. Click the checkbox next to the disk on which the bootloader is desired
  3. Alternatively, uncheck the boot checkbox next to all disks to skip bootloader installation
  4. Proceed with installation on the test system.
"},{"location":"documentation/QA/Testcase_Bootloader_Disk_Selection/#expected-results","title":"Expected Results","text":"
  1. Installation should complete successfully.
  2. Note that if no bootloader is installed, the system may not boot after installation is complete. This is expected.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso/","title":"QA:Testcase Custom Boot Methods Boot Iso","text":"

Associated release criterion

This test case is associated with the Release_Criteria#vnc-graphics-mode-behaviors release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso/#description","title":"Description","text":"

This is to verify that the Anaconda installer starts correctly when booting from the Rocky Linux boot.iso using a custom kernel command line.

"},{"location":"documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso/#setup","title":"Setup","text":"
  1. Prepare your system for booting the boot.iso image. This may involve writing the image to a USB key or burning it to an optical disk. Additionally, attaching the boot.iso to a virtual machine instance as a Virtual Optical Disk or mounting the boot.iso to server via baseboard management controller virtual media attach should be possible but is not expressly required.
"},{"location":"documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso/#how-to-test","title":"How to test","text":"
  1. Boot the system from the prepared optical, USB media or virtual device attachment.
  2. In the boot menu select the appropriate option to boot the installer.
  3. Interrupt the normal boot and edit the kernel command line.
  4. Add appropriate/required options to the kernel command line and resume booting into the installer.
"},{"location":"documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso/#expected-results","title":"Expected Results","text":"
  1. Boot menu is displayed for users to select install options. Navigating the menu and selecting entries must work. Editing the boot command line must be possible. If no option is selected, the installer should load after a reasonable timeout.
  2. System boots into the Anaconda installer and any command line options specified are utilized.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Debranding/","title":"QA:Testcase Debranding","text":"

Associated release criterion

This test case is associated with the Release_Criteria - Debranding release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Debranding/#description","title":"Description","text":"

The Rocky Linux Release Engineering Team builds and maintains tools to manage the debranding of packages received from the upstream vendor. They have published a comprehensive debranding guide and maintain a list of packages requiring debranding patches.

This testcase will verify that all packages available on released media that Rocky Linux Release Engineering has identified as requiring debranding are debranded successfully per their specification.

"},{"location":"documentation/QA/Testcase_Debranding/#setup","title":"Setup","text":"
  1. Obtain access to an environment with the dnf, and koji commands and access to Rocky Linux Gitlab and Rocky Linux Koji
  2. Download the ISO to be tested to test machine.
  3. Configure /etc/koji.conf to access the Rocky Linux Koji.
  4. Download a recent copy the patch.yml from Rocky Linux Gitlab.

patch.yml

Packages listed in patch.yml are names of source RPMs. Binary RPMs containing content produced by building the patched source RPMs need to be validated. The easiest way to get the list of all possible binary RPMs for a particular package and arch is to ask obtain that information in koji.

"},{"location":"documentation/QA/Testcase_Debranding/#how-to-test","title":"How to test","text":"
  1. Mount the ISO to be tested locally.
  2. Determine the path(s) to the repodata directory(ies) on the ISO.
  3. For each package to be validated get the names of the noarch and <arch> specific packages created from it.
  4. Use dnf to obtain the paths to the binary packages requiring debranding.

  5. Copy the <binary_package> from the media and examine it's metadata and/or contents to determine if it has obviously been patched.

    NOTE

    Note all debranding patches will patch files directly and leave very obvious traces, some patches don't even add changelog messages to use as an indicator that the package has been patched or debranded. Sometimes the only solution is to extract the binary package and examine the contents directly to find something to test.

  6. Unmount the ISO.

"},{"location":"documentation/QA/Testcase_Debranding/#expected-results","title":"Expected Results","text":"
  1. Packages tracked by Release Engineering as requiring debranding and published on installation media are, in fact, debranded per their specification.
Sample Output SuccessFailure 
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media\nmount: /media: WARNING: device write-protected, mounted read-only.\n\n$ find /media -name repodata\n/media/BaseOS/repodata\n/media/Minimal/repodata\n\n$ curl -LOR https://git.rockylinux.org/rocky/metadata/-/raw/main/patch.yml\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n100  3410  100  3410    0     0  20419      0 --:--:-- --:--:-- --:--:-- 20419\n\n$ yq .debrand.all[] patch.yml | column -x -c 100 -o \" \"\nabrt                   anaconda               anaconda-user-help   chrony\ncloud-init             cockpit                crash                dhcp\ndnf                    firefox                fwupd                gcc\ngcc-toolset-9-gcc      gcc-toolset-10-gcc     gcc-toolset-11-gcc   gcc-toolset-12-gcc\ngnome-settings-daemon  grub2                  httpd                initial-setup\nkernel                 kernel-rt              libdnf               libreoffice\nlibreport              nginx                  opa-ff               opa-fm\nopenscap               pesign                 PackageKit           python-pip\npython3                redhat-rpm-config      scap-security-guide  shim\nshim-unsigned-x64      shim-unsigned-aarch64  sos                  subscription-manager\nsystemd                thunderbird            WALinuxAgent\n\n$ ./yq .debrand.r8[] patch.yml | column -x -c 100 -o \" \"\ndotnet3.0  fwupdate  gnome-boxes  libguestfs  pcs  plymouth\npython2\n\nNOTE: Only a single package will be shown in this Example.\n\n$ koji --quiet latest-build --arch=x86_64 dist-rocky8-compose sos\n\n$ koji --quiet latest-build --arch=noarch dist-rocky8-compose sos\nsos-4.1-9.el8_5.rocky.3.noarch\nsos-audit-4.1-9.el8_5.rocky.3.noarch\n\n$ dnf download --urls --repofrompath BaseOS,/media/BaseOS --repo BaseOS \\\n  --repofrompath Minimal,/media/Minimal --repo Minimal \\\n  sos sos-audit | grep -E \"^file\"\nfile:///media/BaseOS/Packages/s/sos-4.1-5.el8.noarch.rpm\nfile:///media/BaseOS/Packages/s/sos-audit-4.1-5.el8.noarch.rpm\n\n$ rpm -q --changelog -p /media/BaseOS/Packages/s/sos-4.1-5.el8.noarch.rpm | \\\n    head | grep \"Release Engineering <releng@rockylinux.org>\" -C2\n* Mon Oct 18 2021 Release Engineering <releng@rockylinux.org> - 4.1-5\n- Remove Red Hat branding from sos\n$ echo $?\n0\n\n$ rpm -q --changelog -p /media/BaseOS/Packages/s/sos-audit-4.1-5.el8.noarch.rpm | \\\n    head | grep \"Release Engineering <releng@rockylinux.org>\" -C2\n* Mon Oct 18 2021 Release Engineering <releng@rockylinux.org> - 4.1-5\n- Remove Red Hat branding from sos\n$ echo $?\n0\n\n$ umount /media\n
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media\nmount: /media: WARNING: device write-protected, mounted read-only.\n\n$ find /media -name repodata\n/media/BaseOS/repodata\n/media/Minimal/repodata\n\n$ curl -LOR https://git.rockylinux.org/rocky/metadata/-/raw/main/patch.yml\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n100  3410  100  3410    0     0  20419      0 --:--:-- --:--:-- --:--:-- 20419\n\n$ yq .debrand.all[] patch.yml | column -x -c 100 -o \" \"\nabrt                   anaconda               anaconda-user-help   chrony\ncloud-init             cockpit                crash                dhcp\ndnf                    firefox                fwupd                gcc\ngcc-toolset-9-gcc      gcc-toolset-10-gcc     gcc-toolset-11-gcc   gcc-toolset-12-gcc\ngnome-settings-daemon  grub2                  httpd                initial-setup\nkernel                 kernel-rt              libdnf               libreoffice\nlibreport              nginx                  opa-ff               opa-fm\nopenscap               pesign                 PackageKit           python-pip\npython3                redhat-rpm-config      scap-security-guide  shim\nshim-unsigned-x64      shim-unsigned-aarch64  sos                  subscription-manager\nsystemd                thunderbird            WALinuxAgent\n\n$ ./yq .debrand.r8[] patch.yml | column -x -c 100 -o \" \"\ndotnet3.0  fwupdate  gnome-boxes  libguestfs  pcs  plymouth\npython2\n\nNOTE: Only a single package will be shown in this Example.\n\n$ koji --quiet latest-build --arch=x86_64 dist-rocky8-compose sos\n\n$ koji --quiet latest-build --arch=noarch dist-rocky8-compose sos\nsos-4.1-9.el8_5.rocky.3.noarch\nsos-audit-4.1-9.el8_5.rocky.3.noarch\n\n$ dnf download --urls --repofrompath BaseOS,/media/BaseOS --repo BaseOS \\\n  --repofrompath Minimal,/media/Minimal --repo Minimal \\\n  sos sos-audit | grep -E \"^file\"\nfile:///media/BaseOS/Packages/s/sos-4.1-5.el8.noarch.rpm\nfile:///media/BaseOS/Packages/s/sos-audit-4.1-5.el8.noarch.rpm\n\n$ rpm -q --changelog -p /media/BaseOS/Packages/s/sos-4.1-5.el8.noarch.rpm | \\\n    head | grep \"Release Engineering <releng@rockylinux.org>\" -C2\n$ echo $?\n1\n\n$ rpm -q --changelog -p /media/BaseOS/Packages/s/sos-audit-4.1-5.el8.noarch.rpm | \\\n    head | grep \"Release Engineering <releng@rockylinux.org>\" -C2\n$ echo $?\n1\n\n$ umount /media\n
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Disk_Layouts/","title":"QA:Testcase Disk Layouts","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Disk Layouts release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Disk_Layouts/#description","title":"Description","text":"

This test case verifies successful installation to any supported partition layout using any file system or format combination.

DATA LOSS

Depending on installer choices this MAY destroy all the data on the test system. If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Disk_Layouts/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Disk_Layouts/#how-to-test","title":"How to test","text":"
  1. Select the Installation Destination spoke.
  2. Select the volumes to which the operating system should be installed.
  3. Select the Custom radio button under the Storage Configuration section, then click \"Done\".
  4. For each volume, perform these steps:
    1. Choose the desired partitioning scheme from the dropdown menu. Supported options are Standard Partition, LVM, and LVM Thin Provisioning.
    2. Select the \"Encrypt my data\" checkbox to create an encrypted filesystem.
    3. Select the plus (+) button in the lower left hand corner to add a partition.
    4. Define the desired mount point and volume capacity, then click \"Add mount point\".
    5. Set the device type. Supported options are LVM, RAID, Standard Partition, and LVM Thin Provisioning.
    6. If device type was set to RAID, select the RAID level. Supported options are RAID0, RAID1, RAID4, RAID5, RAID6, and RAID10.
    7. Set the filesystem type. Supported options are BIOS Boot, ext2, ext3, ext4, swap, vfat, and xfs.
    8. In supported cases you may choose to disable formatting of existing partitions by unchecking the Reformat checkbox.
  5. When all partitions have been created, click the blue Done button in the upper left corner.
  6. Review the Summary of Changes dialog, then click Accept Changes.
  7. Continue the installation as normal.
"},{"location":"documentation/QA/Testcase_Disk_Layouts/#expected-results","title":"Expected Results","text":"
  1. The installation should complete successfully and boot to the appropriate disk.
  2. The specified filesystem type and partition scheme should be used.
  3. If configured, software RAID should function as expected.
"},{"location":"documentation/QA/Testcase_Disk_Layouts/#testing-with-openqa","title":"Testing with openQA","text":"

The following openQA test suites satisfy this release criteria:

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Firmware_RAID/","title":"QA:Testcase Firmware RAID","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Firmware RAID release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Firmware_RAID/#description","title":"Description","text":"

The installer must be able to detect and install to firmware RAID devices. Note that system-specific bugs do not count as blockers. It is likely that some hardware support might be broken or not available at all. DUDs (driver update disks) are not considered for this criteria.

"},{"location":"documentation/QA/Testcase_Firmware_RAID/#setup","title":"Setup","text":"
  1. Add steps for setup for this Testcase.
"},{"location":"documentation/QA/Testcase_Firmware_RAID/#how-to-test","title":"How to test","text":"
  1. Do this first...
  2. Then do this...
"},{"location":"documentation/QA/Testcase_Firmware_RAID/#expected-results","title":"Expected Results","text":"
  1. This is what you should see/verify.
  2. You should also see/verify this.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Installation_Interfaces/","title":"QA:Testcase Installation Interfaces","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Installation Interfaces release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Installation_Interfaces/#description","title":"Description","text":"

This test case verifies that the installer can complete an installation using all Anaconda spokes.

DATA LOSS

Depending on installer choices this MAY destroy all the data on the test system. If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Installation_Interfaces/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Installation_Interfaces/#how-to-test","title":"How to test","text":"
  1. Select a keyboard layout in the Keyboard Layout spoke
  2. Set language support in the Language spoke
  3. Set the system time and date in the Time and Date spoke
  1. Set a root password in the Root Password spoke
  2. Create a user in the user creation spoke
  1. Select an installation source from the Installation Source spoke
  2. Select a set of packages to install from the Package Selection spoke
  1. Set a disk to which the operating system should install in the Installation Destination spoke
  2. Set the kdump state from the Kdump spoke
  3. Configure the system's network and hostname from the Network and Hostname spoke
  4. Select a security policy from the Security Policy spoke
"},{"location":"documentation/QA/Testcase_Installation_Interfaces/#expected-results","title":"Expected Results","text":"
  1. The installation should complete and boot successfully.
"},{"location":"documentation/QA/Testcase_Installation_Interfaces/#testing-in-openqa","title":"Testing in openQA","text":"

The following openQA test suites satisfy this release criteria:

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Installer_Help/","title":"QA:Testcase Installer Help","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Installer Help release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Installer_Help/#description","title":"Description","text":"

Any element in the installer which contains a \u201chelp\u201d text must display the appropriate help documentation when selected.

"},{"location":"documentation/QA/Testcase_Installer_Help/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Installer_Help/#how-to-test","title":"How to test","text":"
  1. From the Anaconda Hub, click the Help button in the upper right hand corner.
  2. Verify that you see the \"Customizing your Installation\" help page.
  3. Verify that the \"Configuring language and location settings\" link displays a topically appropriate page.
  4. Close the Help browser to return to the Anaconda Hub.
  5. Verify that the Localization help page displays for the Keyboard, Language Support, and Time & Date spokes:
    1. Select the spoke, then click the Help button.
    2. Verify that you see the \"Configuring localization options\" page containing a functioning link to the \"Configuring keyboard, language, and time and date settings\" page.
    3. Close the Help browser (and click Done if necessary) to return to the Anaconda Hub.
  6. Verify that the Help button in the Installation Source spoke displays the \"Configuring installation source\" page.
  7. Verify that the Help button in the Software Selection spoke displays the \"Configuring software selection\" page.
  8. Verify that the Help button in the Installation Destination spoke displays the \"Configuring storage devices\" page.
  9. Verify that the Help button in the Network & Host Name spoke displays the \"Configuring network and host name options\" page.
  10. Verify that the Help button in the Root Password spoke displays the \"Configuring a root password\" page.
  11. Verify that the Help button in the User Creation spoke displays the \"Creating a user account\" page.
"},{"location":"documentation/QA/Testcase_Installer_Help/#expected-results","title":"Expected Results","text":"
  1. All links should work and display relevant content.
"},{"location":"documentation/QA/Testcase_Installer_Help/#testing-in-openqa","title":"Testing in openQA","text":"

The following openQA test suites satisfy this release criteria:

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Installer_Translations/","title":"QA:Testcase Installer Translations","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Installer Translations release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Installer_Translations/#description","title":"Description","text":"

The installer must correctly display all complete translations that are available for use.

"},{"location":"documentation/QA/Testcase_Installer_Translations/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Installer_Translations/#how-to-test","title":"How to test","text":"
  1. From the Language Selection spoke, select a language.
"},{"location":"documentation/QA/Testcase_Installer_Translations/#expected-results","title":"Expected Results","text":"
  1. All spokes should display at least some of the content in the selected language.
  2. It is expected to still see some content displayed in Latin characters even if a language that does not use Latin characters is selected.
"},{"location":"documentation/QA/Testcase_Installer_Translations/#testing-in-openqa","title":"Testing in openQA","text":"

The following openQA test suites satisfy this release criteria:

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Kickstart_Installation/","title":"QA:Testcase Kickstart Installation","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Kickstart Installation release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Kickstart_Installation/#description","title":"Description","text":"

This test case verifies that installations via both local and remote Kickstart configuration files are successful.

DATA LOSS

Depending on installer choices this MAY destroy all the data on the test system. If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Kickstart_Installation/#setup","title":"Setup","text":"
  1. Copy a valid Kickstart file to a USB stick
  2. Connect the USB stick to the test system
  3. Obtain access to supported system and hardware class to be installed.
  4. Prepare appropriate media for the selected ISO to be tested.
  5. Boot the system from the prepared optical, USB media or virtual device attachment.
  6. In the boot menu select the appropriate option to boot the installer.
  7. Hit the Tab key to edit the boot command
  8. Provide a local Kickstart file by supplying the GRUB boot option inst.ks=file:/path/to/local.ks or a remote Kickstart file by supplying the GRUB boot option inst.ks=https://git.resf.org/testing/createhdds/raw/branch/rocky/server.ks.
"},{"location":"documentation/QA/Testcase_Kickstart_Installation/#how-to-test","title":"How to test","text":"
  1. Continue booting the installer as normal.
"},{"location":"documentation/QA/Testcase_Kickstart_Installation/#expected-results","title":"Expected Results","text":"
  1. The installation should complete and boot successfully, automatically populating the options specified in the Kickstart file.
"},{"location":"documentation/QA/Testcase_Kickstart_Installation/#testing-in-openqa","title":"Testing in openQA","text":"

The following openQA test suites satisfy this release criteria:

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Media_File_Conflicts/","title":"QA:Testcase Media File Conflicts","text":"

Associated release criterion

This test case is associated with the Release_Criteria#no-broken-packages release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Media_File_Conflicts/#description","title":"Description","text":"

This testcase will verify that the offline repository included on release blocking images will not contain any file conflicts between packages without explicit Conflicts: tag in the package metadata.

"},{"location":"documentation/QA/Testcase_Media_File_Conflicts/#setup","title":"Setup","text":"
  1. Obtain access to an environment with the dnf and python3 commands.
  2. Download the ISO to be tested to that machine.
  3. Download the potential_conflict.py script provided by Rocky Linux Testing Team.
"},{"location":"documentation/QA/Testcase_Media_File_Conflicts/#how-to-test","title":"How to test","text":"
  1. Mount the ISO to be tested locally.
  2. Determine the path to the repodata directory(ies) on the ISO.
  3. Run the potential_conflict.py script on the mounted ISO.
  4. Unmount the ISO.
"},{"location":"documentation/QA/Testcase_Media_File_Conflicts/#expected-results","title":"Expected Results","text":"
  1. The potential_conflict.py script does not report any packages with non-declared conflicts.
Sample Output SuccessFailure 
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media\nmount: /media: WARNING: device write-protected, mounted read-only.\n\n$ python3 /vagrant/scripts/potential_conflict.py \\\n  --repofrompath BaseOS,/media/BaseOS --repoid BaseOS \\\n  --repofrompath Minimal,/media/Minimal --repoid Minimal\n\nAdded BaseOS repo from /media/BaseOS\nAdded Minimal repo from /media/Minimal\nGetting complete filelist for:\nfile:///media/BaseOS\nfile:///media/Minimal\n168374 files found.\n\nLooking for duplicated filenames:\n524 duplicates found.\n\nDoing more advanced checks to see if these are real conflicts:\n 10% complete (    52/   524,  1139/sec),    0 found - eta 0:00:00\n 35% complete (   182/   524,  1146/sec),    0 found - eta 0:00:00\n 45% complete (   234/   524,  1818/sec),    0 found - eta 0:00:00\n 50% complete (   260/   524, 592673/sec),    0 found - eta 0:00:00\n 55% complete (   286/   524, 778942/sec),    0 found - eta 0:00:00\n 60% complete (   312/   524, 801852/sec),    0 found - eta 0:00:00\n 79% complete (   416/   524,   234/sec),    0 found - eta 0:00:00\n 84% complete (   442/   524,   902/sec),    0 found - eta 0:00:00\n 89% complete (   468/   524,   935/sec),    0 found - eta 0:00:00\n 94% complete (   494/   524,  1616/sec),    0 found - eta 0:00:00\n 99% complete (   520/   524,  1114/sec),    0 found - eta 0:00:00\n\n0 file conflicts found.\n0 package conflicts found.\n\n== Package conflicts ==\n\n== File conflicts, listed by conflicting packages ==\n\n$ sudo umount /media\n
$ sudo mount -o loop Rocky-8.5-x86_64-dvd1.iso /media\nmount: /media: WARNING: device write-protected, mounted read-only.\n\n\n$ python3 /vagrant/scripts/potential_conflict.py \\\n  --repofrompath AppStream,/media/AppStream --repoid AppStream \\\n  --repofrompath BaseOS,/media/BaseOS --repoid BaseOS\n\n  Added AppStream repo from /media/AppStream\n  Added BaseOS repo from /media/BaseOS\n  Getting complete filelist for:\n  file:///media/AppStream\n  file:///media/BaseOS\n  851967 files found.\n\n  Looking for duplicated filenames:\n  101865 duplicates found.\n\n  Doing more advanced checks to see if these are real conflicts:\n    5% complete (  5093/101865,  8713/sec),    0 found - eta 0:00:11\n   10% complete ( 10186/101865, 1787281/sec),    0 found - eta 0:00:05\n   15% complete ( 15279/101865, 2223312/sec),    0 found - eta 0:00:03\n   20% complete ( 20372/101865, 23614/sec),    0 found - eta 0:00:03\n   25% complete ( 25465/101865, 57188/sec),    0 found - eta 0:00:02\n   30% complete ( 30558/101865,  3831/sec),    0 found - eta 0:00:05\n   35% complete ( 35651/101865, 48455/sec),    0 found - eta 0:00:04\n   40% complete ( 40744/101865, 32067/sec),    0 found - eta 0:00:03\n   45% complete ( 45837/101865, 2136586/sec),    0 found - eta 0:00:03\n   50% complete ( 50930/101865, 72529/sec),    0 found - eta 0:00:02\n   55% complete ( 56023/101865, 176294/sec),    0 found - eta 0:00:02\n   60% complete ( 61116/101865, 68622/sec),    1 found - eta 0:00:01\n   65% complete ( 66209/101865, 155133/sec),    1 found - eta 0:00:01\n   70% complete ( 71302/101865, 13874/sec),    1 found - eta 0:00:01\n   75% complete ( 76395/101865, 10835/sec),    1 found - eta 0:00:01\n   80% complete ( 81488/101865, 27477/sec),    1 found - eta 0:00:00\n   85% complete ( 86581/101865,  9075/sec),    1 found - eta 0:00:00\n   90% complete ( 91674/101865, 14807/sec),    1 found - eta 0:00:00\n   95% complete ( 96767/101865, 197437/sec),    1 found - eta 0:00:00\n  100% complete (101860/101865, 38727/sec),    1 found - eta 0:00:00\n\n  1 file conflicts found.\n  11 package conflicts found.\n\n  == Package conflicts ==\n  mariadb-server-utils-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64\n  mysql-server-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64\n\n  python3-mod_wsgi-4.6.4-4.el8.x86_64\n  python38-mod_wsgi-4.6.8-3.module+el8.4.0+570+c2eaf144.x86_64\n  python39-mod_wsgi-4.7.1-4.module+el8.4.0+574+843c4898.x86_64\n\n  libcmpiCppImpl0-2.0.3-15.el8.i686\n  tog-pegasus-libs-2:2.14.1-46.el8.i686\n\n  mariadb-connector-c-devel-3.1.11-2.el8_3.i686\n  mariadb-connector-c-devel-3.1.11-2.el8_3.x86_64\n  mariadb-devel-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64\n  mysql-devel-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64\n\n  mariadb-server-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64\n  mysql-server-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64\n\n  mariadb-test-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64\n  mysql-test-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64\n\n  mariadb-connector-c-devel-3.1.11-2.el8_3.i686\n  mariadb-connector-c-devel-3.1.11-2.el8_3.x86_64\n  mysql-devel-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64\n\n  mariadb-devel-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64\n  mysql-devel-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64\n\n  mariadb-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64\n  mysql-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64\n\n  libcmpiCppImpl0-2.0.3-15.el8.x86_64\n  tog-pegasus-libs-2:2.14.1-46.el8.x86_64\n\n  libev-libevent-devel-4.24-6.el8.i686\n  libev-libevent-devel-4.24-6.el8.x86_64\n  libevent-devel-2.1.8-5.el8.i686\n  libevent-devel-2.1.8-5.el8.x86_64\n\n\n  == File conflicts, listed by conflicting packages ==\n  mariadb-server-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64\n  mysql-test-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64\n    /usr/bin/mysqld_safe\n\n$ sudo umount /media\n
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Media_Repoclosure/","title":"QA:Testcase Media Repoclosure","text":"

Associated release criterion

This test case is associated with the Release_Criteria#no-broken-packages release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Media_Repoclosure/#description","title":"Description","text":"

This testcase will verify that the offline repository included on release blocking images will not contain broken dependencies.

"},{"location":"documentation/QA/Testcase_Media_Repoclosure/#setup","title":"Setup","text":"
  1. Obtain access to an environment with the dnf repoclosure command.
  2. Download the ISO to be tested to that machine.
"},{"location":"documentation/QA/Testcase_Media_Repoclosure/#how-to-test","title":"How to test","text":"
  1. Mount the ISO to be tested locally.
  2. Determine the path to the repodata directory(ies) on the ISO.
  3. Run the dnf repoclosure command on the mounted ISO.
  4. Unmount the ISO.
"},{"location":"documentation/QA/Testcase_Media_Repoclosure/#expected-results","title":"Expected Results","text":"
  1. The dnf repoclosure command does not generate any errors.
Sample Output SuccessFailure 
$ sudo mount -o loop Rocky-8.5-x86_64-minimal.iso /media\nmount: /media: WARNING: device write-protected, mounted read-only.\n\n[vagrant@localhost ~]$ dnf --refresh repoclosure \\\n  --repofrompath BaseOS,/media/BaseOS --repo BaseOS \\\n  --repofrompath Minimal,/media/Minimal --repo Minimal\nAdded BaseOS repo from /media/BaseOS\nAdded Minimal repo from /media/Minimal\nBaseOS                                               102 MB/s | 2.6 MB     00:00\nMinimal                                               90 kB/s | 384  B     00:00\n\n$ sudo umount /media\n

NOTE: In this example the content of the Rocky-8.5-x86_64-minimal.iso was copied to /tmp then the BaseOS repository was modified to remove the setup-2.12.2-6.el8.noarch.rpm package and the repository metadata was regenerated.

[vagrant@localhost ~]$ dnf --refresh repoclosure \\\n  --repofrompath BaseOS,/tmp/media/BaseOS --repo BaseOS \\\n  --repofrompath Minimal,/tmp/media/Minimal --repo Minimal\nAdded BaseOS repo from /tmp/media/BaseOS\nAdded Minimal repo from /tmp/media/Minimal\nBaseOS                                               3.7 MB/s | 3.8 kB     00:00\nMinimal                                              3.7 MB/s | 3.8 kB     00:00\npackage: basesystem-11-5.el8.noarch from BaseOS\n  unresolved deps:\n    setup\npackage: dump-1:0.4-0.36.b46.el8.x86_64 from BaseOS\n  unresolved deps:\n    setup\npackage: filesystem-3.8-6.el8.x86_64 from BaseOS\n  unresolved deps:\n    setup\npackage: initscripts-10.00.15-1.el8.x86_64 from BaseOS\n  unresolved deps:\n    setup\npackage: rpcbind-1.2.5-8.el8.x86_64 from BaseOS\n  unresolved deps:\n    setup\npackage: shadow-utils-2:4.6-14.el8.x86_64 from BaseOS\n  unresolved deps:\n    setup\nError: Repoclosure ended with unresolved dependencies.\n
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Media_USB_dd/","title":"QA:Testcase Media USB dd","text":"

Associated release criterion

This test case is associated with the Release_Criteria#initialization-requirements release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Media_USB_dd/#description","title":"Description","text":"

This verifies that Rocky Linux ISO image can be written to USB media using dd command, and the resulting USB media successfully boots to the Anaconda Installer.

DATA LOSS

Any data on the USB stick used for this test is likely to be destroyed. Please do not use a stick whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Media_USB_dd/#setup","title":"Setup","text":"
  1. Provide a USB media device that is larger than the ISO image you wish to test and that it can be completely erased.
  2. Provide a Linux (or other *nix system) that has the dd command available and an unoccupied USB port.
  3. Download the Rocky Linux ISO image you wish to test onto the test system.
  4. Download the CHECKSUM file that goes with the Rocky Linux ISO image that you wish to test.
  5. Download the CHECKSUM.sig file that does with the CHECKSUM file.
  6. Download the Rocky Release Engineering GPG key.
"},{"location":"documentation/QA/Testcase_Media_USB_dd/#how-to-test","title":"How to test","text":"
  1. Import the Rocky Release Engineering GPG key.
  2. Verify the signature of the CHECKSUM file.
  3. Verify the CHECKSUM of the Rocky Linux ISO...
  4. Write the Rocky Linux ISO to the USB media using dd...
  5. Boot the test system with the USB media.
  6. In the boot menu select the appropriate option to boot the installer.
  7. [OPTIONAL] Proceed with installation on the test system.Depending on installer choices this MAY destroy all the data on the test system.
"},{"location":"documentation/QA/Testcase_Media_USB_dd/#expected-results","title":"Expected Results","text":"
  1. The gpg signature on the CHECKSUM file is valid.
  2. The CHECKSUM of the Rocky Linux ISO is valid.
  3. The Rocky Linux ISO is written to the USB stick without errors.
  4. The USB stick boots without errors.
  5. The Anaconda Installer starts without errors.

DATA LOSS

If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

[OPTIONALLY] 6. The installation finishes successfully and, if the minimal or DVD ISO were used, the package repository on the USB stick (not a network based repository) was used for the installation.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Minimal_Installation/","title":"QA:Testcase Minimal Installation","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Minimal Installation release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Minimal_Installation/#description","title":"Description","text":"

This test case verifies that a networked minimal installation is able to install the 'Minimal' package set. The installation should not require use of local packages to complete.

DATA LOSS

Depending on installer choices this MAY destroy all the data on the test system. If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Minimal_Installation/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Minimal_Installation/#how-to-test","title":"How to test","text":"
  1. From the Installation Source spoke, configure a remote repository source from MirrorManager appropriate to the architecture under test.
  2. From the Software Selection spoke, select the Minimal package set.
  3. Complete the installation using desired parameters.
"},{"location":"documentation/QA/Testcase_Minimal_Installation/#expected-results","title":"Expected Results","text":"
  1. The installation should complete and boot successfully.
"},{"location":"documentation/QA/Testcase_Minimal_Installation/#testing-in-openqa","title":"Testing in openQA","text":"

The following openQA test suites satisfy this release criteria:

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Network_Attached_Storage/","title":"QA:Testcase Network Attached Storage","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Network Attached Storage release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Network_Attached_Storage/#description","title":"Description","text":"

The installer must be able to detect and install to supported NAS devices (if possible and supported by the kernel).

"},{"location":"documentation/QA/Testcase_Network_Attached_Storage/#setup","title":"Setup","text":"
  1. Add steps for setup for this Testcase.
"},{"location":"documentation/QA/Testcase_Network_Attached_Storage/#how-to-test","title":"How to test","text":""},{"location":"documentation/QA/Testcase_Network_Attached_Storage/#nfs","title":"NFS","text":"

install nfs-utils sudo mount -t nfs nfs-server:/nfs/path /mnt then a created a file echo 1 > /mnt/1 verified it and permissions ls /mnt; cat /mnt/1 then deleted it rm /mnt/1 then unmounted sudo umount /mnt

"},{"location":"documentation/QA/Testcase_Network_Attached_Storage/#iscsi","title":"iSCSI","text":""},{"location":"documentation/QA/Testcase_Network_Attached_Storage/#expected-results","title":"Expected Results","text":"
  1. This is what you should see/verify.
  2. You should also see/verify this.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Packages_Installer_Sources/","title":"QA:Testcase Packages and Installer Sources","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Packages and Installer Sources release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Packages_Installer_Sources/#description","title":"Description","text":"

This test case verifies that the installer can successfully install any of the supported package sets via any of the supported installer sources.

The following package sets are supported for installs from local media:

The following package sets are only available from remote sources and require a network connection:

DATA LOSS

Depending on installer choices this MAY destroy all the data on the test system. If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Packages_Installer_Sources/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Packages_Installer_Sources/#how-to-test","title":"How to test","text":"
  1. For local package installations it is not necessary to enable networking or specify a mirror.
  2. For package installation from remote sources:
    1. From the Network and Hostname spoke, enable networking.
    2. From the Installation Source spoke, configure a remote software source, supplying an appropriate mirror for the version and architecture under test.
  3. Complete the installer and wait for the machine to reboot.
"},{"location":"documentation/QA/Testcase_Packages_Installer_Sources/#expected-results","title":"Expected Results","text":"
  1. The installation should complete and boot successfully.
  2. If a graphical package set was specified, the system should boot to a graphical login screen.
"},{"location":"documentation/QA/Testcase_Packages_Installer_Sources/#testing-in-openqa","title":"Testing in openQA","text":"

The following openQA test suites satisfy this release criteria, provided they pass the _do_install_reboot module at a minimum:

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Packages_No_Insights/","title":"QA:Testcase Packages No Insights","text":"

Associated release criterion

This test case is associated with the Release_Criteria#repositories-must-match-upstream release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Packages_No_Insights/#description","title":"Description","text":"

This test will verify that insights-client package is not declared be installed as part of a package group.

"},{"location":"documentation/QA/Testcase_Packages_No_Insights/#setup","title":"Setup","text":"
  1. Obtain access to an environment with the dnf command.
  2. Download the ISO to be tested to that machine.
"},{"location":"documentation/QA/Testcase_Packages_No_Insights/#how-to-test","title":"How to test","text":"
  1. Mount the ISO to be tested locally.
  2. Determine the path to the comps file(s) on the ISO.
  3. Verify that insights-client is not declared to be installed automatically.
  4. Unmount the ISO.
"},{"location":"documentation/QA/Testcase_Packages_No_Insights/#expected-results","title":"Expected Results","text":"
  1. insights-client is not declared to be installed by default.
Sample Output SuccessFailure

UPDATE SAMPLE

NOTE: This example needs to be refreshed when the 8.6 ISO has been produced. As seen in the Failure section below the Rocky-8.5-x86_64-dvd1.iso includes the insights-client as part of the base group. The package should be included on the DVD ISO but should not be installed automatically.

$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media\nmount: /media: WARNING: device write-protected, mounted read-only.\n\n$ dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath Minimal,/media/Minimal --repo Minimal search insights-client\nAdded BaseOS repo from /media/BaseOS\nAdded Minimal repo from /media/Minimal\nBaseOS                                                                    3.8 MB/s | 3.9 kB     00:00\nMinimal                                                                   3.7 MB/s | 3.8 kB     00:00\nNo matches found.\n\n$ find /media -name \"*comps*.xml\" -exec grep -H \"insights-client\" '{}' \\;\n\n$ dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath Minimal,/media/Minimal --repo Minimal groupinfo base | grep -E \":|insights\"\nBaseOS                                          3.8 MB/s | 3.9 kB     00:00\nMinimal                                         3.7 MB/s | 3.8 kB     00:00\nGroup: Base\n Description: The standard installation of Rocky Linux.\n Mandatory Packages:\n Default Packages:\n Optional Packages:\n\n$ sudo umount /media\n
$ sudo mount -o loop Rocky-8.5-x86_64-dvd1.iso /media\nmount: /media: WARNING: device write-protected, mounted read-only.\n\n$ dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream search insights-client\nAdded BaseOS repo from /media/BaseOS\nAdded AppStream repo from /media/AppStream\nBaseOS                                                                    3.8 MB/s | 3.9 kB     00:00\nAppStream                                                                 4.2 MB/s | 4.3 kB     00:00\n================================= Name Exactly Matched: insights-client ==================================\ninsights-client.noarch : Uploads Insights information to Red Hat on a periodic basis\n\n$ find /media -name \"*comps*.xml\" -exec grep -H \"insights-client\" '{}' \\;\n/media/AppStream/repodata/a6742e1300e1c786af91656b152d3b98bb7aff598e650509381417970e1f1b7e-comps-AppStream.x86_64.xml:      <packagereq type=\"default\">insights-client</packagereq>\n/media/AppStream/repodata/a6742e1300e1c786af91656b152d3b98bb7aff598e650509381417970e1f1b7e-comps-AppStream.x86_64.xml:      <packagereq type=\"default\">insights-client</packagereq>\n\n$ dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream groupinfo base | grep -E \":|insights\"\nBaseOS                                          3.8 MB/s | 3.9 kB     00:00\nAppStream                                       4.2 MB/s | 4.3 kB     00:00\nGroup: Base\n Description: The standard installation of Rocky Linux.\n Mandatory Packages:\n Default Packages:\n   insights-client\n Optional Packages:\n\n$ sudo umount /media\n
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Packages_No_RHSM/","title":"QA:Testcase Packages No RHSM","text":"

Associated release criterion

This test case is associated with the Release_Criteria#repositories-must-match-upstream release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Packages_No_RHSM/#description","title":"Description","text":"

This test will verify that packages that are availble from upstream do not have hard requirements on subscription-manager (RHSM).

"},{"location":"documentation/QA/Testcase_Packages_No_RHSM/#setup","title":"Setup","text":"
  1. Obtain access to an environment with the dnf command.
  2. Download the ISO to be tested to that machine.
"},{"location":"documentation/QA/Testcase_Packages_No_RHSM/#how-to-test","title":"How to test","text":"
  1. Mount the ISO to be tested locally.
  2. Obtain a list of packages that have Requires: for subscription-manager
  3. Download the packages with explicity Requires: for subscription-manager
  4. Obtain the SOURCEPKG definition for the above packages
  5. Unmount the ISO.
"},{"location":"documentation/QA/Testcase_Packages_No_RHSM/#expected-results","title":"Expected Results","text":"
  1. No packages have an explicit requirement for subscription-manager.
Sample Output SuccessFailure 
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media\nmount: /media: WARNING: device write-protected, mounted read-only.\n\n$ package_list=($(dnf --refresh repoquery --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream --whatrequires subscription-manager 2>/dev/null| grep el8))\n\n$ dnf --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream download \"${package_list[@]}\"\nAdded BaseOS repo from /media/BaseOS\nAdded AppStream repo from /media/AppStream\nLast metadata expiration check: 0:00:25 ago on Sun 24 Apr 2022 10:57:13 PM UTC.\n\n$ rpm -q --queryformat=\"%{NAME}|%{SOURCERPM}\\n\" subscription-manager*.rpm | column -s\\| -t\nsubscription-manager-cockpit        subscription-manager-1.28.21-3.el8.src.rpm\nsubscription-manager-migration      subscription-manager-1.28.21-3.el8.src.rpm\nsubscription-manager-plugin-ostree  subscription-manager-1.28.21-3.el8.src.rpm\n\n$ sudo umount /media\n

TBD

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_Application_Functionality/","title":"QA:Testcase Application Functionality","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#default-application-functionality-desktop-only release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

REFERENCED RELEASE CRITERIA IS OVERLY GENERAL AND UNTESTABLE

The associated release criteria, Release_Criteria#default-application-functionality-desktop-only, for this test case is overly general and must be modified to specific enough to be testable.

"},{"location":"documentation/QA/Testcase_Post_Application_Functionality/#description","title":"Description","text":"

This testcase handles all applications, considered as core applications of the desktop environment GNOME or user facing commandline applications.

The following tasks apply in general to all of the following applications:

"},{"location":"documentation/QA/Testcase_Post_Application_Functionality/#setup","title":"Setup","text":"

Obtain access to a suitable system with either a Workstation or a Graphical Server installation.

"},{"location":"documentation/QA/Testcase_Post_Application_Functionality/#how-to-test","title":"How to test","text":"
  1. Check that the application starts without any errors
  2. Further check that the context menus for the correct function
  3. Open files to test the functionality of the individual applications
"},{"location":"documentation/QA/Testcase_Post_Application_Functionality/#expected-results","title":"Expected Results","text":"

Make sure that the individual applications behave as they should.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_Artwork_and_Assets/","title":"QA:Testcase Artwork and Assets","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#artwork-and-assets-server-and-desktop release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_Artwork_and_Assets/#description","title":"Description","text":"

There are several brand artworks and assets throughout the whole OS, this testcase will take care of checking, that these are actually in place, and don't produce any UI errors. This is exclusively for installations with the default desktop environment GDM and GNOME.

"},{"location":"documentation/QA/Testcase_Post_Artwork_and_Assets/#setup","title":"Setup","text":"
  1. Acquire access to either a baremetal machine or a VM host, to install a new machine
  2. Prepare appropriate media for the selected ISO to be tested.
"},{"location":"documentation/QA/Testcase_Post_Artwork_and_Assets/#how-to-test","title":"How to test","text":"
  1. While booting the image check, that the correct logo is visible in the loading screen before Anaconda comes up
  2. Look at the Anaconda images in the rocky-logos repo and check if all assets are correctly applied in Anaconda (they will generally be visible right away while going through the install process)
  3. Install the system with either the Workstation install set or Graphical Server
  4. While the OS does its first boot, check that the correct logo is visible in the loading screen before the boot login screen shows up
  5. Check the logo and background of the boot login screen
  6. After the login check the desktop background and further all available options in the settings menu for the desktop background
  7. Lock the screen and check the background visible in the flyover
  8. At last check the logo and background of the login screen
"},{"location":"documentation/QA/Testcase_Post_Artwork_and_Assets/#expected-results","title":"Expected Results","text":"

The tests during the process could be successfully finished.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_GNOME_UI_Functionality/","title":"QA:Testcase GNOME UI Functionality","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

REFERENCED RELEASE CRITERIA IS OVERLY GENERAL AND UNTESTABLE

The associated release criteria, Release_Criteria#default-panel-functionality-desktop-only, for this test case is overly general and must be modified to specific enough to be testable.

Associated release criterion

This test case is associated with the Release_Criteria#default-panel-functionality-desktop-only release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_GNOME_UI_Functionality/#description","title":"Description","text":"

This test collection takes care of the correct functionality of the GNOME UI.

"},{"location":"documentation/QA/Testcase_Post_GNOME_UI_Functionality/#setup","title":"Setup","text":"

Obtain access to a suitable system with either a Workstation or a Graphical Server installation.

"},{"location":"documentation/QA/Testcase_Post_GNOME_UI_Functionality/#how-to-test","title":"How to test","text":"
  1. Login to the Rocky Machine via the UI
  2. Navigate through the GNOME UI
"},{"location":"documentation/QA/Testcase_Post_GNOME_UI_Functionality/#expected-results","title":"Expected Results","text":"
  1. After the login you should have landed on the desktop with the background and the top bar of GNOME visible
  2. Clicking the the Activities button in the upper right should bring up the overview
  3. Further there should be the favourite applications ribbon on the left
  4. And after clicking the 9-dot-icon all applications should appear
  5. Back on the desktop check the function of the system and clock panel on the upper right and middle

It is also a good measure to do some more basic clicking through the GNOME UI, like opening applications, interacting with the application headerbar, moving applications to different desktops or changing settings in the System settings.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_Identity_Management/","title":"QA:Testcase Identity Management","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#packages-and-module-installation release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_Identity_Management/#description","title":"Description","text":"

Setting up a IdM system (FreeIPA) and using it's functionality leverages not also a lot of the packages in the official repos, it also tests quite a lot of used functions a corporate environment. This installatation will host it's own dns server for more generic testing without relying on the individual infrastructure of the environment.

"},{"location":"documentation/QA/Testcase_Post_Identity_Management/#requirements","title":"Requirements","text":""},{"location":"documentation/QA/Testcase_Post_Identity_Management/#setup","title":"Setup","text":"
  1. dnf module enable idm:DL1
  2. dnf module install idm:DL1/dns

  3. ipa-server-install

  4. firewall-cmd --add-service={freeipa-4,dns} --permanent

  5. firewall-cmd --add-service={freeipa-4,dns}
"},{"location":"documentation/QA/Testcase_Post_Identity_Management/#how-to-test","title":"How to test","text":"
  1. Make sure Kerberos works, by running kinit admin and klist
  2. Make sure the webfrontend is reachable and login works
  3. Furthermore you can also attach another system (DNS + connecting via SSSD)
"},{"location":"documentation/QA/Testcase_Post_Identity_Management/#expected-results","title":"Expected Results","text":"

After installation all services should be available and work correctly.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/","title":"QA:Testcase Keyboard Layout","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#keyboard-layout release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/#description","title":"Description","text":"

As there are a lot of different keyboard layouts available, it is necessary to test if the keyboard functionality works without any issues throughout the system.

"},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/#setup","title":"Setup","text":""},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/#how-to-test","title":"How to test","text":""},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/#installer","title":"Installer","text":"
  1. Bootup the installer
  2. Choose a language
  3. Make sure that the keyboard layout got chosen correctly corresponding to the language setting
  4. Change the keyboard layout if needed to test
  5. Enter text all over Anaconda to make sure the keyboard layout works correctly with the chosen keyboard layout
"},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/#disk-encryption","title":"Disk Encryption","text":"
  1. Setup a system with disk encryption
  2. Check that the password for the disk encryption works on bootup with graphical UI
  3. Check that the password for the disk encryption works on bootup with text mode
"},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/#text-mode","title":"Text mode","text":"

Check that the chosen keyboard layout works correctly on text mode.

"},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/#gnome-and-application","title":"GNOME and Application","text":"
  1. Check the login, that the keyboard layout works correctly on the graphical UI login screen
  2. Also check that the GNOME UI works correctly with the chosen keyboard layout
  3. And finally check some applications, that the keyboard works as expected
"},{"location":"documentation/QA/Testcase_Post_Keyboard_Layout/#expected-results","title":"Expected Results","text":"

The tests during the process could be successfully finished.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_Module_Streams/","title":"QA:Testcase Module Streams","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#packages-and-module-installation release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_Module_Streams/#description","title":"Description","text":"

This test case takes care of testing the module streams, that they are all installable, all available and working as expected.

"},{"location":"documentation/QA/Testcase_Post_Module_Streams/#setup","title":"Setup","text":"

For this tests you will need to install every module stream on its own, so it's the best to setup a new system which gets snapshoted after the initial setup. After that it can be rolled back for every module install.

It's enough to setup a system with the Minimal Install group.

"},{"location":"documentation/QA/Testcase_Post_Module_Streams/#how-to-test","title":"How to test","text":"
  1. Login to the machine
  2. Get a list of all module streams and compare it to the stream list from RHEL and to the source in Git source repo
  3. The easiest way to test all streams is to install the package groups in the individual streams, i.e. for postgresql:
dnf module install postgresql\ndnf module install postgresql:13\ndnf module install postgresql:13/client\n

Repeat step 3 as often as module streams and package groups are available.

This could be automated with i.e. Ansible to do all the install -> rollback -> install -> rollback -> ... and emiting the output via Ansible.

"},{"location":"documentation/QA/Testcase_Post_Module_Streams/#expected-results","title":"Expected Results","text":"

All module streams should be available and there shouldn't be any errors while installing any of the package groups of the individual streams. (some of the installs will show warnings though because they are incompatible with other streams)

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_Multimonitor_Setup/","title":"QA:Testcase Multimonitor Setup","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#dual-monitor-setup-desktop-only release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_Multimonitor_Setup/#description","title":"Description","text":"

This test covers the check if GNOME behaves as it should in multi-monitor setups.

"},{"location":"documentation/QA/Testcase_Post_Multimonitor_Setup/#setup","title":"Setup","text":"

You will need either a machine which can be reinstalled with multiple screens, or a virtualization software which is capable of providing multiple screens (like VMware Workstation (Pro or Player) or VMware Fusion, but there is also a hack for VMware ESXi)

"},{"location":"documentation/QA/Testcase_Post_Multimonitor_Setup/#how-to-test","title":"How to test","text":"
  1. Run installer with multiple screens connected and install with either the Workstation or Graphical Server group
  2. Login to the machine after the finished install
"},{"location":"documentation/QA/Testcase_Post_Multimonitor_Setup/#expected-results","title":"Expected Results","text":"

There shouldn't be any graphical glitches, or scaling issues through the install and the usage.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_Package_installs/","title":"QA:Testcase Basic Package installs","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#packages-and-module-installation release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

REFERENCED RELEASE CRITERIA IS OVERLY GENERAL AND UNTESTABLE

The associated release criteria, Release_Criteria#packages-and-module-installation, for this test case is overly general and must be modified to specific enough to be testable.

"},{"location":"documentation/QA/Testcase_Post_Package_installs/#description","title":"Description","text":"

Installing several packages should work without any issues.

Please also test these usecases (it's basically the fun of learning to install software, it's even good if it's done differently each other time):

"},{"location":"documentation/QA/Testcase_Post_Package_installs/#setup","title":"Setup","text":"

Obtain access to a suitable system where any of the tested packages can be installed without any issues.

"},{"location":"documentation/QA/Testcase_Post_Package_installs/#how-to-test","title":"How to test","text":"
  1. Install a list of packages or usecases
"},{"location":"documentation/QA/Testcase_Post_Package_installs/#expected-results","title":"Expected Results","text":"

Installs work without any issues.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Desktop/","title":"QA:Testcase SELinux Errors on Desktop clients","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#selinux-and-crash-notifications-desktop-only release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Desktop/#description","title":"Description","text":"

Basically running a Workstation or Graphical Server install for a longer amount of time, while using it and then checking if there were any SELinux audit messages.

"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Desktop/#setup","title":"Setup","text":"

Obtain access to a suitable system with either a Workstation or a Graphical Server installation.

"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Desktop/#how-to-test","title":"How to test","text":"
  1. Setup new machine or get access to a installed machine
  2. Click through the system and various applications, to mimic user behavior
  3. Leave the system running for a few more minutes, if possible hours
"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Desktop/#expected-results","title":"Expected Results","text":"
  1. Open the SETroubleshoot Application and invoke the error summarization.
  2. There must not be shown any errors / denials
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Server/","title":"QA:Testcase SELinux Errors on Server installations","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#selinux-errors-server release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Server/#description","title":"Description","text":"

Basically running a text mode installation for a longer amount of time, while using it and then checking if there were any SELinux audit messages.

"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Server/#setup","title":"Setup","text":"

Obtain access to a suitable system with one of the text mode installation base groups.

It might also be beneficial to run this test with other than the core installation, but that is a long term test and a bit out of scope of this test.

"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Server/#how-to-test","title":"How to test","text":"
  1. Setup new machine or get access to a installed machine
  2. As this test is mostly about the stability of the core system it is mostly only needed to let the system run for a few minutes, if possible hours
"},{"location":"documentation/QA/Testcase_Post_SELinux_Errors_Server/#expected-results","title":"Expected Results","text":"
  1. Install sealert with dnf install setroubleshoot-server
  2. Run sealert -a /var/log/audit/audit.log
  3. There must not be shown any errors / denials
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Post_System_Services/","title":"QA:Testcase System Services","text":"

Release relevance

This Testcase applies the following versions of Rocky Linux: 8, 9

Associated release criterion

This test case is associated with the Release_Criteria#system-services release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Post_System_Services/#description","title":"Description","text":"

This test covers the check, that all basic system service which are getting installed with the base groups are starting / running normally.

"},{"location":"documentation/QA/Testcase_Post_System_Services/#setup","title":"Setup","text":"
  1. Acquire access to either a baremetal machine or a VM host, to install a new machine
  2. Prepare appropriate media for the selected ISO to be tested.
"},{"location":"documentation/QA/Testcase_Post_System_Services/#how-to-test","title":"How to test","text":"

Startup the system and check that all services are running without any failure:

systemctl status\n
"},{"location":"documentation/QA/Testcase_Post_System_Services/#expected-results","title":"Expected Results","text":"

The tests during the process could be successfully finished.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Repo_Compare/","title":"QA:Testcase Media Repo Compare","text":"

Associated release criterion

This test case is associated with the Release_Criteria#repositories-must-match-upstream release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Repo_Compare/#description","title":"Description","text":"

This test case will verify that repositories and the packages within them match upstream as closely as possible.

"},{"location":"documentation/QA/Testcase_Repo_Compare/#setup","title":"Setup","text":"
  1. Verify access to the Rocky Linux repocompare tooling.
"},{"location":"documentation/QA/Testcase_Repo_Compare/#how-to-test","title":"How to test","text":"
  1. Access Rocky Linux repocompare website.
  2. Verify similarity of Rocky Linux repositories with upstream content.
"},{"location":"documentation/QA/Testcase_Repo_Compare/#expected-results","title":"Expected Results","text":"
  1. Rocky Linux repositories should match, as closely as possible, upstream repositories.
  2. The content of Rocky Linux packages should match, as closely as possible, upstream repositories.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Storage_Volume_Resize/","title":"QA:Testcase Storage Volume Resize","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Storage Volume Resize release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Storage_Volume_Resize/#description","title":"Description","text":"

This test case verifies that the installer will successfully resize or delete and overwrite existing partitions on storage volumes.

DATA LOSS

Depending on installer choices this MAY destroy all the data on the test system. If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Storage_Volume_Resize/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
"},{"location":"documentation/QA/Testcase_Storage_Volume_Resize/#how-to-test","title":"How to test","text":""},{"location":"documentation/QA/Testcase_Storage_Volume_Resize/#resize","title":"Resize","text":"
  1. From the Installation Destination spoke, in the Storage Configuration section, select the Custom radio button, then click Done.
  2. Expand the list of available partitions by clicking the black arrow to the left of the release version and architecture.
  3. Select the partition you wish to resize. Be sure to uncheck the Reformat checkbox if you wish to resize without reformatting the partition.
  4. Click the Update Settings button to save your settings.
  5. Click the + button to create a new partition off of the existing partition. Provide a mount point and desired capacity, then click Add Mount Point.
  6. Repeat as necessary for additional partitions, or click Done to return to the Anaconda main hub.
"},{"location":"documentation/QA/Testcase_Storage_Volume_Resize/#delete","title":"Delete","text":"
  1. From the Installation Destination spoke, in the Storage Configuration section, select the Automatic radio button, then click Done.
  2. You should be presented with an \"Installation Options\" dialog, indicating the amount of disk space that is available for use and available to reclaim.
  3. Click the Reclaim Space button.
  4. Select a partition, then click the Delete button to delete the partition and reclaim the space.
  5. Alternatively, click the Delete All button to delete all existing partitions.
  6. When you have finished, click the Reclaim Space button to reclaim available free space.
"},{"location":"documentation/QA/Testcase_Storage_Volume_Resize/#expected-results","title":"Expected Results","text":"
  1. The installation should complete and boot successfully.
  2. Resized partitions should correctly reflect the desired size. This may be verified using the lsblk command.
  3. Deleted partitions should no longer exist.
"},{"location":"documentation/QA/Testcase_Storage_Volume_Resize/#testing-in-openqa","title":"Testing in openQA","text":"

The following openQA test suites satisfy this release criteria:

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Template/","title":"QA:Testcase Template","text":"

Associated release criterion

This test case is associated with the Release_Criteria#TBD release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Template/#description","title":"Description","text":"

Add a short description here for this Testcase.

"},{"location":"documentation/QA/Testcase_Template/#setup","title":"Setup","text":"
  1. Add steps for setup for this Testcase.
"},{"location":"documentation/QA/Testcase_Template/#how-to-test","title":"How to test","text":"
  1. Do this first...
  2. Then do this...
"},{"location":"documentation/QA/Testcase_Template/#expected-results","title":"Expected Results","text":"
  1. This is what you should see/verify.
  2. You should also see/verify this.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_Update_Image/","title":"QA:Testcase Update Image","text":"

Associated release criterion

This test case is associated with the Release_Criteria#Update Image release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_Update_Image/#description","title":"Description","text":"

This test case verifies that an update image can be loaded into Anaconda and applied during the install process.

DATA LOSS

Depending on installer choices this MAY destroy all the data on the test system. If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_Update_Image/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Boot the system from the prepared optical, USB media or virtual device attachment.
  4. In the boot menu select the appropriate option to boot the installer.
  5. Hit the Tab key to edit the boot command
"},{"location":"documentation/QA/Testcase_Update_Image/#how-to-test","title":"How to test","text":"
  1. Supply inst.updates=https://fedorapeople.org/groups/qa/updates/updates-openqa.img to the GRUB command line
  2. Boot into the installer as usual.
  3. In Anaconda, open the Installation Destination spoke.
"},{"location":"documentation/QA/Testcase_Update_Image/#expected-results","title":"Expected Results","text":"
  1. Within the Installation Destination spoke, the selected install disk should have a pink background
FAILPASS
  1. If you cannot verify visually, check for the existence of /tmp/updates, which should contain updated source files if the update was successfully applied. Note that if the update image doesn't actually contain any source files, this directory will not be created.
"},{"location":"documentation/QA/Testcase_Update_Image/#testing-with-openqa","title":"Testing with openQA","text":"

The following openQA test suites satisfy this release criteria:

"},{"location":"documentation/QA/Testcase_Update_Image/#additional-references","title":"Additional References","text":"

Red Hat Debug Boot Options Fedora QA:Testcase Anaconda updates.img via URL Fedora QA:Testcase Anaconda updates.img via local media

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/QA/Testcase_VNC_Graphics_Mode/","title":"QA:Testcase VNC Graphics Mode","text":"

Associated release criterion

This test case is associated with the Release_Criteria#vnc-graphics-mode-behaviors release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.

"},{"location":"documentation/QA/Testcase_VNC_Graphics_Mode/#description","title":"Description","text":"

This test case will verify that release-blocking installers function as intended using the VNC installation method on supported systems and classes of hardware.

Supported Systems and Hardware Classes x86_64aarch64ppc64s309x

TBD

TBD

TBD

TBD

"},{"location":"documentation/QA/Testcase_VNC_Graphics_Mode/#setup","title":"Setup","text":"
  1. Obtain access to supported system and hardware class to be installed.
  2. Prepare appropriate media for the selected ISO to be tested.
  3. Obtain access to remote system with a VNC client installed to use for VNC connection.

Suggested VNC Clients

Both tigervnc and vinagre are VNC clients provided in Rocky Linux but any VNC client may be used.

"},{"location":"documentation/QA/Testcase_VNC_Graphics_Mode/#how-to-test","title":"How to test","text":"
  1. Boot the system from the prepared optical, USB media or virtual device attachment.
  2. Interrupt the kernel boot and specify the appropriate VNC installation option on the boot command line.
  3. Proceed with installation on the test system.Depending on installer choices this MAY destroy all the data on the test system.
  4. Depending on the choice or direct or connect mode connect inbound to the system under test or wait for it to connect to your listening VNC client.

DATA LOSS

If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.

"},{"location":"documentation/QA/Testcase_VNC_Graphics_Mode/#expected-results","title":"Expected Results","text":"
  1. Connection to (with direct mode) or from (in connect mode) to the Anaconda installer using VNC is possible.
  2. Anaconda installer presents a usable graphical intallation environment.
  3. System under test can be installed normally.
  4. After reboot system boots into graphical environment.
  5. After login user is able to operate the graphical environment.
Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Quality Assurance documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"documentation/dev_guides/commit_signing/","title":"Creating your primary keypair","text":"

  1. Initiate the keypair generation wizard

    gpg --full-generate-key --expert\n

  2. Select option (9) ECC and ECC for the key type

  3. Select option (1) Curve 25519 for the elliptic curve
  4. Set a validity period of your choice, ideally less than 1 year
  5. Specify real name and email address to associate with this keypair. The email address must match your verified Github email address or be set to your-github-username@users.noreply.github.com.
  6. Type a passphrase (twice)
"},{"location":"documentation/dev_guides/commit_signing/#create-a-signing-keypair","title":"Create a signing keypair","text":"

  1. Add a signing subkey

    gpg --expert --edit-key my@email.addr\ngpg> addkey\n

  2. Select option (10) ECC (sign only) for the key type

  3. Select option (1) Curve 25519 for the elliptic curve
  4. Set a validity period of your choice, ideally less than 1 year
  5. Accept the prompts and type a passphrase (twice)
  6. Save and exit
    gpg> save\n
"},{"location":"documentation/dev_guides/commit_signing/#create-revocation-certificate","title":"Create revocation certificate","text":"
gpg --output my_email_addr.gpg-revocation-certificate --gen-revoke my@email.addr\n
"},{"location":"documentation/dev_guides/commit_signing/#back-up-your-keypair","title":"Back up your keypair","text":"

Export the primary keypair (put these somewhere very safe along with revocation certificate)

gpg --export-secret-keys --armor my@email.addr > my_email_addr.private.gpg-key\ngpg --export --armor my@email.addr > my_email_addr.public.gpg-key\n
"},{"location":"documentation/dev_guides/commit_signing/#remove-the-primary-keypair-from-your-keyring","title":"Remove the primary keypair from your keyring","text":"

  1. Export all subkeys from the new keypair to a file

    gpg --export-secret-subkeys my@email.addr > $HOME/.gnupg/subkeys\n

  2. Delete primary key from keyring - BE SURE TO BACK UP YOUR PRIMARY KEYPAIR FIRST!

    gpg --delete-secret-key my@email.addr\n

  3. Re-import the previously exported keys

    gpg --import $HOME/.gnupg/subkeys\n

  4. Look for sec# instead of sec in the output - pound sign means signing subkey is not in the keypair located in the keyring

    gpg --list-secret-keys $HOME/.gnupg/secring.gpg\n
"},{"location":"documentation/dev_guides/commit_signing/#revoking-a-signing-keypair","title":"Revoking a signing keypair","text":"

Find the primary keypair and import it (preferably into an ephemeral system like a liveUSB)

gpg --import /path/to/my_email_addr.public.gpg-key /path/to/my_email_addr.private.gpg-key\ngpg --edit-key my@email.addr\ngpg> revkey\n[ passphrase twice ]\ngpg> save\n
"},{"location":"documentation/dev_guides/commit_signing/#renew-an-expired-or-expiring-keypair","title":"Renew an expired or expiring keypair","text":"
gpg --edit-key my@email.addr\n[select a key]\ngpg> expire\n[specify an expiration]\ngpg> save\n
"},{"location":"documentation/dev_guides/commit_signing/#create-a-single-signed-git-commit","title":"Create a single signed git commit","text":"
git commit -S -m \"my awesome signed commit\"\n
"},{"location":"documentation/dev_guides/commit_signing/#configure-git-to-always-sign-commits-with-a-specified-key","title":"Configure git to always sign commits with a specified key","text":"
$ gpg --list-secret-keys --keyid-format=long # grab the fingerprint from the 'sec' line\ngit config [--global] commit.gpgsign true\ngit config [--global] user.signingkey DEADB33FBAD1D3A\n
"},{"location":"documentation/dev_guides/commit_signing/#configure-vscode-to-sign-commits","title":"Configure VSCode to sign commits","text":"
# User or workspace setting\n\"git.enableCommitSigning\": true\n
"},{"location":"documentation/dev_guides/commit_signing/#upload-your-public-key-to-a-keyserver","title":"Upload your public key to a keyserver","text":"
gpg --keyserver pgp.mit.edu --send-keys 0xDEADB33FBAD1D3A\n
"},{"location":"documentation/dev_guides/commit_signing/#verify-your-key-has-been-published","title":"Verify your key has been published","text":"
gpg --keyserver pgp.mit.edu --search-key my@email.addr\n
"},{"location":"documentation/dev_guides/commit_signing/#references","title":"References","text":"

OpenPGP Best Practices Github: Signing Commits Braincoke's Log: Create a GPG Key Creating the Perfect GPG Keypair Digital Neanderthal: Generate GPG Keys With Curve Ed25519

"},{"location":"documentation/dev_guides/openqa_access/","title":"openQA - Access","text":""},{"location":"documentation/dev_guides/openqa_access/#system-requirements","title":"System Requirements","text":"

To complete any of the examples below you will need access to a system providing the openQA client. Typically that will be a Fedora based system/container with the openqa-client package and it's (~239) dependencies installed.

"},{"location":"documentation/dev_guides/openqa_access/#access-requirement","title":"Access Requirement","text":""},{"location":"documentation/dev_guides/openqa_access/#api-get-access","title":"API GET access","text":"

The Rocky Linux openQA system allows unrestricted public access via it's web interface or using the openqa-client for GET operations against the API.

"},{"location":"documentation/dev_guides/openqa_access/#api-post-access","title":"API POST access","text":"

In order to use the openQA client to interact with the Rocky Linux openQA system for POST operations the following are required:

"},{"location":"documentation/dev_guides/openqa_access/#configuring-your-openqa-client","title":"Configuring your openqa client","text":"

Per the openqa client command help you can configure your client to use your API key in a number of ways.

The following example shows how to configure your client by the most common method used. It's possible to configure multiple openqa client API keys in this way.

$ mkdir -p ~/.config/openqa\n\n$ vim ~/.config/openqa/client.conf\n\n$ cat ~/.config/openqa/client.conf\n[localhost]\nkey = your_localhost_api_key\nsecret = your_localhost_api_secret\n[openqa.rockylinux.org]\nkey = your_api_key\nsecret = your_api_secret\n
"},{"location":"documentation/dev_guides/openqa_access/#testing-your-openqa-client-installation","title":"Testing your openqa client installation","text":"
$ openqa-cli api --host http://openqa.rockylinux.org --pretty jobs/1\n{\n   \"job\" : {\n      \"assets\" : {\n         \"iso\" : [\n            \"Rocky-8.6-x86_64-boot.iso\"\n         ]\n      },\n      \"assigned_worker_id\" : 2,\n      \"blocked_by_id\" : null,\n      \"children\" : {\n         \"Chained\" : [],\n         \"Directly chained\" : [],\n         \"Parallel\" : []\n      },\n      \"clone_id\" : null,\n      \"group\" : \"Rocky\",\n      \"group_id\" : 2,\n      \"has_parents\" : 0,\n      \"id\" : 1,\n      \"name\" : \"rocky-8.6-boot-iso-x86_64-Build-8.6-boot-iso--20221110.223812.0-install_default@64bit\",\n      \"parents\" : {\n         \"Chained\" : [],\n         \"Directly chained\" : [],\n         \"Parallel\" : []\n      },\n      \"parents_ok\" : 1,\n      \"priority\" : 10,\n      \"result\" : \"failed\",\n      \"settings\" : {\n         \"ARCH\" : \"x86_64\",\n         \"ARCH_BASE_MACHINE\" : \"64bit\",\n         \"BACKEND\" : \"qemu\",\n         \"BUILD\" : \"-8.6-boot-iso--20221110.223812.0\",\n         \"DESKTOP\" : \"gnome\",\n         \"DISTRI\" : \"rocky\",\n         \"FLAVOR\" : \"boot-iso\",\n         \"GRUB\" : \"ip=dhcp\",\n         \"HDDSIZEGB\" : \"15\",\n         \"ISO\" : \"Rocky-8.6-x86_64-boot.iso\",\n         \"MACHINE\" : \"64bit\",\n         \"NAME\" : \"00000001-rocky-8.6-boot-iso-x86_64-Build-8.6-boot-iso--20221110.223812.0-install_default@64bit\",\n         \"PACKAGE_SET\" : \"default\",\n         \"PART_TABLE_TYPE\" : \"mbr\",\n         \"POSTINSTALL\" : \"_collect_data\",\n         \"QEMUCPU\" : \"Nehalem\",\n         \"QEMUCPUS\" : \"2\",\n         \"QEMURAM\" : \"3072\",\n         \"QEMUVGA\" : \"virtio\",\n         \"QEMU_VIRTIO_RNG\" : \"1\",\n         \"TEST\" : \"install_default\",\n         \"TEST_SUITE_NAME\" : \"install_default\",\n         \"TEST_TARGET\" : \"ISO\",\n         \"VERSION\" : \"8.6\",\n         \"WORKER_CLASS\" : \"qemu_x86_64\"\n      },\n      \"state\" : \"done\",\n      \"t_finished\" : \"2022-11-10T22:44:19\",\n      \"t_started\" : \"2022-11-10T22:38:12\",\n      \"test\" : \"install_default\"\n   }\n}\n
"},{"location":"documentation/dev_guides/openqa_access/#references","title":"References","text":"

openQA Documentation

Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"documentation/dev_guides/openqa_cli_post_examples/","title":"openqa-cli POST Examples","text":"

This page will provide a brief overview of some basic openqa-cli POST examples.

"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#system-access-requirements","title":"System / Access Requirements","text":"

To complete any of the examples please complete the API POST Access steps outlined in the openQA - Access document.

"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#basic-post","title":"Basic POST","text":"

A basic 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.

"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#flavorboot-iso","title":"FLAVOR=boot-iso","text":"

This first 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 \\\n  DISTRI=rocky FLAVOR=boot-iso VERSION=9.1 CURRREL=9 BUILD=20230409-Rocky-9.1-x86_64.0\n
"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#flavorminimal-iso","title":"FLAVOR=minimal-iso","text":"

This 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 POST the 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 \\\n  DISTRI=rocky FLAVOR=minimal-iso VERSION=8.7 CURRREL=8 BUILD=20230409-Rocky-8.7-x86_64.0\n
"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#flavorpackage-set","title":"FLAVOR=package-set","text":"

This 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 \\\n  DISTRI=rocky FLAVOR=package-set VERSION=9.1 CURRREL=9 BUILD=20230409-Rocky-9.1-x86_64.0\n

These three test suites provide for the minimal testing of all ISOs produced for a given release of Rocky Linux.

"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#advanced-post","title":"Advanced POST","text":"

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:

Standard POSTs for these test suites is very similar to the basic POSTs above and are shown below...

"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#flavordvd-iso","title":"FLAVOR=dvd-iso","text":"
$ openqa-cli api -X POST isos ISO=Rocky-9.1-20221214.1-x86_64-dvd.iso ARCH=x86_64 \\\n  DISTRI=rocky FLAVOR=dvd-iso VERSION=9.1 CURRREL=9 BUILD=20230409-Rocky-9.1-x86_64.0\n
"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#flavoruniversal","title":"FLAVOR=universal","text":"
$ openqa-cli api -X POST isos ISO=Rocky-9.1-20221214.1-x86_64-dvd.iso ARCH=x86_64 \\\n  DISTRI=rocky FLAVOR=universal VERSION=9.1 CURRREL=9 BUILD=20230409-Rocky-9.1-x86_64.0\n
"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#collection-of-test-suites-by-build","title":"Collection of test suites by BUILD","text":"

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...

"},{"location":"documentation/dev_guides/openqa_cli_post_examples/#references","title":"References","text":"

openQA Documentation

Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/","title":"openqa-clone-custom-git-refspec Examples","text":"

This page will provide a brief overview of basic and advanced job cloning using the openqa-clone-custom-git-refspec command.

At a high level openqa-clone-custom-git-refspec can be viewed as a mechanism to test PRs for openQA tests directly in a Rocky Linux openQA instance with making changes to the default configuration. As such, it can support testing of PRs that change test code and needles as long as changes to templates.fif.json are not also required. A combination of openqa-clone-custom-git-refspec and openqa-clone-job (which is actually used by openqa-clone-custom-git-refspec under the hood) can be used for some cases where POST variables are pre-defined in templates.fif.json.

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#system-access-requirements","title":"System / Access Requirements","text":"

To complete any of the examples please complete the API POST Access steps outlined in the openQA - Access document.

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#basic-openqa-clone-custom-git-refspec","title":"Basic openqa-clone-custom-git-refspec","text":"

The following example demonstrates the testing of an open Github pull request in the Rocky Linux openQA production system. The PR only changes test code and does not supply updated needles for the test.

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#github-pr-information","title":"Github PR information","text":"

NOTE: The Github CLI tool (gh) is used to display PR information statically in this guide.

\u279c  os-autoinst-distri-rocky git:(develop) gh pr view 168\nSerial console install #168\nMerged \u2022 AlanMarshall wants to merge 1 commit into develop from serial_console \u2022 about 27 days ago\n+5 -2 \u2022 No checks\nReviewers: akatch (Approved), tcooper (Approved), lumarel (Requested)\nLabels: priority: medium, type: bug, test suite\n\n\n  Network is enabled by default at v9 so requires conditional code to handle multiple versions.\n  Tested for 9.1, 8.7 & 8.8:\n\n    openqa-cli api -X POST isos ISO=Rocky-9.1-20221214.1-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal\n  VERSION=9.1 BUILD=-\"$(date +%Y%m%d.%H%M%S).0\"-9.1-20221214.1-universal TEST=install_serial_console\n    openqa-cli api -X POST isos ISO=Rocky-8.7-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.7 BUILD=-\n  \"$(date +%Y%m%d.%H%M%S).0\"-8.7-20221110-universal TEST=install_serial_console\n    openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.8 BUILD=-\n  \"$(date +%Y%m%d.%H%M%S).0\"-8.8-lookahead-universal TEST=install_serial_console\n\n  Result: Tests pass.\n  Also confirm that all main hub check boxes are checked and user test created prior to start of installation.\n  Fixes Issue #102\n\nView this pull request on GitHub: https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/168\n

Above is the information provided in the original PR and it includes tests performed in Alan's openQA development system. We can rerun failing tests in the Rocky Linux openQA system after identifying an appropriate job ID for each Rocky Linux version we are testing. For this example the openQA WebUI was used to find appropriate test IDs to clone.

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#run-openqa-clone-custom-git-refspec-in-verbose-dry-run-mode","title":"Run openqa-clone-custom-git-refspec in --verbose --dry-run mode","text":"

In practice it is useful to run openqa-clone-custom-git-refspec in --verbose and --dry-run mode to observe it's behavior even for the Basic cases...

$ openqa-clone-custom-git-refspec --verbose --dry-run \\\n    https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/168 \\\n    https://openqa.rockylinux.org/tests/16080 2>&1 | tee pr-168\n

NOTE: The full output of openqa-clone-custom-git-refspece will not be shown here.

+ shift\n+ true\n+ case \"$1\" in\n+ dry_run=true\n+ shift\n+ true\n+ case \"$1\" in\n+ shift\n+ break\n+ job_list=https://openqa.rockylinux.org/tests/16080\n+ [[ -z '' ]]\n+ first_arg=https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/168\n+ [[ https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/168 == *\\p\\u\\l\\l* ]]\n+ pr_url=https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/168\n+ target_repo_part=https://github.com/rocky-linux/os-autoinst-distri-rocky\n+ pr=168\n+ pr=168\n+ [[ -z '' ]]\n+ pr_url=https://api.github.com/repos/rocky-linux/os-autoinst-distri-rocky/pulls/168\n++ eval 'curl -s https://api.github.com/repos/rocky-linux/os-autoinst-distri-rocky/pulls/168'\n+++ curl -s https://api.github.com/repos/rocky-linux/os-autoinst-distri-rocky/pulls/168\n\n...<snip>...\n\n++ jq -r '.NEEDLES_DIR | select (.!=null)'\n+ old_needledir=\n+ local needles_dir=\n+ needles_dir=rocky/needles\n+ local repo_branch=AlanMarshall/os-autoinst-distri-rocky#serial_console\n+ local test_suffix=@AlanMarshall/os-autoinst-distri-rocky#serial_console\n+ local build=AlanMarshall/os-autoinst-distri-rocky#168\n+ local casedir=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#serial_console\n+ local GROUP=0\n+ local dry_run=true\n+ local scriptdir\n++ dirname /usr/bin/openqa-clone-custom-git-refspec\n+ scriptdir=/usr/bin\n+ local 'cmd=true /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance \"https://openqa.rockylinux.org\" \"15973\" _GROUP=\"0\" TEST+=\"@AlanMarshall/os-autoinst-distri-rocky#serial_console\" BUILD=\"AlanMarshall/os-autoinst-distri-rocky#168\" CASEDIR=\"https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#serial_console\" PRODUCTDIR=\"os-autoinst-distri-rocky\" NEEDLES_DIR=\"rocky/needles\"'\n+ [[ 0 -ne 0 ]]\n+ [[ -n '' ]]\n+ eval 'true /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance \"https://openqa.rockylinux.org\" \"15973\" _GROUP=\"0\" TEST+=\"@AlanMarshall/os-autoinst-distri-rocky#serial_console\" BUILD=\"AlanMarshall/os-autoinst-distri-rocky#168\" CASEDIR=\"https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#serial_console\" PRODUCTDIR=\"os-autoinst-distri-rocky\" NEEDLES_DIR=\"rocky/needles\"'\n++ true /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance https://openqa.rockylinux.org 15973 _GROUP=0 TEST+=@AlanMarshall/os-autoinst-distri-rocky#serial_console BUILD=AlanMarshall/os-autoinst-distri-rocky#168 CASEDIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#serial_console PRODUCTDIR=os-autoinst-distri-rocky NEEDLES_DIR=rocky/needles\n

What can be seen from the complete --dry-run output for openqa-clone-custom-git-refspec is that both the job to be cloned and the PR to be used are inspected and a openqa-clone-job command is generated to be submitted to the openQA system the job is being cloned on.

Without using --dry-run the final openqa-clone-job command shown above will be run causing the job of interest to be cloned with additional POST variables that will cause the repository/branch referenced in the PR to be cloned into the test directory with important files referenced in the cloned job.

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#run-openqa-clone-custom-git-refspec-without-verbose-dry-run-mode","title":"Run openqa-clone-custom-git-refspec without --verbose --dry-run mode...","text":"
$ openqa-clone-custom-git-refspec \\\n    https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/168 \\\n    https://openqa.rockylinux.org/tests/16080\nCreated job #16119: rocky-9.1-universal-x86_64-Build20230329-Rocky-9.1-x86_64.0-install_serial_console@64bit -> https://openqa.rockylinux.org/t16119\n
"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#cloned-job-information","title":"Cloned job information...","text":"
$ openqa-cli api jobs/16119 --pretty\n{\n   \"job\" : {\n      \"assets\" : {\n         \"iso\" : [\n            \"Rocky-9.1-20221214.1-x86_64-dvd.iso\"\n         ]\n      },\n      \"assigned_worker_id\" : 5,\n      \"blocked_by_id\" : null,\n      \"children\" : {\n         \"Chained\" : [],\n         \"Directly chained\" : [],\n         \"Parallel\" : []\n      },\n      \"clone_id\" : 16121,\n      \"group_id\" : null,\n      \"has_parents\" : 0,\n      \"id\" : 16119,\n      \"name\" : \"rocky-9.1-universal-x86_64-BuildAlanMarshall_os-autoinst-distri-rocky_168-install_serial_console@AlanMarshall_os-autoinst-distri-rocky_serial_console@64bit\",\n      \"parents\" : {\n         \"Chained\" : [],\n         \"Directly chained\" : [],\n         \"Parallel\" : []\n      },\n      \"parents_ok\" : 1,\n      \"priority\" : 10,\n      \"reason\" : \"isotovideo abort: isotovideo received signal TERM\",\n      \"result\" : \"user_restarted\",\n      \"settings\" : {\n         \"ANACONDA_TEXT\" : \"1\",\n         \"ARCH\" : \"x86_64\",\n         \"ARCH_BASE_MACHINE\" : \"64bit\",\n         \"BACKEND\" : \"qemu\",\n         \"BUILD\" : \"AlanMarshall\\/os-autoinst-distri-rocky#168\",\n         \"CASEDIR\" : \"https:\\/\\/github.com\\/AlanMarshall\\/os-autoinst-distri-rocky.git#serial_console\",\n         \"CLONED_FROM\" : \"https:\\/\\/openqa.rockylinux.org\\/tests\\/15973\",\n         \"CURRREL\" : \"9\",\n         \"DISTRI\" : \"rocky\",\n         \"FLAVOR\" : \"universal\",\n         \"HDDSIZEGB\" : \"15\",\n         \"ISO\" : \"Rocky-9.1-20221214.1-x86_64-dvd.iso\",\n         \"LOCATION\" : \"https:\\/\\/download.rockylinux.org\\/pub\\/rocky\\/9.1\\/BaseOS\",\n         \"MACHINE\" : \"64bit\",\n         \"NAME\" : \"00016119-rocky-9.1-universal-x86_64-BuildAlanMarshall_os-autoinst-distri-rocky_168-install_serial_console@AlanMarshall_os-autoinst-distri-rocky_serial_console@64bit\",\n         \"NEEDLES_DIR\" : \"rocky\\/needles\",\n         \"NICTYPE_USER_OPTIONS\" : \"net=172.16.2.0\\/24\",\n         \"NO_UEFI_POST\" : \"1\",\n         \"PART_TABLE_TYPE\" : \"mbr\",\n         \"PRODUCTDIR\" : \"os-autoinst-distri-rocky\",\n         \"QEMUCPU\" : \"Nehalem\",\n         \"QEMUCPUS\" : \"2\",\n         \"QEMURAM\" : \"2048\",\n         \"QEMU_HOST_IP\" : \"172.16.2.2\",\n         \"QEMU_VIDEO_DEVICE\" : \"virtio-vga\",\n         \"QEMU_VIRTIO_RNG\" : \"1\",\n         \"SERIAL_CONSOLE\" : \"1\",\n         \"TEST\" : \"install_serial_console@AlanMarshall\\/os-autoinst-distri-rocky#serial_console\",\n         \"TEST_SUITE_NAME\" : \"install_serial_console\",\n         \"TEST_TARGET\" : \"ISO\",\n         \"VERSION\" : \"9.1\",\n         \"VIRTIO_CONSOLE_NUM\" : \"2\",\n         \"WORKER_CLASS\" : \"qemu_x86_64\",\n         \"XRES\" : \"1024\",\n         \"YRES\" : \"768\"\n      },\n      \"state\" : \"done\",\n      \"t_finished\" : \"2023-03-29T06:19:37\",\n      \"t_started\" : \"2023-03-29T06:12:26\",\n      \"test\" : \"install_serial_console@AlanMarshall\\/os-autoinst-distri-rocky#serial_console\"\n   }\n}\n
"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#advanced-openqa-clone-custom-git-refspec","title":"Advanced openqa-clone-custom-git-refspec","text":"

The following example demonstrates the testing of an open Github pull request in the Rocky Linux openQA production system. The PR changes test code and supplies updated needles for the test.

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#github-pr-information_1","title":"Github PR information","text":"
\u279c  os-autoinst-distri-rocky git:(nazunalika/develop) gh pr view 162\n\nAnaconda text install #162\nOpen \u2022 AlanMarshall wants to merge 2 commits into develop from anaconda-txt \u2022 about 1 day ago\n+30 -5 \u2022 No checks\nReviewers: akatch (Approved), lumarel (Requested), tcooper (Requested)\nLabels: priority: medium, type: bug, test suite\n\n\n  Added new needle for text install.\n  Deleted redundant code.\n  Tested for 9.1, 8.7 & 8.8:\n\n    openqa-cli api -X POST isos ISO=Rocky-9.1-20221214.1-x86_64-dvd.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal\n  VERSION=9.1 BUILD=-\"$(date +%Y%m%d.%H%M%S).0\"-9.1-20221214.1-universal TEST=install_anaconda_text\n    openqa-cli api -X POST isos ISO=Rocky-8.7-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.7 BUILD=-\n  \"$(date +%Y%m%d.%H%M%S).0\"-8.7-20221110-universal TEST=install_anaconda_text\n    openqa-cli api -X POST isos ISO=Rocky-8.8-x86_64-dvd1.iso ARCH=x86_64 DISTRI=rocky FLAVOR=universal VERSION=8.8 BUILD=-\n  \"$(date +%Y%m%d.%H%M%S).0\"-8.8-lookahead-universal TEST=install_anaconda_text\n\n  Result: Pass\n  Fixes Issue #145\n\n\nakatch approved (Member) \u2022 18h \u2022 Newest comment\n\n  All indicated tests pass.\n\n\nView this pull request on GitHub: https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/162\n
"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#run-openqa-clone-custom-git-refspec-in-verbose-dry-run-mode_1","title":"Run openqa-clone-custom-git-refspec in --verbose --dry-run mode","text":"
$ openqa-clone-custom-git-refspec --verbose --dry-run https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/162 https://openqa.rockylinux.org/tests/13371\n+ shift\n+ true\n+ case \"$1\" in\n+ dry_run=true\n+ shift\n+ true\n+ case \"$1\" in\n+ shift\n+ break\n+ job_list=https://openqa.rockylinux.org/tests/13371\n+ [[ -z '' ]]\n+ first_arg=https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/162\n+ [[ https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/162 == *\\p\\u\\l\\l* ]]\n+ pr_url=https://github.com/rocky-linux/os-autoinst-distri-rocky/pull/162\n+ target_repo_part=https://github.com/rocky-linux/os-autoinst-distri-rocky\n\n\n...<snip>...\n\n++ jq -r '.NEEDLES_DIR | select (.!=null)'\n+ old_needledir=\n+ local needles_dir=\n+ needles_dir=rocky/needles\n+ local repo_branch=AlanMarshall/os-autoinst-distri-rocky#anaconda-txt\n+ local test_suffix=@AlanMarshall/os-autoinst-distri-rocky#anaconda-txt\n+ local build=AlanMarshall/os-autoinst-distri-rocky#162\n+ local casedir=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt\n+ local GROUP=0\n+ local dry_run=true\n+ local scriptdir\n++ dirname /usr/bin/openqa-clone-custom-git-refspec\n+ scriptdir=/usr/bin\n+ local 'cmd=true /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance \"https://openqa.rockylinux.org\" \"13371\" _GROUP=\"0\" TEST+=\"@AlanMarshall/os-autoinst-distri-rocky#anaconda-txt\" BUILD=\"AlanMarshall/os-autoinst-distri-rocky#162\" CASEDIR=\"https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt\" PRODUCTDIR=\"os-autoinst-distri-rocky\" NEEDLES_DIR=\"rocky/needles\"'\n+ [[ 0 -ne 0 ]]\n+ [[ -n '' ]]\n+ eval 'true /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance \"https://openqa.rockylinux.org\" \"13371\" _GROUP=\"0\" TEST+=\"@AlanMarshall/os-autoinst-distri-rocky#anaconda-txt\" BUILD=\"AlanMarshall/os-autoinst-distri-rocky#162\" CASEDIR=\"https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt\" PRODUCTDIR=\"os-autoinst-distri-rocky\" NEEDLES_DIR=\"rocky/needles\"'\n++ true /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance https://openqa.rockylinux.org 13371 _GROUP=0 TEST+=@AlanMarshall/os-autoinst-distri-rocky#anaconda-txt BUILD=AlanMarshall/os-autoinst-distri-rocky#162 CASEDIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt PRODUCTDIR=os-autoinst-distri-rocky NEEDLES_DIR=rocky/needles\n

This PR provides updated needles and the default behavior of openqa-clone-custom-git-refspec is to not provide an alternate location for NEEDLES. The --verbose --dry-run output needs to be modified to ensure the needles provided in the PR are used in the test.

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#modify-verbose-dry-run-output-to-point-to-needles-in-the-pr","title":"Modify --verbose --dry-run output to point to needles in the PR...","text":"

Use output to modify clone job...

"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#original","title":"original","text":"
$ /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance https://openqa.rockylinux.org \\\n  13371 _GROUP=0 TEST+=@AlanMarshall/os-autoinst-distri-rocky#anaconda-txt \\\n  BUILD=AlanMarshall/os-autoinst-distri-rocky#162 CASEDIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt \\\n  PRODUCTDIR=os-autoinst-distri-rocky\nNEEDLES_DIR=rocky/needles\n
"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#specify-needles_dir-manually-pointing-at-pr-branch","title":"specify NEEDLES_DIR manually pointing at PR branch","text":"
$ /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance https://openqa.rockylinux.org \\\n  13371 _GROUP=0 TEST+=@AlanMarshall/os-autoinst-distri-rocky#anaconda-txt \\\n  BUILD=AlanMarshall/os-autoinst-distri-rocky#162 CASEDIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt \\\n  PRODUCTDIR=os-autoinst-distri-rocky NEEDLES_DIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt/needles\n
"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#rocky-linux-91","title":"Rocky Linux 9.1","text":"
$ /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance https://openqa.rockylinux.org \\\n  13255 _GROUP=0 TEST+=@AlanMarshall/os-autoinst-distri-rocky#anaconda-txt \\\n  BUILD=AlanMarshall/os-autoinst-distri-rocky#162 CASEDIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt \\\n  PRODUCTDIR=os-autoinst-distri-rocky NEEDLES_DIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt/needles\nCreated job #14228: rocky-9.1-universal-x86_64-Build20230319-Rocky-9.1-x86_64.0-install_anaconda_text@64bit -> https://openqa.rockylinux.org/t14228\n
$ openqa-cli api jobs/14228 --pretty\n{\n   \"job\" : {\n      \"assets\" : {\n         \"iso\" : [\n            \"Rocky-9.1-20221214.1-x86_64-dvd.iso\"\n         ]\n      },\n      \"assigned_worker_id\" : 9,\n      \"blocked_by_id\" : null,\n      \"children\" : {\n         \"Chained\" : [],\n         \"Directly chained\" : [],\n         \"Parallel\" : []\n      },\n      \"clone_id\" : null,\n      \"group_id\" : null,\n      \"has_parents\" : 0,\n      \"id\" : 14228,\n      \"name\" : \"rocky-9.1-universal-x86_64-BuildAlanMarshall_os-autoinst-distri-rocky_162-install_anaconda_text@AlanMarshall_os-autoinst-distri-rocky_anaconda-txt@64bit\",\n      \"parents\" : {\n         \"Chained\" : [],\n         \"Directly chained\" : [],\n         \"Parallel\" : []\n      },\n      \"parents_ok\" : 1,\n      \"priority\" : 0,\n      \"result\" : \"passed\",\n      \"settings\" : {\n         \"ANACONDA_TEXT\" : \"1\",\n         \"ARCH\" : \"x86_64\",\n         \"ARCH_BASE_MACHINE\" : \"64bit\",\n         \"BACKEND\" : \"qemu\",\n         \"BUILD\" : \"AlanMarshall\\/os-autoinst-distri-rocky#162\",\n         \"CASEDIR\" : \"https:\\/\\/github.com\\/AlanMarshall\\/os-autoinst-distri-rocky.git#anaconda-txt\",\n         \"CLONED_FROM\" : \"https:\\/\\/openqa.rockylinux.org\\/tests\\/13255\",\n         \"CURRREL\" : \"9\",\n         \"DISTRI\" : \"rocky\",\n         \"FLAVOR\" : \"universal\",\n         \"HDDSIZEGB\" : \"15\",\n         \"ISO\" : \"Rocky-9.1-20221214.1-x86_64-dvd.iso\",\n         \"LOCATION\" : \"https:\\/\\/dl.rockylinux.org\\/pub\\/rocky\\/9.1\",\n         \"MACHINE\" : \"64bit\",\n         \"NAME\" : \"00014228-rocky-9.1-universal-x86_64-BuildAlanMarshall_os-autoinst-distri-rocky_162-install_anaconda_text@AlanMarshall_os-autoinst-distri-rocky_anaconda-txt@64bit\",\n         \"NEEDLES_DIR\" : \"https:\\/\\/github.com\\/AlanMarshall\\/os-autoinst-distri-rocky.git#anaconda-txt\\/needles\",\n         \"NICTYPE_USER_OPTIONS\" : \"net=172.16.2.0\\/24\",\n         \"PART_TABLE_TYPE\" : \"mbr\",\n         \"PRODUCTDIR\" : \"os-autoinst-distri-rocky\",\n         \"QEMUCPU\" : \"Nehalem\",\n         \"QEMUCPUS\" : \"2\",\n         \"QEMURAM\" : \"2048\",\n         \"QEMU_HOST_IP\" : \"172.16.2.2\",\n         \"QEMU_VIDEO_DEVICE\" : \"virtio-vga\",\n         \"QEMU_VIRTIO_RNG\" : \"1\",\n         \"TEST\" : \"install_anaconda_text@AlanMarshall\\/os-autoinst-distri-rocky#anaconda-txt\",\n         \"TEST_SUITE_NAME\" : \"install_anaconda_text\",\n         \"TEST_TARGET\" : \"ISO\",\n         \"VERSION\" : \"9.1\",\n         \"WORKER_CLASS\" : \"qemu_x86_64\",\n         \"XRES\" : \"1024\",\n         \"YRES\" : \"768\"\n      },\n      \"state\" : \"done\",\n      \"t_finished\" : \"2023-03-22T05:28:28\",\n      \"t_started\" : \"2023-03-22T05:07:09\",\n      \"test\" : \"install_anaconda_text@AlanMarshall\\/os-autoinst-distri-rocky#anaconda-txt\"\n   }\n}\n
"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#rocky-linux-87","title":"Rocky Linux 8.7","text":"
$ /usr/bin/openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance https://openqa.rockylinux.org \\\n  13371 _GROUP=0 TEST+=@AlanMarshall/os-autoinst-distri-rocky#anaconda-txt \\\n  BUILD=AlanMarshall/os-autoinst-distri-rocky#162 CASEDIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt \\\n  PRODUCTDIR=os-autoinst-distri-rocky NEEDLES_DIR=https://github.com/AlanMarshall/os-autoinst-distri-rocky.git#anaconda-txt/needles\nCreated job #14229: rocky-8.7-universal-x86_64-Build20230319-Rocky-8.7-x86_64.0-install_anaconda_text@64bit -> https://openqa.rockylinux.org/t14229\n
$ openqa-cli api jobs/14229 --pretty\n{\n   \"job\" : {\n      \"assets\" : {\n         \"iso\" : [\n            \"Rocky-8.7-x86_64-dvd1.iso\"\n         ]\n      },\n      \"assigned_worker_id\" : 8,\n      \"blocked_by_id\" : null,\n      \"children\" : {\n         \"Chained\" : [],\n         \"Directly chained\" : [],\n         \"Parallel\" : []\n      },\n      \"clone_id\" : null,\n      \"group_id\" : null,\n      \"has_parents\" : 0,\n      \"id\" : 14229,\n      \"name\" : \"rocky-8.7-universal-x86_64-BuildAlanMarshall_os-autoinst-distri-rocky_162-install_anaconda_text@AlanMarshall_os-autoinst-distri-rocky_anaconda-txt@64bit\",\n      \"parents\" : {\n         \"Chained\" : [],\n         \"Directly chained\" : [],\n         \"Parallel\" : []\n      },\n      \"parents_ok\" : 1,\n      \"priority\" : 0,\n      \"result\" : \"passed\",\n      \"settings\" : {\n         \"ANACONDA_TEXT\" : \"1\",\n         \"ARCH\" : \"x86_64\",\n         \"ARCH_BASE_MACHINE\" : \"64bit\",\n         \"BACKEND\" : \"qemu\",\n         \"BUILD\" : \"AlanMarshall\\/os-autoinst-distri-rocky#162\",\n         \"CASEDIR\" : \"https:\\/\\/github.com\\/AlanMarshall\\/os-autoinst-distri-rocky.git#anaconda-txt\",\n         \"CLONED_FROM\" : \"https:\\/\\/openqa.rockylinux.org\\/tests\\/13371\",\n         \"CURRREL\" : \"8\",\n         \"DISTRI\" : \"rocky\",\n         \"FLAVOR\" : \"universal\",\n         \"HDDSIZEGB\" : \"15\",\n         \"ISO\" : \"Rocky-8.7-x86_64-dvd1.iso\",\n         \"LOCATION\" : \"https:\\/\\/dl.rockylinux.org\\/pub\\/rocky\\/8.7\",\n         \"MACHINE\" : \"64bit\",\n         \"NAME\" : \"00014229-rocky-8.7-universal-x86_64-BuildAlanMarshall_os-autoinst-distri-rocky_162-install_anaconda_text@AlanMarshall_os-autoinst-distri-rocky_anaconda-txt@64bit\",\n         \"NEEDLES_DIR\" : \"https:\\/\\/github.com\\/AlanMarshall\\/os-autoinst-distri-rocky.git#anaconda-txt\\/needles\",\n         \"NICTYPE_USER_OPTIONS\" : \"net=172.16.2.0\\/24\",\n         \"PART_TABLE_TYPE\" : \"mbr\",\n         \"PRODUCTDIR\" : \"os-autoinst-distri-rocky\",\n         \"QEMUCPU\" : \"Nehalem\",\n         \"QEMUCPUS\" : \"2\",\n         \"QEMURAM\" : \"2048\",\n         \"QEMU_HOST_IP\" : \"172.16.2.2\",\n         \"QEMU_VIDEO_DEVICE\" : \"virtio-vga\",\n         \"QEMU_VIRTIO_RNG\" : \"1\",\n         \"TEST\" : \"install_anaconda_text@AlanMarshall\\/os-autoinst-distri-rocky#anaconda-txt\",\n         \"TEST_SUITE_NAME\" : \"install_anaconda_text\",\n         \"TEST_TARGET\" : \"ISO\",\n         \"VERSION\" : \"8.7\",\n         \"WORKER_CLASS\" : \"qemu_x86_64\",\n         \"XRES\" : \"1024\",\n         \"YRES\" : \"768\"\n      },\n      \"state\" : \"done\",\n      \"t_finished\" : \"2023-03-22T05:31:22\",\n      \"t_started\" : \"2023-03-22T05:10:46\",\n      \"test\" : \"install_anaconda_text@AlanMarshall\\/os-autoinst-distri-rocky#anaconda-txt\"\n   }\n}\n
"},{"location":"documentation/dev_guides/openqa_clone_custom_git_refspec_examples/#references","title":"References","text":"

openQA Documentation

Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"documentation/dev_guides/openqa_clone_job_examples/","title":"openqa-clone-job Examples","text":"

This page will provide a brief overview of basic and advanced job cloning using the openqa-clone-job command.

"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#system-access-requirements","title":"System / Access Requirements","text":"

To complete any of the examples please complete the API POST Access steps outlined in the openQA - Access document.

"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#basic-openqa-clone-job","title":"Basic openqa-clone-job","text":""},{"location":"documentation/dev_guides/openqa_clone_job_examples/#querying-openqa-for-a-specific-test-or-job","title":"Querying openQA for a specific test or job","text":"

First you might want to query the Rocky Linux openQA system for the latest job ID for a specific job or test. The openQA client, hereafter refered to as openqa-cli will allow you to quickly do that via the API. Here is an example...

$ openqa-cli api --host http://openqa.rockylinux.org jobs/overview groupid=0 distri=rocky version=9.1 test=install_default_upload latest=1 | jq '.'\n[\n  {\n    \"id\": 22735,\n    \"name\": \"rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\"\n  }\n]\n

This basically says \"give me the job id and name of the most recent install_default_upload test for Rocky Linux 9.1\".

"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#cloning-a-job-as-is","title":"Cloning a job \"as-is\"","text":"

With that job id in hand you can now clone that job directly to your local openQA development system with...

$ openqa-clone-job --from https://openqa.rockylinux.org --skip-download 22735\nCloning children of rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\nCreated job #23: rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit -> http://localhost/t23\n
"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#basic-job-overview","title":"Basic job overview","text":"

Now you should have the same job running in your local instance...

$ openqa-cli api jobs/overview\n[{\"id\":23,\"name\":\"rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\"}]\n
"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#basic-job-details","title":"Basic job details","text":"
$ openqa-cli api jobs/23 | jq '.'\n{\n  \"job\": {\n    \"assets\": {\n      \"iso\": [\n        \"Rocky-9.1-20221214.1-x86_64-dvd.iso\"\n      ]\n    },\n    \"assigned_worker_id\": 2,\n    \"blocked_by_id\": null,\n    \"children\": {\n      \"Chained\": [],\n      \"Directly chained\": [],\n      \"Parallel\": []\n    },\n    \"clone_id\": null,\n    \"group\": \"Rocky\",\n    \"group_id\": 2,\n    \"has_parents\": 0,\n    \"id\": 23,\n    \"name\": \"rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\",\n    \"parents\": {\n      \"Chained\": [],\n      \"Directly chained\": [],\n      \"Parallel\": []\n    },\n    \"parents_ok\": 1,\n    \"priority\": 50,\n    \"result\": \"none\",\n    \"settings\": {\n      \"ARCH\": \"x86_64\",\n      \"ARCH_BASE_MACHINE\": \"64bit\",\n      \"BACKEND\": \"qemu\",\n      \"BUILD\": \"20230423-Rocky-9.1-x86_64.0\",\n      \"CLONED_FROM\": \"https://openqa.rockylinux.org/tests/22735\",\n      \"CURRREL\": \"9\",\n      \"DEPLOY_UPLOAD_TEST\": \"install_default_upload\",\n      \"DESKTOP\": \"gnome\",\n      \"DISTRI\": \"rocky\",\n      \"FLAVOR\": \"dvd-iso\",\n      \"HDDSIZEGB\": \"15\",\n      \"ISO\": \"Rocky-9.1-20221214.1-x86_64-dvd.iso\",\n      \"LOCATION\": \"https://download.rockylinux.org/pub/rocky/9.1/BaseOS\",\n      \"MACHINE\": \"64bit\",\n      \"NAME\": \"00000023-rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\",\n      \"NICTYPE_USER_OPTIONS\": \"net=172.16.2.0/24\",\n      \"PACKAGE_SET\": \"default\",\n      \"PART_TABLE_TYPE\": \"mbr\",\n      \"POSTINSTALL\": \"_collect_data\",\n      \"QEMUCPU\": \"Nehalem\",\n      \"QEMUCPUS\": \"2\",\n      \"QEMURAM\": \"2048\",\n      \"QEMU_HOST_IP\": \"172.16.2.2\",\n      \"QEMU_VIDEO_DEVICE\": \"virtio-vga\",\n      \"QEMU_VIRTIO_RNG\": \"1\",\n      \"STORE_HDD_1\": \"disk_dvd-iso_64bit.qcow2\",\n      \"TEST\": \"install_default_upload\",\n      \"TEST_SUITE_NAME\": \"install_default_upload\",\n      \"TEST_TARGET\": \"ISO\",\n      \"VERSION\": \"9.1\",\n      \"WORKER_CLASS\": \"qemu_x86_64\",\n      \"XRES\": \"1024\",\n      \"YRES\": \"768\"\n    },\n    \"state\": \"running\",\n    \"t_finished\": null,\n    \"t_started\": \"2023-04-23T03:02:06\",\n    \"test\": \"install_default_upload\"\n  }\n}\n

NOTE: In the above job information you can clearly see the job was cloned from https://openqa.rockylinux.org/tests/22735.

"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#advanced-openqa-clone-job","title":"Advanced openqa-clone-job","text":"

You can, of course, perform more elaborate operations while cloneing a job either from your local instance or from the production instance. Typically, this might be done to modify some of the job POST variables in the cloned job while keeping all other variables unchanged.

"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#changing-variable-during-clone","title":"Changing variable during clone","text":"

Here is an example where the ISO is changed in the cloned job...

$ openqa-clone-job --from https://openqa.rockylinux.org --skip-download 22735 ISO=Rocky-9.1-x86_64-dvd.iso\nCloning children of rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\nCreated job #24: rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit -> http://localhost/t24\n
"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#job-overview","title":"Job overview","text":"
$ openqa-cli api jobs/overview\n[{\"id\":24,\"name\":\"rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\"}]\n
"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#job-details","title":"Job details","text":"
$ openqa-cli api jobs/24 | jq '.'\n{\n  \"job\": {\n    \"assets\": {\n      \"iso\": [\n        \"Rocky-9.1-x86_64-dvd.iso\"\n      ]\n    },\n    \"assigned_worker_id\": 1,\n    \"blocked_by_id\": null,\n    \"children\": {\n      \"Chained\": [],\n      \"Directly chained\": [],\n      \"Parallel\": []\n    },\n    \"clone_id\": null,\n    \"group\": \"Rocky\",\n    \"group_id\": 2,\n    \"has_parents\": 0,\n    \"id\": 24,\n    \"name\": \"rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\",\n    \"parents\": {\n      \"Chained\": [],\n      \"Directly chained\": [],\n      \"Parallel\": []\n    },\n    \"parents_ok\": 1,\n    \"priority\": 50,\n    \"result\": \"none\",\n    \"settings\": {\n      \"ARCH\": \"x86_64\",\n      \"ARCH_BASE_MACHINE\": \"64bit\",\n      \"BACKEND\": \"qemu\",\n      \"BUILD\": \"20230423-Rocky-9.1-x86_64.0\",\n      \"CLONED_FROM\": \"https://openqa.rockylinux.org/tests/22735\",\n      \"CURRREL\": \"9\",\n      \"DEPLOY_UPLOAD_TEST\": \"install_default_upload\",\n      \"DESKTOP\": \"gnome\",\n      \"DISTRI\": \"rocky\",\n      \"FLAVOR\": \"dvd-iso\",\n      \"HDDSIZEGB\": \"15\",\n      \"ISO\": \"Rocky-9.1-x86_64-dvd.iso\",\n      \"LOCATION\": \"https://download.rockylinux.org/pub/rocky/9.1/BaseOS\",\n      \"MACHINE\": \"64bit\",\n      \"NAME\": \"00000024-rocky-9.1-dvd-iso-x86_64-Build20230423-Rocky-9.1-x86_64.0-install_default_upload@64bit\",\n      \"NICTYPE_USER_OPTIONS\": \"net=172.16.2.0/24\",\n      \"PACKAGE_SET\": \"default\",\n      \"PART_TABLE_TYPE\": \"mbr\",\n      \"POSTINSTALL\": \"_collect_data\",\n      \"QEMUCPU\": \"Nehalem\",\n      \"QEMUCPUS\": \"2\",\n      \"QEMURAM\": \"2048\",\n      \"QEMU_HOST_IP\": \"172.16.2.2\",\n      \"QEMU_VIDEO_DEVICE\": \"virtio-vga\",\n      \"QEMU_VIRTIO_RNG\": \"1\",\n      \"STORE_HDD_1\": \"disk_dvd-iso_64bit.qcow2\",\n      \"TEST\": \"install_default_upload\",\n      \"TEST_SUITE_NAME\": \"install_default_upload\",\n      \"TEST_TARGET\": \"ISO\",\n      \"VERSION\": \"9.1\",\n      \"WORKER_CLASS\": \"qemu_x86_64\",\n      \"XRES\": \"1024\",\n      \"YRES\": \"768\"\n    },\n    \"state\": \"running\",\n    \"t_finished\": null,\n    \"t_started\": \"2023-04-23T03:08:03\",\n    \"test\": \"install_default_upload\"\n  }\n}\n
"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#difference-between-basic-and-advanced-openqa-clone-job","title":"Difference between Basic and Advanced openqa-clone-job","text":"

You should notice that the only substantive difference between the two cloned jobs is the ISO that is used to run the install_default_upload test...

$ openqa-cli api jobs/23 | jq '.job.settings.ISO'\n\"Rocky-9.1-20221214.1-x86_64-dvd.iso\"\n\n$ openqa-cli api jobs/24 | jq '.job.settings.ISO'\n\"Rocky-9.1-x86_64-dvd.iso\"\n
"},{"location":"documentation/dev_guides/openqa_clone_job_examples/#references","title":"References","text":"

openQA Documentation

Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"documentation/dev_guides/wiki_development_boxes/","title":"How to create a live system to work on the documentation","text":"

There are several ways how to setup your development environment, here are the currently used once by the testing team:

"},{"location":"documentation/dev_guides/wiki_development_boxes/#vagrant","title":"Vagrant","text":"

For now here is the link to Trevor's vagrant box setup, this might be merged here in the future!

"},{"location":"documentation/dev_guides/wiki_development_boxes/#manual-setup-for-wsl-and-toolbox","title":"Manual setup for WSL and toolbox","text":""},{"location":"documentation/dev_guides/wiki_development_boxes/#wsl-specific","title":"WSL specific","text":"

Create a WSL machine like described here, make sure to give it a name like rocky-wiki.

"},{"location":"documentation/dev_guides/wiki_development_boxes/#toolbox-specific","title":"toolbox specific","text":""},{"location":"documentation/dev_guides/wiki_development_boxes/#container-setup-for-both","title":"Container setup for both","text":"

To develop then, the easiest way is to use VS Code with the Remote - WSL, where you have to open the repo in the container (click on the Remote symbol on the lower left, 'Open folder in WSL...').

For toolbox just place the repo inside your user profile and you will be able to access it with VS Code inside and outside of the toolbox container.

And finally run mkdocs serve 2>&1 | tee ./mkdocs.serve.log in the terminal of this VS Code session. Then you are ready to start changing stuff!

"},{"location":"documentation/dev_guides/wiki_development_boxes/#docker","title":"Docker","text":"

From the root of this repository on a machine with Docker installed, run

docker-compose up\n

When the container finishes starting up, you can access the documentation in your web browser at http://localhost:8000.

Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Release Requirements documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"guidelines/","title":"Guidelines","text":"

This section goes over guidelines that the Testing team has set out for anything related to the infrastructure used for testing Rocky Linux.

All guidelines are listed on the left side of this page.

Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"guidelines/release_criteria/release_criteria/","title":"Rocky Linux Release Status","text":"

The QA and Testing efforts during releases are tracked in online shared documents. After release the status track and go/no-go documents are published here.

Rocky Linux Version Release Criteria QA and Testing Status QA and Testing GO / NO-GO Summary Official Release Date Rocky Linux 8.5 not available not available not available NOVEMBER 15, 2021 Rocky Linux 8.6 AVAILABLE AVAILABLE AVAILABLE MAY 16, 2022 Rocky Linux 9.0 AVAILABLE AVAILABLE AVAILABLE TBD Additional Information ContactDisclaimerLicense

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 info@rockylinux.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.

"},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/","title":"Rocky Linux 8.6 QA and Testing : GO / NO GO Status","text":"

This document summarizes the GO / NO GO Status for Release of Rocky Linux 8.6 from perspective of the QA / Testing efforts. It is based largely on the Release Criteria (https://wiki.rockylinux.org/team/testing/release_criteria/) as was started as an import of that document. If there are differences between the official Release Critieria document and this document the official Release Criteria document will override and this document shall be updated.

As a reminder, the objective of a release (major or minor) is to provide a solid Enterprise Linux release that is suitable to: - Meet the needs of end users - Meet the needs of enterprises big or small

"},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#summary","title":"SUMMARY","text":"Category Proportion Remaining Items TO_CONFIRM 3 / 29 (10%) PASS 25 / 29 (86%) FAIL_NON_BLOCKING 1 / 29 (3%) cloud-images FAIL_BLOCKING 0 / 29 (0%)"},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#sop","title":"SOP","text":"

In this document each requirement is described and status is specified in the title.

Current choices are...

"},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#to_confirm","title":"TO_CONFIRM","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#pass","title":"PASS","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#fail_non_blocking","title":"FAIL_NON_BLOCKING","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#fail_blocking","title":"FAIL_BLOCKING","text":"

In this document criteria status should include who completed the item and generally how it was complete.

Examples...

"},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#initialization-requirements","title":"Initialization Requirements","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#cloud-image-requirements","title":"Cloud Image Requirements","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_go_no_go/#post-installation-requirements","title":"Post-Installation Requirements","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/","title":"Rocky Linux 8.6 QA and Testing Summary","text":"

Last updated: Fri May 13 17:36:41 UTC 2022

"},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#scope","title":"Scope","text":"

This document will record a summary of all QA and Testing results for Rocky Linux 8.6 release. It is only a record of success and/or failure. Solution discussion should take place elsewhere.

"},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#sop","title":"SOP","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#investigate","title":"INVESTIGATE","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#upstream","title":"UPSTREAM","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#fail","title":"FAIL","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#notabug","title":"NOTABUG","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#manual-success-reported-in-mm","title":"Manual success reported in MM","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#openqa-summary","title":"openQA summary","text":""},{"location":"guidelines/release_criteria/r8/8.6_qa_testing_summary/#createhdds-kickstart-file-test-summary","title":"createhdds kickstart file test summary","text":"

Test method: Used packer to build VM. Booted VM. Verified root login. Shutdown VM.

"},{"location":"guidelines/release_criteria/r8/8_release_criteria/","title":"Rocky Linux 8 Final Release Objectives","text":"

The objective of a release (major or minor) is to provide a solid Enterprise Linux release that is suitable to:

"},{"location":"guidelines/release_criteria/r8/8_release_criteria/#rocky-linux-8-final-release-requirements","title":"Rocky Linux 8 Final Release Requirements","text":"

In order for Rocky Linux to be released to the general public, a compose must be able to meet all the following criteria as provided in this document. This is allows the decision process to be straightforward and as clear as possible. This document only contains \u201chard requirement\u201d items. Optional/nice to have items are not to be included in this list.

There may cases where a requirement cannot be met but only in particular configurations. In these types of cases, the Release Engineering Team should use their judgement to determine whether or not the issue should be considered to block the release. They should consider the number of users likely to be affected by said issue, the severity of the case, if the issue can be avoided with ease (by both informed and uninformed users), and if the problem exists upstream in the current Red Hat Enterprise Linux that the release is based on.

Release-blocking Server

...means bugs as it pertains to server functionality can be considered to block a release. This applies to any packages that provide a service such as httpd, nginx, etc. All architectures apply.

Release-blocking Desktop

...means bugs as it pertains to desktop functionality (GNOME) can be considered to block a release. This applies to both x86_64 and aarch64. Additional desktops (as provided by EPEL or a SIG) are not considered blockers.

Release-blocking Image

...means bugs as it pertains to the images built that can block a release. This applies to the DVD, minimal, and boot images on all architectures.

"},{"location":"guidelines/release_criteria/r8/8_release_criteria/#initialization-requirements","title":"Initialization Requirements","text":""},{"location":"guidelines/release_criteria/r8/8_release_criteria/#release-blocking-images-must-boot","title":"Release-blocking images must boot","text":"

Release-blocking installer images must boot when written to optical media or USB flash drive of appropriate sizes (if applicable) via officially supported methods. It is not the testing team\u2019s responsibility to test optical media, but they can and report back. If a bug is found, it is considered a blocker.

Optical Media Requirements

Release-blocking images must boot when written to optical media of an appropriate size. Current size requirements are: boot.iso = 789M, minimal.iso = 2.0G and dvd.iso = 10G.

Officially supported USB flash drive writing methods

The following methods of writing USB flash drives are officially support: dd The following methods of writing USB flash drives are not supported: rufus

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#basic-graphics-mode-behaviors","title":"Basic Graphics Mode behaviors","text":"

The generic video driver option (\u201cbasic graphics mode\u201d) on all release-blocking installers must function as intended. This means launching the installer or desktop and attempting to use a generic driver. There must be no bugs that prevent the installer from being reached in this configuration on all systems and classes of hardware supported by the enterprise linux kernel.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#no-broken-packages","title":"No Broken Packages","text":"

Critical errors, such as undeclared conflicts, unresolved dependencies, or modules relying on packages from another stream will be considered an automatic blocker. There are potential exceptions to this (eg, freeradius cannot be installed on an older perl stream, this is a known issue upstream).

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#repositories-must-match-upstream","title":"Repositories Must Match Upstream","text":"

Repositories and the packages within them should match upstream as closely as possible. Notable exceptions would be kmods, kpatch, or what is deemed as \u201cspyware\u201d like insights. Packages that are available from upstream should not have hard requirements on RHSM and packages that have it default built in should be patched out.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#debranding","title":"Debranding","text":"

Assets and functionality that are Red Hat specific should not be included. If they are not patched out, it will be considered an automatic blocker.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#installer-requirements","title":"Installer Requirements","text":""},{"location":"guidelines/release_criteria/r8/8_release_criteria/#media-consistency-verification","title":"Media Consistency Verification","text":"

This means that the installer\u2019s mechanism for verifying the install medium is intact and must complete successfully, with the assumption that the medium was correctly written. It should return a failure message if this not the case.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#packages-and-installer-sources","title":"Packages and Installer Sources","text":"

The installer must be able to use all supported local/remote packages and installer sources.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#nas-network-attached-storage","title":"NAS (Network Attached Storage)\"","text":"

The installer must be able to detect and install to supported NAS devices (if possible and supported by the kernel).

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#installation-interfaces","title":"Installation Interfaces","text":"

The installer must be able to complete an installation using all supported spokes.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#minimal-installation","title":"Minimal Installation","text":"

A minimal installation (via network) must be able to install the minimal package set.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#kickstart-installation","title":"Kickstart Installation","text":"

A kickstart installation should succeed, whether from optical/USB media or via the network.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#disk-layouts","title":"Disk Layouts","text":"

The installer must be able to create and install to any workable partition layout using any file system or format combination offered or supported by the installer. File systems that are not supported by the EL kernel is not tested here (this means btrfs, zfs, both of wish are not supported).

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#firmware-raid","title":"Firmware RAID","text":"

The installer must be able to detect and install to firmware RAID devices. Note that system-specific bugs do not count as blockers. It is likely that some hardware support might be broken or not available at all. DUDs (driver update disks) are not considered for this criteria.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#bootloader-disk-selection","title":"Bootloader Disk Selection","text":"

The installer must allow the user to choose which disk the bootloader will be installed to or, if the user so chooses, not to install a bootloader.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#storage-volume-resize","title":"Storage Volume Resize","text":"

Any installer mechanism for resizing storage volumes must correctly attempt the requested operation. This means that if the installer offers a way to resize storage volumes, then it must use the correct resizing tool with the correct parameters. However, it does not require the installer to disallow resizing of unformatted or volumes with an unknown filesystem type.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#update-image","title":"Update Image","text":"

The installer must be able to use an installer update image retrieved from removable media or a remote package source. This includes DUDs (driver update disks).

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#installer-help","title":"Installer Help","text":"

Any element in the installer which contains a \u201chelp\u201d text must display the appropriate help documentation when selected.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#installer-translations","title":"Installer Translations","text":"

The installer must correctly display all complete translations that are available for use.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#cloud-image-requirements","title":"Cloud Image Requirements","text":""},{"location":"guidelines/release_criteria/r8/8_release_criteria/#images-published-to-cloud-providers","title":"Images Published to Cloud Providers","text":"

Release-blocking cloud disk images must be published to appropriate cloud providers (such as Amazon) and they must successfully boot. This also applies to KVM based instances, such as x86 and aarch64 systems.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#post-installation-requirements","title":"Post-Installation Requirements","text":""},{"location":"guidelines/release_criteria/r8/8_release_criteria/#system-services","title":"System Services","text":"

All system services present after installation must start properly, with the exception of services that require hardware which is not present. Examples of such services would be:

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#keyboard-layout","title":"Keyboard Layout","text":"

If a particular keyboard layout has been configured for the system, that layout must be used:

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#selinux-errors-server","title":"SELinux Errors (Server)","text":"

There must be no SELinux denial logs in /var/log/audit/audit.log

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#selinux-and-crash-notifications-desktop-only","title":"SELinux and Crash Notifications (Desktop Only)","text":"

There must be no SELinux denial notifications or crash notifications on boot, during installation, or during first login.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#default-application-functionality-desktop-only","title":"Default Application Functionality (Desktop Only)","text":"

Applications that can be launched within GNOME or on the command line must start successfully and withstand basic functionality tests. This includes:

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#default-panel-functionality-desktop-only","title":"Default Panel Functionality (Desktop Only)","text":"

All elements of GNOME should function properly in regular use.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#dual-monitor-setup-desktop-only","title":"Dual Monitor Setup (Desktop Only)","text":"

Computers using two monitors, the graphical output is correctly shown on both monitors.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#artwork-and-assets-server-and-desktop","title":"Artwork and Assets (Server and Desktop)","text":"

Proposed final artwork (such as wallpapers and other assets) must be included. A wallpaper from this package should show up as a default for GDM and GNOME.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#packages-and-module-installation","title":"Packages and Module Installation","text":"

Packages (non-module) should be able to be installed without conflicts or dependent on repositories outside of Rocky Linux.

References "},{"location":"guidelines/release_criteria/r8/8_release_criteria/#identity-management-server-setup","title":"Identity Management Server Setup","text":"

It should be possible to setup a IdM server (FreeIPA), use it's functionality and connect clients.

References Additional Information ContactDisclaimerAttributionLicense

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 testing@rockylinux.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 work is heavily inspired by the Fedora Release Requirements documents which were made available under Attribution-Share Alike 4.0 International license unless otherwise noted.

This content is licensed under under Attribution-Share Alike 4.0 International license unless otherwise noted.

"},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/","title":"Rocky Linux 9 QA and Testing : GO / NO GO Status","text":"

This document summarizes the GO / NO GO Status for Release of Rocky Linux 9.0 from perspective of the QA / Testing efforts. It is based largely on the Release Criteria (https://wiki.rockylinux.org/team/testing/release_criteria/) as was started as an import of that document. If there are differences between the official Release Critieria document and this document the official Release Criteria document will override and this document shall be updated.

As a reminder, the objective of a release (major or minor) is to provide a solid Enterprise Linux release that is suitable to: - Meet the needs of end users - Meet the needs of enterprises big or small

"},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#summary","title":"SUMMARY","text":"Category Proportion Remaining Items TO_CONFIRM 1 / 29 (3%) Firmware RAID PASS 28/ 29 (97%) FAIL_NON_BLOCKING 0 / 29 (0%) FAIL_BLOCKING 0 / 29 (0%)"},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#sop","title":"SOP","text":"

In this document each requirement is described and status is specified in the title.

Current choices are...

"},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#to_confirm","title":"TO_CONFIRM","text":""},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#pass","title":"PASS","text":""},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#fail_non_blocking","title":"FAIL_NON_BLOCKING","text":""},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#fail_blocking","title":"FAIL_BLOCKING","text":"

In this document criteria status should include who completed the item and generally how it was complete.

Examples...

"},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#initialization-requirements","title":"Initialization Requirements","text":""},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#cloud-image-requirements","title":"Cloud Image Requirements","text":""},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_go_no_go/#post-installation-requirements","title":"Post-Installation Requirements","text":""},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_summary/","title":"Rocky Linux 9 QA and Testing Summary","text":"

Last updated:"},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_summary/#scope","title":"Scope","text":"

This document will record a summary of all QA and Testing results for Rocky Linux {{ no such element: dict object[9] }} release. It is only a record of success and/or failure. Solution discussion should take place elsewhere.

"},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_summary/#reference","title":"Reference","text":""},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_summary/#sop","title":"SOP","text":""},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_summary/#investigate","title":"INVESTIGATE","text":"

This is a list of items that are being INVESTIGATEd further before being assigned a PASS, FAIL, NOTABUG or UPSTREAM status. PLEASE add your MM handle if you are working on this item to minimize duplication of work. More than one handle is allowed but please communicate.

"},{"location":"guidelines/release_criteria/r9/9.0_qa_testing_summary/#upstream","title":"UPSTREAM","text":"

This is a list of items that have been verified to be replicated UPSTREAM in RHEL {{ no such element: dict object[9] }} and/or are described clearly in the RHEL 9 Release Notes.