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 #122059 (Resolved): Add AutoYaST testsuite for Tumbleweed on s390x z/VMhttps://progress.opensuse.org/issues/1220592022-12-15T15:56:34Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Kernel squad would like to have similar test suites <a href="https://openqa.suse.de/tests/10087068#dependencies" class="external">sequence</a> in Tumbleweed that what they use for SLE to run later on LTP tests. (more info on <a href="https://suse.slack.com/archives/C02CANHLANP/p1671098344384289" class="external">slack thread</a>)<br>
In SLE is used <a href="https://openqa.suse.de/tests/10086929" class="external">create_hdd_minimal_base</a>:</p>
<ul>
<li>Module selected: base, desktop, development, server</li>
<li>guided partitioning: no separate home</li>
<li>system role: gnome (shouldn't be better to select textmode?)</li>
<li>pattern: base and minimal</li>
<li>Major Linux security: none</li>
<li>disable grub timeout</li>
</ul>
<p>But this is s390x kvm, and in openSUSE there is only support for z/VM.<br>
Therefore Yam squad could provide similar auto-installation than for SLE but for this backend as Kernel squad needs something that run fast, because there is not booting snapshots for z/VM so any LTP test needs to run first the installation.</p>
<p>Starting point could be to convert in AutoYaST this interactive installation: <a href="https://openqa.opensuse.org/tests/2956964">https://openqa.opensuse.org/tests/2956964</a> :</p>
<ul>
<li>disk activation</li>
<li>system role: server</li>
<li>patterns: it could be more minimal comparing with the job above</li>
<li>disable grub timeout</li>
</ul>
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p>A new autoyast installation testsuite is to be created in <a href="openqa.opensuse.org/" class="external">openqa.opensuse.org</a>.<br>
Currently we run there a <a href="https://openqa.opensuse.org/tests/2954722" class="external">guided installation</a> which takes around 42 mins.<br>
Products: opensuse Tumbleweed<br>
Architectures: s390x with backend s390x (which just means z/VM, the only supported backend for s390x in o3 right now)</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Create auto-installation for Tumbleweed in s390x zVM<br>
<strong>AC2</strong>: File a bug if any is found for AutoYaST cloning or service order after booting to YaST<br>
<strong>AC3</strong>: Investigate and file a infrastructure bug if found<br>
<strong>AC4</strong>: if some blocker is found, consider as last option using libyui-rest-api, which is also fast (but not ideal to have interactive installation)</p>
<a name="Additional-information"></a>
<h4 >Additional information<a href="#Additional-information" class="wiki-anchor">¶</a></h4>
<p>afir there was some issues with z/VM when booting but we will see what is the state. This is completely new area where to enable AutoYaST.</p>
qe-yam - action #119083 (Rejected): [Timebox: 3 days] Investigate how to make SUT offline on PowerVMhttps://progress.opensuse.org/issues/1190832022-10-19T13:12:21Zgeorggkioulis@suse.com
<p>Related to <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: Run offline_install+skip_registration with PowerVM (Resolved)" href="https://progress.opensuse.org/issues/116116">#116116</a></p>
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Testsuite <a href="https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=offline_install%2Bskip_registration_dev&modules=&module_re=&version=15-SP5&distri=sle&groupid=456#" class="external">offline_install+skip_registration_dev</a> on ppc64le in development group is similar to <a href="https://openqa.suse.de/tests/overview?arch=ppc64le&flavor=&machine=&test=offline_install%2Bskip_registration&modules=&module_re=&version=15-SP5&distri=sle&groupid=129#" class="external">offline_install+skip_registration</a> but it runs on PowerVM backend (<code>pvm_hmc</code>) instead of QEMU.<br>
Both <code>offline_install+skip_registration_dev</code> and <code>offline_install+skip_registration</code> require an offline SUT to run. This is achieved by providing the <code>OFFLINE_SUT=1</code> setting.</p>
<p>However the <code>OFFLINE_SUT=1</code> can only set a QEMU backend offline as can be seen in <a href="https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L825" class="external">os-autoinst/qemu.pm</a>.<br>
This ticket aims to investigate whether it is possible to set the system offline via <a href="https://github.com/os-autoinst/os-autoinst/blob/master/backend/pvm_hmc.pm" class="external">os-autoinst/pvm_hmc.pm</a> backend or even via boot parameters in the bootloader stage of the testsuite.<br>
This would hopefully prevent the failure on the PowerVM job <a href="https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=offline_install%2Bskip_registration_dev&modules=&module_re=&version=15-SP5&distri=sle&groupid=456#" class="external">offline_install+skip_registration_dev</a></p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Investigate whether it is possible to set the PowerVM system offline via it's hypervisor settings (maybe as an <code>HMC_*</code> variable). <br>
<strong>AC2</strong>: If <strong>AC1</strong> is not possible, investigate whether it is possible to set the PowerVM system offline via a boot parameter. Some candidates here can be the <code>netdev</code> kernel parameter or the even the obsoleted <code>ether</code> parameter, which might be used to disable Ethernet cards.<br>
<strong>AC3</strong>: If any of the above works, create a new progress ticket to implement the change and move <code>offline_install+skip_registration_dev</code> from development to production, replacing the existing <code>offline_install+skip_registration</code> testsuite that runs there.</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 #117949 (Resolved): Apply workaround to force screen refresh on YaST Qt windowhttps://progress.opensuse.org/issues/1179492022-10-11T07:41:24Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h3 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h3>
<p>Occasionally, the screen on a YaST Qt window does not refresh properly (<a href="https://bugzilla.suse.com/show_bug.cgi?id=1204176" class="external">bsc#1204176</a>). This leads to failures like <a href="https://openqa.suse.de/tests/9681079#step/iscsi_client/52" class="external">this one</a> where content from the previous screen is still visible in the new screen, and <a href="https://openqa.suse.de/tests/9680782#step/yast2_control_center/96" class="external">this one</a> where the content does not fully load.<br>
A workaround is to hit <code>shift-F3</code> twice to bring up the style sheet selection and close it again. This forces a refresh on the YaST screen, as seen <a href="https://bugzilla.suse.com/attachment.cgi?id=862070" class="external">here</a>.<br>
We should apply this workaround to all affected areas.</p>
<a name="Scope"></a>
<h3 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h3>
<p>The workaround should be applied for 15-SP5, all archs.<br>
Concerning which areas of the code would be affected, check the <strong>Suggestion</strong> section.<br>
Workaround should be applied where is not working now, not everywhere.</p>
<a name="Acceptance-criteria"></a>
<h3 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h3>
<p><strong>AC1</strong>: Add a workaround (hitting <code>shift-f3</code> to open and close the style menu) to force a refresh on the YaST Qt window.<br>
<strong>AC2</strong>: Make sure to record a soft failure, above the workaround, mentioning the <strong>new</strong> bug <code>bsc#1204176</code> as the reason for the workaround.</p>
<a name="Suggestion"></a>
<h3 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h3>
<p>We used to apply a similar workaround where we would send <code>alt-F10</code> multiple times (actually, an <em>even number</em> of times), which would maximize and unmaximize the window, forcing a screen refresh.<br>
The workaround was removed with <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15585/files" class="external">this PR</a> when a fix was added to the new 15-SP5 builds.<br>
However this fix seems to not fully remove the refresh issue.<br>
The suggestion here is to check this PR to view in which areas of the code to introduce the <code>shift-F3</code> workaround.<br>
So for instance we could re-introduce at the same areas a <code>send_key_until_needlematch</code> but this time with <code>shift-F3</code>.</p>
qe-yam - action #116365 (Resolved): Add AutoYaST test suites for chained dependencies in YaST Mai...https://progress.opensuse.org/issues/1163652022-09-08T15:43:25Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>See <a class="issue tracker-6 status-3 priority-4 priority-default closed parent" title="coordination: [Epic] Add AutoYaST test suites for dependencies in YaST Maintenance Updates and keep interactive... (Resolved)" href="https://progress.opensuse.org/issues/109187">#109187</a><br>
It is done for SLE-15-SP{3,4} in <a class="issue tracker-4 status-5 priority-5 priority-high3 closed child" title="action: Add AutoYaST test suites for dependencies in YaST Maintenance Updates and keep interactive instal... (Closed)" href="https://progress.opensuse.org/issues/109214">#109214</a>. Let's try to reuse the same AutoYaST profile for the rest of the products in maintenance.<br>
<a href="https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=mru-install-desktop-with-addons&modules=&module_re=&distri=sle&version=12-SP4&version=12-SP5&build=20220907-1&groupid=414#" class="external">mru-install-desktop-with-addons</a> | <a href="https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=mru-install-minimal-with-addons&modules=&module_re=&distri=sle&version=12-SP4&version=12-SP5&build=20220907-1&groupid=414#" class="external">mru-install-minimal-with-addons</a></p>
<p>These new testsuites should be put in YaST Development job group. Then we will file another ticket to deploy this in YaST MU job group.</p>
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p>Test suites with external dependencies: <code>mru-install-desktop-with-addons</code> & <code>mru-install-minimal-with-addons</code><br>
Products: SLE 12-SP4 and SLE 12-SP5.<br>
Architectures: <code>mru-install-minimal-with-addons</code> is running in three architectures, aim for all of them if possible.</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: New AutoYaST test suites are created in 'YaST Maintenance Updates - Development' openQA job group corresponding to <code>mru-install-desktop-with-addons</code> & <code>mru-install-minimal-with-addons</code>.<br>
<strong>AC2</strong>: Copies of the chained dependencies of test suites <code>mru-install-desktop-with-addons</code> & <code>mru-install-minimal-with-addons</code> which are in YaST MU job group will be set to new AutoYaST test suites in 'YaST Maintenance Updates - Development' job group<br>
<strong>AC3</strong>: If we cannot reuse the AutoYaST profile created for SLE-15-SP{3,4} consider to reduce the scope of products or architectures to migrate to AutoYaST.</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<ul>
<li>Reuse knowledge from previous task: <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="action: Migrate create_hdd_gnome in Functional group to use AutoYaST (Closed)" href="https://progress.opensuse.org/issues/107674">#107674</a> <a class="issue tracker-6 status-3 priority-4 priority-default closed parent" title="coordination: [Epic] Add AutoYaST test suites for dependencies in YaST Maintenance Updates and keep interactive... (Resolved)" href="https://progress.opensuse.org/issues/109187">#109187</a></li>
<li>We could reuse very likely the AutoYaST profiles created for SLE-15-SP3.</li>
<li>Rename the teststuites creating AutoYaST image to <code>autoyast_create_*</code> so we can distinguish better between old and new things regardless of the job group, maintenance or product.</li>
</ul>
<p>For sle-12-sp5 seems that we can reuse the profile, but for sle-12-sp4 where we have some issue with ltss we need to figure out.</p>
qe-yam - action #116131 (Rejected): Ensure Boot from Hard Disk is selected in grub, migrationhttps://progress.opensuse.org/issues/1161312022-09-01T15:38:54Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p><a href="https://openqa.suse.de/tests/9427729#step/grub_test/3" class="external">Migration from 12SP5 fails</a> because the entry <code>Boot from Hard Disk</code> is not selected in grub menu of the migrated system.</p>
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p>testsuite <a href="https://openqa.suse.de/tests/9427729#step/grub_test/3" class="external">sle-15-SP5-Migration-from-SLE12-SPx-x86_64-Build19.1-autoupgrade_sles12sp5_pscc_lp_def_full</a></p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Ensure <code>Boot from Hard Disk</code> is selected in grub menu</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<p>It seems that the input that selects the entry is not registered, but also that the grub timeout is too big compared to the needle timeout. Maybe it is worth investigating if this is unexpected behavior/bug</p>
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 #115622 (Resolved): Install kdumptool where needed and fix synchronization failur...https://progress.opensuse.org/issues/1156222022-08-22T15:42:21Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Kdump is not a dependency of yast2-kdump module in SLE15-SP5 and is no longer installed when yast2-kdump is installed.<br>
This behavior is intended as can be seen in <a href="https://bugzilla.suse.com/show_bug.cgi?id=1202535" class="external">bsc#1202535</a> and is a feature, not a bug.<br>
However this may be the cause of failures on our yast2_kdump testsuite, which need to be investigated (they are differ by architecture).</p>
<ul>
<li>aarch64 and x86_64: both fail because kdumptool is not available, which makes sense since kdump has not been installed. Even when installing kdump however, the testsuites fail because no crashkernel arguments have been added in grub config.</li>
<li>ppc64le : test does not catch the expected restart popup</li>
<li>s390x : code execution finished too early</li>
</ul>
<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=&modules=yast2_kdump&module_re=&distri=sle&version=15-SP5&build=15.2&groupid=129#" class="external">https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=yast2_kdump&module_re=&distri=sle&version=15-SP5&build=15.2&groupid=129#</a> <br>
<code>ppc64le-spvm</code> is hit by a libyui bug (bsc#1202575) but the rest architectures failures are within scope. </p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Setup properly the kdump installing only for SLE-15-SP5 necessary tools and fix sync issues with reboot screen.<br>
<strong>AC2</strong>: File found bugs if any.</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<p>When fixing sync issues, please take a look to Kernel squad where this module is used for real, doing a real kdump, not just configuring it.<br>
Perhaps we need to install development module, this test suite is still linked to Functional job group to an interactive installation, we should aim to have a textmode installation with development module included in the future.</p>
qe-yam - action #115619 (Resolved): Adjust send_key_until_needlematch `$counter` argument in test...https://progress.opensuse.org/issues/1156192022-08-22T15:15:21Zgeorggkioulis@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 addressed in <a href="https://progress.opensuse.org/issues/107749" class="external">poo#107749</a> with <a href="https://github.com/os-autoinst/os-autoinst/pull/2151" class="external">this PR</a>.<br>
It is now needed to adjust all testsuites that make use of <code>send_key_until_needlematch</code> by increasing the <code>$counter</code> argument by one, if this argument is used.</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>AC1</strong>: Make sure that all testsuites that call <code>send_key_until_needlematch</code> and pass the <code>$counter</code> argument as n, now pass n+1.</p>
<a name="Suggestion"></a>
<h3 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h3>
<p>Since the scope is so vast, it would be hard to do extensive verification runs. One recommendation is to do a small sample of verification runs.</p>
qe-yam - action #114730 (Rejected): [Timebox: 16h] Investigate which job results block approval f...https://progress.opensuse.org/issues/1147302022-07-27T12:58:27Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>When a job from our <a href="https://openqa.suse.de/group_overview/421" class="external">aggregate maintenance updates</a> fails, it blocks all the related maintenance updates from approval by the members of the <code>qam-openqa</code> group (maintenance openqa reviewers).<br>
The questions arises, what job states, other than <code>failed</code>, result in maintenance updates being blocked?<br>
Does for instance an <a href="https://openqa.suse.de/tests/9222738" class="external">incomplete</a> job or a <a href="https://openqa.suse.de/tests/9222743#" class="external">cancelled</a> job also block their related updates? <br>
Knowing this will help us better organize the required actions in the context of our Maintenance Update Review process. </p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong> Figure out what job results block update approval for qam-openqa</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<p>The maintenance openqa reviewer use this dashboard <a href="http://dashboard.qam.suse.de/blocked" class="external">http://dashboard.qam.suse.de/blocked</a> to have visibility on the blocked updates.<br>
The maintainer of this dashboard (maybe someone from qe-tools?) should be able to help.<br>
Also we could check what happen when some arch doesn't run any job.</p>
qe-yam - action #114682 (Resolved): Fix HDD name matching in mru-iscsi maintance update jobshttps://progress.opensuse.org/issues/1146822022-07-26T10:19:29Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>In YaST Maintenance updates there have been recent failures in the <code>mru-iscsi</code> server and client jobs such as <a href="https://openqa.suse.de/tests/9214130" class="external">this one</a>.<br>
The failure is that the qcow stated in the HDD_1 setting does not exist.<br>
The jobs have dependency on <code>create_hdd_yast_maintenance_desktop</code> which generate a qcow without issue.</p>
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p>Testsuites: mru-iscsi_client_normal_auth_backstore_fileio, mru-iscsi_server_normal_auth_backstore_fileio, mru-iscsi_client_normal_auth_backstore_hdd, mru-iscsi_server_normal_auth_backstore_hdd, mru-iscsi_client_normal_auth_backstore_lvm, mru-iscsi_server_normal_auth_backstore_lvm<br>
Products: 15-SP3, 15-SP4</p>
<a name="Acceptance-Criteria"></a>
<h4 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Make sure that PUBLISH_HDD from <code>create_hdd_yast_maintenance_desktop</code> and HDD_1 from the <code>iscsi</code> jobs have the same form.<br>
<strong>AC2</strong>: Provide verification runs for the fix.</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<p>Delete the -%FLAVOR%-%MACHINE% from the HDD_1 parameters of the <code>iscsi</code> jobs so that the expected qcow name matches the one generated from <code>create_hdd_yast_maintenance_desktop</code></p>
<a name="Further-Information"></a>
<h4 >Further Information<a href="#Further-Information" class="wiki-anchor">¶</a></h4>
<p>Related merge request: <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/328" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/328</a></p>
qe-yam - action #111458 (Resolved): Create a small cli/script to help debugging failures with mai...https://progress.opensuse.org/issues/1114582022-05-23T12:09:16Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>We now have responsibility of YaST tests in <a href="https://openqa.suse.de/group_overview/421" class="external">YaST Maintenance Updates</a>.<br>
This means that we will have to debug failures that could be caused by maintenance updates installed on the systems of those runs. <br>
In order to facilitate with this it would be convenient to have a tool that shows a small overview of the maintenance updates that are applied to a job.</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Given an openQA job id, the script can retrieve incidents IDs filtering by product module.<br>
<strong>AC2</strong>: The script can query information for those IDs that helps to debugs problems (for instance patchinfo)<br>
<strong>AC3</strong>: The script should be simple enough, containing a few lines that are easy to maintain.<br>
<strong>AC4</strong>: Consider how we could filter YaST related updates with the final output (not implementation required).</p>
<a name="Suggestion"></a>
<h4 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h4>
<ul>
<li><p>Using the <code>openQA Job ID</code> we should be able to construct the var.json url of the job (eg <code>https://openqa.suse.de/tests/8805896/file/vars.json</code>). We can either parse the .json file to get get the Incident IDs from <code>.*_TEST_ISSUES</code> or from the <code>MAINT_TEST_REPO</code> variables.</p></li>
<li><p>Script should be able to give us incident ids related to specific products, for example if we are only interested in <code>HPCM_TEST_ISSUES</code> we could filter by HPCM, but also we could also interested on ASMM, so we could specify a comma-separated list <code>HPCM,ASMM</code>. Without filter we should get all of them present in the vars.json.</p></li>
<li><p>For each Incident ID we should be able to get the <code>patchinfo</code> of the update. Eg for Incident ID <code>24365</code> this can be done either via getting the file <a href="https://build.suse.de/source/SUSE:Maintenance:24364/patchinfo/_patchinfo">https://build.suse.de/source/SUSE:Maintenance:24364/patchinfo/_patchinfo</a> , or by scraping <a href="https://build.suse.de/package/view_file/SUSE:Maintenance:24365/patchinfo/_patchinfo?expand=1">https://build.suse.de/package/view_file/SUSE:Maintenance:24365/patchinfo/_patchinfo?expand=1</a> , or via osc commands. All three methods require a login first.</p></li>
<li><p>The tool should output a small amount of information for each Incident ID. The patchinfo file may contain more info than needed so it could need additional parsing.</p></li>
<li><p>Once we have a script easy to maintain for us if we would see that we need more features, we will be in a better position to know what we want exactly and we can consider other existing and more powerful tools in that case, but likely this would be enough for our goal.</p></li>
<li><p>Perhaps just grep by "yast" is enough but perhaps there are more YaST components or maintained by YaST developers which do not start by "yast". We could figure out or ask them, but we don't need to implement that additional filtering for now.</p></li>
</ul>
qe-yam - action #103320 (Rejected): Create new test module for DASD disk filteringhttps://progress.opensuse.org/issues/1033202021-11-30T14:13:15Zgeorggkioulis@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>In DASD Disk Management page (can be seen <a href="https://openqa.suse.de/tests/7125537#step/disk_activation/2" class="external">here</a>) there is the capability of filtering DASD disks by inputting a channel range in the minimum and maximum channel ID fields.</p>
<p>We can test this by using the functionality (<code>enter_maximum_channel</code>, <code>enter_minimum_channel</code>, <code>press_filter_button</code>) provided by <code>DASDDiskManagementPage.pm</code>.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create a test module that filters the shown DASD devices by a selected channel range and validate the output.</li>
<li>It is sufficient to include this test module in a single job's schedule that includes the <code>configure_dasd</code> test module, not all of them.</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>An easy implementation can be to have the same channel value for minimum and maximum channel. This will make validating the output easier, since the device table item list will contain only one item to be asserted.</li>
</ul>
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>