openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-01-20T15:09:49ZopenSUSE Project Management Tool
Redmine qe-yam - action #123460 (Resolved): Provide workaround for iscsi failure bsc#1207157https://progress.opensuse.org/issues/1234602023-01-20T15:09:49Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>iscsi MU tests for 15 SP3 are <a href="https://openqa.suse.de/tests/10349912#step/iscsi_client/68" class="external">failing due to wrong return code</a> (<a href="https://bugzilla.suse.com/show_bug.cgi?id=1207157" class="external">bsc#1207157</a>)<br>
We should apply the workaround suggested <a href="https://bugzilla.suse.com/show_bug.cgi?id=1206132#c12" class="external">here</a> and softfail the tests until a fix is available.</p>
<a name="Scope"></a>
<h3 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h3>
<p>For 15 SP3 MU on Yast job group, tests</p>
<ul>
<li>mru-iscsi_{server..client}_normal_auth_backstore_fileio</li>
<li>mru-iscsi_{server..client}_normal_auth_backstore_hdd</li>
<li>mru-iscsi_{server..client}_normal_auth_backstore_lvm</li>
</ul>
<p>arch x86_64</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Apply simple soft-failure of skip on the point of failure until ticket is complete<br>
<strong>AC2</strong>: Apply workaround to <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/iscsi/iscsi_client.pm" class="external">iscsi_client</a><br>
<strong>AC3</strong>: Softfail the iscsi tests by pointing to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1207157" class="external">bsc#1207157</a></p>
<a name="Additional-information"></a>
<h4 >Additional information<a href="#Additional-information" class="wiki-anchor">¶</a></h4>
<p>The workaround is simple enough.<br>
After <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/iscsi/iscsi_client.pm#L108" class="external">open-iscsi has been installed</a> we need to edit the file <code>/usr/lib/systemd/system/iscsid.service</code>.<br>
At the end of the <code>[Unit]</code> section add</p>
<pre><code>Requires=iscsid.socket
After=iscsid.socket
</code></pre>
<p>Leave the rest of the file as is.<br>
After editing the service file you will need to run <code>systemctl daemon-reload</code>.</p>
qe-yam - action #118966 (Rejected): Testuiste mru-iscsi_{client,server}_normal_auth_backstore_{lv...https://progress.opensuse.org/issues/1189662022-10-17T16:13:22Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Related to <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Add AutoYaST test suites for chained dependencies in YaST Maintenance Updates (rest of products) (Resolved)" href="https://progress.opensuse.org/issues/111743">#111743</a><br>
Testsuites <code>create_hdd_yast_maintenance_desktop</code> and <code>create_hdd_yast_maintenance_minimal</code> are performing an autoyast installation which is used by subsequent testsuites (eg <code>mau-extratests-yast2ui</code>, <code>mau_extratests_yast2_ncurses</code>, <code>mau_extratests_yast_cmd</code>).</p>
<p>However the <code>mru-iscsi</code> multimachine testsuites that have <code>create_hdd_yast_maintenance_desktop</code> as a dependency seem to bump into an issue where the Network of the resulting image is not configured, ending up with <a href="https://openqa.suse.de/tests/9742604#step/addon_products_via_SCC_yast2/25" class="external">this type of failure</a>.</p>
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p><a href="https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=mru-iscsi_client_normal_auth_backstore_lvm_dev&test=mru-iscsi_server_normal_auth_backstore_lvm_dev&test=mru-iscsi_client_normal_auth_backstore_fileio_dev&test=mru-iscsi_server_normal_auth_backstore_fileio_dev&test=mru-iscsi_client_normal_auth_backstore_hdd_dev&test=mru-iscsi_server_normal_auth_backstore_hdd_dev&modules=&module_re=&distri=sle&build=20221016-1&groupid=446#" class="external">mru-iscsi_{client,server}_normal_auth_backstore_{lvm,fileio,hdd}</a> for MU YaST 12-SP4 to 15-SP2 Job groups.<br>
arch: x86_64</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: The mru-iscsi_{client,server}<u>normal_auth_backstore</u>{lvm,fileio,hdd} testsuites succeed on the Registration step.<br>
<strong>AC2</strong>: The mru-iscsi_{client,server}<u>normal_auth_backstore</u>{lvm,fileio,hdd} are removed from the development group, and their equivalent testsuites in the YaST MU Job Groups now have a dependency on the <code>create_hdd_yast_maintenance_desktop</code> testsuite.</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<ul>
<li>This is most probably an AutoYaST profile related issue. The <code>mru-iscsi_{client,server}_normal_auth_backstore_{lvm,fileio,hdd}</code> seem to run fine for <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP3&build=20221016-1&groupid=421" class="external">15-SP3</a> and <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=20221016-1&groupid=421" class="external">15-SP4</a>, maybe it is worth observing how network configuration is done on these autoyast installation <code>create_hdd_yast_maintenance_desktop</code> jobs.</li>
</ul>
qe-yam - action #116128 (Rejected): Rectify unsupported configuration in bootloader settings when...https://progress.opensuse.org/issues/1161282022-09-01T14:20:22Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>When migrating form 15sp4 hpc to 15sp5, the test encounters an unsupported bootloader configuration (unkown udev device), as seen <a href="https://openqa.suse.de/tests/9426332#step/start_install/2" class="external">here</a>. The issue is likely caused by an earlier configuration which would need to be mitigated.</p>
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p>Migration: HPC <a href="https://openqa.suse.de/tests/9426332#step/start_install/2" class="external">https://openqa.suse.de/tests/9426332#step/start_install/2</a> </p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Adjust the test so that bootloader configuration is written to an existing disk.</p>
qe-yam - action #108758 (Closed): Wait for extensions and modules registrationhttps://progress.opensuse.org/issues/1087582022-03-22T18:25:19Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h3 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h3>
<p>On slow architectures like aarch64, Extensions and Modules Registration can take a long time, resulting in test failure.<br>
For example <a href="https://openqa.suse.de/tests/8364864#step/skip_install_addons/2" class="external">https://openqa.suse.de/tests/8364864#step/skip_install_addons/2</a></p>
<a name="Acceptance-criteria"></a>
<h3 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h3>
<p><strong>AC1</strong>: Introduce the functionality to wait for registration on <code>ModuleRegistrationController.pm</code>.<br>
<strong>AC2</strong>: Adjust <code>register_nonconflicting_modules.pm</code>, <code>register_module_transactional.pm</code> and <code>register_module_desktop.pm</code> modules as needed to wait for registration.</p>
<a name="Suggestions"></a>
<h3 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h3>
<p>Check the work that has already been done in <code>perform_installation.pm</code> with <code>PerformingInstallationController.pm</code> function <code>wait_installation_popup()</code><br>
Check for Installation Settings Page where we recently applied something like <code>is it fully loaded the page</code> method.</p>
qe-yam - action #107749 (Resolved): Send the correct number of keys in send_key_until_needlematchhttps://progress.opensuse.org/issues/1077492022-03-01T13:48:28Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h3 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h3>
<p>Function <code>send_key_until_needlematch</code>, instead of sending the specified key <code>n</code> times, passed via argument, sends the key <code>n+1</code> times before failing.<br>
This is an issue for some scenarios, for example if an even number of keypresses is required, as is the case of maximizing and unmaximizing a window, by sending an even number of <code>alt-f10</code>.</p>
<a name="Scope"></a>
<h3 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h3>
<p>Affects all testsuites that call testapi's <code>send_key_until_needlematch</code>.</p>
<a name="Acceptance-criteria"></a>
<h3 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h3>
<p><strong>ΑC1</strong>: Modify <code>send_key_until_needlematch</code> so that key is sent the exact amount of times specified in the argument, before failing.<br>
<strong>AC2</strong>: Make sure that testsuites that use <code>send_key_until_needlematch</code> are not affected</p>
<a name="Suggestion"></a>
<h3 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h3>
<p>Change the <code>send_key_until_needlematch</code> so that <code>if (!$counter--)</code> becomes <code>if (!--$counter)</code> so that the <code>assert_screen</code> command is executed when <code>$counter</code> has become 0, not -1.</p>
qe-yam - action #105972 (Rejected): New version of nvme package causes nvme_checks module to failhttps://progress.opensuse.org/issues/1059722022-02-04T16:28:46Zgeorggkioulis@suse.com
<p>Since build 91.2 the nvme package has been bumped to version 2.0 (from 1.13).</p>
<p>This causes (among other things) some changes in the output of <code>nvme list</code> and <code>nvme list-ns /dev/nvme0</code>.</p>
<p>The <code>nvme_checks.pm</code> module fails when running <code>nvme list-ns /dev/$nvm_test_data->{nvm_char_device} | awk -F ':' '{print $2}'"</code>, because, in the new version, <code>nvme list-ns /dev/nvme0</code> outputs nothing, instead of <code>[ 0]:0x1</code>.</p>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=uefi&test=nvme&version=15-SP4" class="external">latest</a></p>
<p><strong>Suggestion:</strong> change the <code>nvme list-ns</code> command to verify the 0x1 namespace array</p>
qe-yam - action #104580 (Closed): OKStopPopup does not appear after performing installationhttps://progress.opensuse.org/issues/1045802022-01-03T16:25:15Zgeorggkioulis@suse.com
<p>PerformingInstallationController expects a popup with stop button (OKStopPopup) in order to stop the timeout after the installation has been performed.<br>
The controller should be potentially adapted.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-x86_64-textmode@svirt-xen-hvm fails in<br>
<a href="https://openqa.suse.de/tests/7924080/modules/stop_timeout_system_reboot_now/steps/2" class="external">stop_timeout_system_reboot_now</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7924080" class="external">79.1</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/7887705" class="external">77.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=svirt-xen-hvm&test=textmode&version=15-SP4" class="external">latest</a></p>
qe-yam - action #103718 (Closed): Select disk with YuiRestClient instead of using encrypt_lvm_sim...https://progress.opensuse.org/issues/1037182021-12-08T15:21:45Zgeorggkioulis@suse.com
<p>The page we find ourselves in <code>encrypt_lvm_simple_pwd</code> is the Select Hard Disks(s) page.<br>
The Partitioning Scheme page is not shown (there is no checkbox to enable lvm) and thus the test fails.</p>
<p>According to last GMC where this test scenario (before the iscsi bug appeared) was working we indeed need to select the disk:<br>
<a href="https://openqa.suse.de/tests/6445388#step/encrypt_lvm/2" class="external">https://openqa.suse.de/tests/6445388#step/encrypt_lvm/2</a></p>
<p>Let's apply the the test modules using libyui-rest-api which we already developed: </p>
<ul>
<li><code>tests/installation/partitioning/guided_setup/select_disks.pm</code></li>
<li><code>tests/installation/partitioning/guided_setup/encrypt_lvm_simple_pwd.pm</code></li>
</ul>
qe-yam - action #101908 (Closed): Investigate test failure in accept_default_part_schemehttps://progress.opensuse.org/issues/1019082021-11-03T15:46:01Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-s390x-select_modules_and_patterns@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/7591773/modules/accept_default_part_scheme/steps/2" class="external">accept_default_part_scheme</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: qe-sle-yast</p>
<p>Perform an installation enabling some modules.<br>
This test suite always registers to have access to some modules.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7584517" class="external">58.2</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/7554246" class="external">55.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online&machine=s390x-kvm-sle12&test=select_modules_and_patterns&version=15-SP4" class="external">latest</a></p>
qe-yam - action #101903 (Rejected): Investigate test failure in integration_serviceshttps://progress.opensuse.org/issues/1019032021-11-03T15:18:29Zgeorggkioulis@suse.com
<p>The <code>integration_services.pm</code> module fails at the <code>select_console 'root-console'</code> call.<br>
This fails because the System Under Test finds itself in the display manager screen.<br>
When fixed the test behavior should be similar to <a href="https://openqa.suse.de/tests/5785744#step/integration_services/2" class="external">the old runs</a>.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Full-x86_64-select_modules_and_patterns+registration@svirt-hyperv-uefi fails in<br>
<a href="https://openqa.suse.de/tests/7591216/modules/integration_services/steps/5" class="external">integration_services</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Full Medium installation that covers the following cases:<br>
1. Additional modules enabled using SCC (Legacy, Development Tools,<br>
Web and Scripting, Containers, Desktop Applications);<br>
2. Yast patterns installed;<br>
3. System registration is skipped during installation;<br>
4. Installation is validated by successful boot and that YaST does not<br>
report any issues;<br>
5. Registration is performed on the installed system.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7200373" class="external">38.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Full&machine=svirt-hyperv-uefi&test=select_modules_and_patterns%2Bregistration&version=15-SP4" class="external">latest</a></p>
qe-yam - action #99603 (Rejected): svirt-xen-hvm jobs entering emergency mode in first boothttps://progress.opensuse.org/issues/996032021-10-01T09:59:42Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-x86_64-xfs@svirt-xen-hvm fails in<br>
<a href="https://openqa.suse.de/tests/7262467/modules/first_boot/steps/9" class="external">first_boot</a></p>
<p>also fails on <a href="https://openqa.suse.de/tests/7276616#step/first_boot/9" class="external">textmode</a> and <a href="https://openqa.suse.de/tests/7262464#step/first_boot/9" class="external">minimal+base_yast</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>. Maintainer: QE Yast, QE Kernel</p>
<p>Installation test with explicit selection of "xfs" instead of default.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7262467" class="external">43.1</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/7218822" class="external">39.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=svirt-xen-hvm&test=xfs&version=15-SP4" class="external">latest</a></p>
qe-yam - action #99600 (Rejected): Investigate System Role page not loadinghttps://progress.opensuse.org/issues/996002021-10-01T09:43:51Zgeorggkioulis@suse.com
<p>Until now, at the end of <code>addon_products_sle</code> module, once the next button is pressed using keyboard, the System Role page appears, as can be seen in the last screen of the <code>addon_products_sle</code> module <a href="https://openqa.suse.de/tests/7200374#step/addon_products_sle/60" class="external">on previous runs</a>.</p>
<p>In the new build however, the transition to the System Role page never happens resulting in a failing needle in the <code>system_role</code> module.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Full-x86_64-select_modules_and_patterns+registration@svirt-hyperv2016 fails in<br>
<a href="https://openqa.suse.de/tests/7279621/modules/system_role/steps/2" class="external">system_role</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Full Medium installation that covers the following cases:<br>
1. Additional modules enabled using SCC (Legacy, Development Tools,<br>
Web and Scripting, Containers, Desktop Applications);<br>
2. Yast patterns installed;<br>
3. System registration is skipped during installation;<br>
4. Installation is validated by successful boot and that YaST does not<br>
report any issues;<br>
5. Registration is performed on the installed system.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7124547" class="external">36.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Full&machine=svirt-hyperv2016&test=select_modules_and_patterns%2Bregistration&version=15-SP4" class="external">latest</a></p>
qe-yam - action #99573 (Rejected): Investigate failure of LVM activationhttps://progress.opensuse.org/issues/995732021-09-30T15:36:18Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-aarch64-activate_encrypted_volume+import_users@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/7274219/modules/skip_install_addons/steps/1" class="external">skip_install_addons</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7269640" class="external">43.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/7217928" class="external">39.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=activate_encrypted_volume%2Bimport_users&version=15-SP4" class="external">latest</a></p>
qe-yam - action #99555 (Closed): Investigate x11_yast pattern being installed unexpectedelyhttps://progress.opensuse.org/issues/995552021-09-30T11:52:54Zgeorggkioulis@suse.com
<p>It seems that in Build43.1 pattern <code>x11_yast</code> is (unexpectedly) installed, alongside the other expected patterns.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Full-x86_64-select_modules_and_patterns+registration@64bit fails in<br>
<a href="https://openqa.suse.de/tests/7261284/modules/validate_installed_patterns/steps/5" class="external">validate_installed_patterns</a></p>
<p>also visible eg <a href="https://openqa.suse.de/tests/7270890#step/validate_installed_patterns/5" class="external">in this s390 job</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Full Medium installation that covers the following cases:<br>
1. Additional modules enabled using SCC (Legacy, Development Tools,<br>
Web and Scripting, Containers, Desktop Applications);<br>
2. Yast patterns installed;<br>
3. System registration is skipped during installation;<br>
4. Installation is validated by successful boot and that YaST does not<br>
report any issues;<br>
5. Registration is performed on the installed system.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7261284" class="external">43.1</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/7217514" class="external">39.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Full&machine=64bit&test=select_modules_and_patterns%2Bregistration&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #99180 (Resolved): test fails in scc_registration in QR 15-SP3https://progress.opensuse.org/issues/991802021-09-24T10:49:22Zgeorggkioulis@suse.com
<p>After a recent change where the multipath activation pop up appears right after disk activation has been completed, the multipath module needs to precede the registration module in the zfcp jobs.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Online-QR-s390x-zfcp@s390x-zfcp fails in<br>
<a href="https://openqa.suse.de/tests/7215665/modules/scc_registration/steps/5" class="external">scc_registration</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>. Maintainer: QE Yast, mgriessmeier</p>
<p>Installation-only test configuring an s390x ZFCP storage.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/7141435" class="external">188.16</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/6872082" class="external">188.15</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online-QR&machine=s390x-zfcp&test=zfcp&version=15-SP3" class="external">latest</a></p>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<p>Alter the order the schedule so that multipath module precedes the registration.</p>