openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-02-15T18:12:36ZopenSUSE Project Management Tool
Redmine openQA Project - action #124652 (Resolved): gtk glitch not showing dialog window decoration on op...https://progress.opensuse.org/issues/1246522023-02-15T18:12:36Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>During our graphical YaST tests we (the qe-yam team) encounter a type of graphic glitch where the screen is not properly refreshed.<br>
Examples can be seen <a href="https://openqa.suse.de/tests/10436703#step/iscsi_client/57" class="external">here</a> and <a href="https://openqa.suse.de/tests/9680782#step/yast2_control_center/96" class="external">here</a></p>
<p>This behavior is sporadic but widespread enough that it has forced qe-yam to apply <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15889" class="external">workarounds</a> to a number of our tests.<br>
Because the conditions allowing the workarounds are not always consistent, we have interest in the root of the issue getting resolved.<br>
Our <a href="https://bugzilla.suse.com/show_bug.cgi?id=1204176" class="external">latest bug entry</a> on the matter has been tagged as WONTFIX because we (qe-yam and the YaST developers) have not found a way to reproduce this glitch outside of the openQA environment.</p>
<p>latest: <a href="https://openqa.suse.de/tests/10499467#step/yast2_lan_restart_vlan/19">https://openqa.suse.de/tests/10499467#step/yast2_lan_restart_vlan/19</a> (glitch does not happen on yast2_control_center on last build but can be seen elsewhere)<br>
last good: <a href="https://openqa.suse.de/tests/5900202#step/yast2_control_center/94">https://openqa.suse.de/tests/5900202#step/yast2_control_center/94</a></p>
<a name="Scope"></a>
<h3 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h3>
<p>aarch64, s390x, x86_64 on SLE 15-SP4 and SLE 15-SP5 (issue is not exclusive on qemu)</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The graphic glitch does not appear anymore in tests</li>
</ul>
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<ul>
<li><p><strong>H1</strong> could be the qemu video adapter</p>
<ul>
<li><strong>H1.1</strong> <strong>REJECTED</strong> could be the specific choice of qemu video adapter</li>
<li><em>E1.1-1</em> <em>DONE</em> Try out the reproducing openQA test with different qemu video adapters -> <em>O1.1-1-1</em> <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-16">#124652#note-16</a> different video
adapters reproduced the same issue</li>
<li><strong>H1.2</strong> maybe can not be reproduced with using special qemu video adapter settings</li>
</ul></li>
<li><p><strong>H2</strong> <strong>REJECTED</strong> only happens in older SLE versions => Current SLE15SP5 affected the same</p>
<ul>
<li><em>E2-1</em> <em>DONE</em> Run the equivalent openQA test on SLE </li>
<li><em>O2-1-1</em> issue observed on SLE15SP4-build31.2+ <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-3">#124652#note-3</a></li>
<li><em>O2-1-2</em> 0/100 failures on SLE15SP3+maintenance updates <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-25">#124652#note-25</a></li>
<li><em>E2-2</em> <em>DONE</em> Run the equivalent openQA test on current Tumbleweed -> <em>O2-2-1</em> Tumbleweed does not reproduce the problem, see <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-26">#124652#note-26</a></li>
<li><em>E2-3</em> <em>DONE</em> Run the equivalent openQA test on current SLE15SP5 -> <em>O2-3-1</em> <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-32">#124652#note-32</a> 5/101 (yast2_security) fails <a href="https://openqa.suse.de/tests/overview?distri=sle&build=glitch_investigation_SP5&version=15-SP5" class="external">SLE15SP5@OSD</a></li>
<li><strong>H2.1</strong> <strong>ACCEPTED</strong> only happens in older SLE versions with newer maintenance updates</li>
<li><em>E2.1-1</em> <em>DONE</em> Run openQA test on SLE15-SP4 -> <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-23">#124652#note-23</a> 97% fail rate iscsi_server on SLE15-SP4</li>
<li><em>E2.1-2</em> <em>DONE</em> From <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-24">#124652#note-24</a> Run openQA test on SLE15-SP3 with state of maintenance update from 2 years ago ("last good" <a href="https://openqa.suse.de/tests/5900202#step/yast2_control_center/94">https://openqa.suse.de/tests/5900202#step/yast2_control_center/94</a> from #Motivation) -> <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-36">#124652-36</a> 0/100 failures on SLE15SP3GM; 0/100 failures on SLE15SP2+updates -> accept <em>H2.1</em></li>
</ul></li>
<li><p><strong>H3</strong> <strong>ACCEPTED</strong> can only be reproduced in openQA</p>
<ul>
<li><em>E3-1</em> <em>DONE</em> try to reproduce manually -> no one could reproduce manually</li>
<li><strong>H3.1</strong> <strong>REJECTED</strong> can be reproduced on openqa.suse.de regardless of OS version or variant</li>
<li><em>E3.1-1</em> <em>DONE</em> Run openSUSE openQA test on openqa.suse.de -> <em>O3.1-1-1</em> <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-32">#124652#note-32</a> 0/101 fails <a href="https://openqa.suse.de/tests/overview?distri=opensuse&build=glitch_investigation_tw&version=Tumbleweed" class="external">Tumbleweed@OSD</a> + 0/101 <a href="https://openqa.suse.de/tests/overview?distri=opensuse&build=glitch_investigation_leap_sp4&version=15.4" class="external">Leap15.4@OSD</a> + 0/100 <a href="https://openqa.suse.de/tests/overview?distri=opensuse&version=Leap15.5&build=glitch_investigation_leap_sp5" class="external">Leap15.5@OSD</a> vs. 5/101 fails <a href="https://openqa.suse.de/tests/overview?distri=sle&build=glitch_investigation_SP5&version=15-SP5" class="external">SLE15SP5@OSD</a></li>
</ul></li>
<li><p><strong>H4</strong> <strong>ACCEPTED</strong> The test module(s) "iscsi_server/client" are most prone to fail, also shows in other yast modules</p>
<ul>
<li><em>E4-1</em> <em>DONE</em> Gather statistics for different yast modules -></li>
<li><em>O4-1-1</em> <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-11">#124652#note-11</a> the problem was referenced for different modules, e.g. iscsi_server and yast2_security but no clear statistics</li>
<li><em>O4-1-2</em> <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-23">#124652#note-23</a> 97-99% fail rate iscsi_server on SLE15-SP4/5 vs. <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: gtk glitch not showing dialog window decoration on openQA size:M (Resolved)" href="https://progress.opensuse.org/issues/124652#note-32">#124652#note-32</a> 5% yast2_security on SLE15-SP5</li>
</ul></li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>It looks like window decorations are missing from the dialog</li>
<li>The emulated graphics adapter might be causing problems with the window manager</li>
<li>Research what options could be used with the graphics emulation in qemu</li>
<li>Identify the underlying parameter(s) in the openQA environment that can cause this graphical glitch.</li>
<li>Find a last good? We couldn't find one easily?</li>
<li>could be a VNC-related issue? Missing borders may occur there</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=yast2_gui&version=15-SP5" class="external">Link to latest</a></p>
openQA Project - action #122608 (Resolved): exit code of shell command not received by script_runhttps://progress.opensuse.org/issues/1226082023-01-02T18:41:03Zgeorggkioulis@suse.com
<p>Occasionally, <code>script_run</code> (and <code>assert_script_run</code>) do not receive the exit code from the shell command, even though the command has exited, resulting in a timeout.<br>
This has been noticed on s390x-kvm <a href="https://openqa.suse.de/tests/9951916#step/logs_from_installation_system/6" class="external">here</a> where the ping command returns but still <code>script_run</code> times out.<br>
It is also obvious in <a href="https://openqa.suse.de/tests/10244897#step/logs_from_installation_system/7" class="external">this example</a> where <code>assert_script_run</code> times out, despite the fact that the <code>ls</code> command has returned.<br>
The issue is very sporadic and not easy to debug.</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 #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 #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 #105440 (Resolved): Add new ZFCP devices that appear over 0.0.fc00 channelhttps://progress.opensuse.org/issues/1054402022-01-25T14:30:32Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>In the <a href="https://openqa.suse.de/tests/latest?distri=sle&flavor=Online&test=zfcp&version=15-SP4" class="external">zfcp testsuite</a>, the <code>configure_zfcp_device</code> module is adding four zfcp devices based on the channel ID <code>0.0.fa00</code>.</p>
<p>Since a Host Bus Adapter (with channel ID <code>0.0.fc00</code>) is now connected to our z/VM server, in order to test against the entirety of our infrastructure, we will need to add the four new ZFCP devices that appear on the <code>0.0.fc00</code> channel.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<p><strong>AC1</strong>: Configure and add the ZFCP devices that appear on two Channel IDs: <code>0.0.fa00</code> and <code>0.0.fc00</code>. These should be 8 devices in total.<br>
<strong>AC2</strong>: Steps should be visible via screenshots or making more tests more atomic, as we pass by the sames screen twice.</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<p>Adding devices for both channels in <code>configure_zfcp_device</code> module <em>should</em> probably be enough.</p>
qe-yam - coordination #105437 (Resolved): [Epic] Refine our testing of multipathhttps://progress.opensuse.org/issues/1054372022-01-25T14:10:18Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>The FCP topology on our z/VM testing infrastructure has recently been updated.<br>
We now have two Host Bus Adapters connecting our z/VM Server to the storage.</p>
<p>You can see an overview of our updated topology <a href="https://confluence.suse.com/download/attachments/910164448/fcp_topology1_updated2.png?version=1&modificationDate=1641917169989&api=v2" class="external">here</a>.</p>
<p>Our aim is to have in place a multipath test that will check the status of the infrastructure as it currently is, and the status of multipathing on top of it.</p>
<p>For some more info about FCP and multipathing on our z/VM system check <a href="https://confluence.suse.com/display/QYT/Mainframe+Musings%3A+Playing+around+with+FCP+and+multipath#MainframeMusings:PlayingaroundwithFCPandmultipath-Faulttoleranceinaction" class="external">this confluence article</a>.</p>
openQA Infrastructure - action #102167 (Resolved): Disk monitoring for s390x z/VM backendhttps://progress.opensuse.org/issues/1021672021-11-09T13:47:32Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>There are multiple recent occasions of openQA s390x z/VM tests failing due to <code>Disk or file space is full</code>, eg in scenario sle-15-SP4-Online-s390x-allpatterns@s390x-zVM-vswitch-l3, on <a href="https://openqa.suse.de/tests/7618985/modules/bootloader_start/steps/30" class="external">bootloader_start</a></p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<p><strong>AC1</strong>: Monitor disk space of the z/VM hypervisor<br>
<strong>AC2</strong>: Trigger a manual or automatic clean-up process</p>
<a name="Other-Suggestions"></a>
<h2 >Other Suggestions<a href="#Other-Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Increase storage size</li>
</ul>
openQA Tests - action #96992 (Resolved): [qe-core][samba_adcli] Track and softfail all samba_adcl...https://progress.opensuse.org/issues/969922021-08-16T13:47:30Zgeorggkioulis@suse.com
<p>The samba_adcli module fails sporadically in a multitude of different cases.</p>
<ul>
<li>Identify those cases</li>
<li>Create individual poos for those that don't have one and track them</li>
<li>Softfail the sporadic failures so that the test can run without blocking approval of updates.</li>
</ul>
openQA Tests - action #95926 (Resolved): [qe-core] Investigate if mau-qa_userspace_openssh covera...https://progress.opensuse.org/issues/959262021-07-23T12:44:21Zgeorggkioulis@suse.com
<p>We need to investigate whether <code>mau-qa_userspace_openssh</code> covers any functional test cases that are not covered by the other ssh tests currently scheduled (eg sshd).</p>
<p>If not, <code>mau-qa_userspace_openssh</code> should be unscheduled (and most probably completely remove it from the os-autoinst-distri-opensuse repo, if no other squad depends on it, as it looks to be the case)</p>
openQA Tests - action #95798 (Resolved): [qe-core] SLE 15-SP3 missing from version specific secti...https://progress.opensuse.org/issues/957982021-07-21T14:34:22Zgeorggkioulis@suse.com
<p>the following yamls are missing an entry for SLE 15-SP3 in the conditional_schedule/version_specific section:</p>
<ul>
<li>schedule/qam/common/mau-extratests1.yaml </li>
<li>schedule/qam/common/mau-extratests2.yaml</li>
<li>schedule/qam/common/mau-extratests-phub.yaml</li>
</ul>
<p>This results in a number of modules (osinfo_db, ovn, firewalld, libgcrypt, valgrind, journald_fss, openvswitch_ssl and others) not being run for SLE 15-SP3 in maintenance.</p>
<p>There would be need to add an entry for 15-SP3 and also check/report if there are any related failures in those modules.</p>
QA - action #94600 (New): [tools][mtui] Communicate reduced visibility of openQA incident related...https://progress.opensuse.org/issues/946002021-06-23T13:49:30Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>The <code>Results from openQA incidents jobs:</code> section in a maintenance update's test log shows, as one would expect, the incident jobs related to the incident that is to be tested.<br>
It can happen that engineers testing the incident fall under the impression that the openQA coverage shown in the log is the complete openQA test coverage for that incident.<br>
It should thus be communicated that the <code>openQA incident jobs</code> section does not show the complete test coverage of the incident in openQA, but only a subset of it (the other being in aggregate runs that test the incident).</p>
<p>This should clarify to the engineers that the absence of failed incident jobs in the log does not mean necessarily that there are no other failed jobs related to the incident.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Communicate that the jobs listed in the log of an update are not the complete set of jobs that test that update</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>One suggestion could be to remove that section from the log and instead link the incident comments (eg <a href="https://maintenance.suse.de/incident/19067/#comments" class="external">https://maintenance.suse.de/incident/19067/#comments</a>) where all jobs related to that incident are listed.</li>
</ul>
openQA Tests - action #90923 (Resolved): [qe-core] Schedule userspace_systemd in SLE 15 SP3https://progress.opensuse.org/issues/909232021-04-09T12:13:30Zgeorggkioulis@suse.com
<p>A <a href="https://openqa.suse.de/tests/5793735#" class="external">userspace_systemd</a> job is running on maintenance products but not on 15 SP3.</p>
<p>There already is a qa_userspace_systemd testsuite (defined but unscheduled).</p>
<p>It is needed to verify that there are no issues running it on 15 SP3.</p>
<p>After that the job can be scheduled in the Functional Job Group</p>
openQA Tests - action #89461 (Resolved): [qe-core][systemd] qa_test_systemd fails in check-mdmonitorhttps://progress.opensuse.org/issues/894612021-03-04T08:41:41Zgeorggkioulis@suse.com
<p>testcase <code>check-mdmonitor</code> of <code>qa_test_systemd</code> package fails in sle 15-SP1 and sle 15-SP2</p>
openQA Tests - coordination #69055 (Resolved): [qe-core][qem][openvswitch][epic][sprint] Increase...https://progress.opensuse.org/issues/690552020-07-16T14:43:24Zgeorggkioulis@suse.com
<p>According to <a href="https://jira.suse.com/browse/ECO-2242" class="external">ECO-2242</a> Openvswitch will include some new packages in 15 SP2:<br>
Those will be:</p>
<ul>
<li>openvswitch-ipsec</li>
<li>openvswitch-pki</li>
<li>openvswitch-test</li>
<li>openvswitch-vtep</li>
</ul>
<p>Also there is a new set of ovn packages, those have been split into another ticket <a href="https://progress.opensuse.org/issues/70501" class="external">https://progress.opensuse.org/issues/70501</a>.</p>
<p>There is need to expand openvswitch testing to cover relevant usecases.<br>
Before implementation this will require some investigation on what scenarios to include.</p>