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 #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 #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 #105449 (Resolved): Create new test module for testing multipathhttps://progress.opensuse.org/issues/1054492022-01-25T17:39:35Zgeorggkioulis@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 and the <a href="https://openqa.suse.de/tests/latest?distri=sle&flavor=Online&test=zfcp&version=15-SP4" class="external">zfcp testsuite</a> needs a new test module to validate multipathing.</p>
<a name="Task"></a>
<h2 >Task<a href="#Task" class="wiki-anchor">¶</a></h2>
<p>The idea is to check the status of the known infrastructure, and the status of multipathing on top of it.</p>
<p><strong>AC1</strong>: Verify that there are two host bus adapters attached, and that the corresponding channels (<code>0.0.fa00, 0.0.fc00</code>) are listed</p>
<pre><code># ls -l /sys/class/fc_host
total 0
lrwxrwxrwx 1 root root 0 Dec 19 17:53 host0 -> ../../devices/css0/0.0.0005/0.0.fa00/host0/fc_host/host0
lrwxrwxrwx 1 root root 0 Dec 19 17:53 host1 -> ../../devices/css0/0.0.0006/0.0.fc00/host1/fc_host/host1
</code></pre>
<p><strong>AC2</strong>: Based on the output of lsscsi:</p>
<pre><code># lsscsi -xxgst
[0:0:0:0x4001403200000000] disk fc:0x500507630703d3b30x760f00 /dev/sda /dev/sg0 214GB
[0:0:0:0x4001405000000000] disk fc:0x500507630703d3b30x760f00 /dev/sdb /dev/sg1 42.9GB
[0:0:1:0x4001403200000000] disk fc:0x500507630708d3b30x761000 /dev/sdc /dev/sg2 214GB
[0:0:1:0x4001405000000000] disk fc:0x500507630708d3b30x761000 /dev/sdd /dev/sg3 42.9GB
[1:0:0:0x4001403200000000] disk fc:0x500507630718d3b30x771000 /dev/sde /dev/sg4 214GB
[1:0:0:0x4001405000000000] disk fc:0x500507630718d3b30x771000 /dev/sdf /dev/sg5 42.9GB
[1:0:1:0x4001403200000000] disk fc:0x500507630713d3b30x770f00 /dev/sdg /dev/sg6 214GB
[1:0:1:0x4001405000000000] disk fc:0x500507630713d3b30x770f00 /dev/sdh /dev/sg7 42.9GB
</code></pre>
<ul>
<li>verify that there are 8 SCSI block devices listed (as a result of having two adapters, two hard disks and two paths to each disk, 2<sup>3</sup> = 8)</li>
<li>verify that LUN <code>0x4001403200000000</code> corresponds to the 214GB disk, and LUN <code>0x4001405000000000</code> to the 42.9GB disk</li>
</ul>
<p><strong>AC3</strong>: Based on the output of multipath -l:</p>
<pre><code># multipath -l
36005076307ffd3b30000000000000132 dm-0 IBM,2107900
size=200G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=0 status=enabled
|- 0:0:0:1077035009 sda 8:0 active undef running
|- 0:0:1:1077035009 sdc 8:32 active undef running
|- 1:0:0:1077035009 sde 8:64 active undef running
`- 1:0:1:1077035009 sdg 8:96 active undef running
36005076307ffd3b30000000000000150 dm-41 IBM,2107900
size=40G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=0 status=enabled
|- 0:0:0:1079001089 sdb 8:16 active undef running
|- 0:0:1:1079001089 sdd 8:48 active undef running
|- 1:0:1:1079001089 sdh 8:112 active undef running
`- 1:0:0:1079001089 sdf 8:80 active undef running
</code></pre>
<p><strong>AC4</strong>: Enable the validation in YaST group and Maintenance.</p>
<ul>
<li>verify that the multipath device with WWID <code>36005076307ffd3b30000000000000132</code> corresponds to the 200G disk and the multipath device with WWID <code>36005076307ffd3b30000000000000150</code> to the 40G disk</li>
<li>verify that there are 4 block devices listed for each virtual multipath device, and those corresponds to the right LUN (1077035009 and 1079001089)</li>
</ul>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<p>It might help to 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> for some more insight on the output of the above commands.</p>
<a name="Note"></a>
<h3 >Note<a href="#Note" class="wiki-anchor">¶</a></h3>
<p>This ticket requires that <a href="https://progress.opensuse.org/issues/105440" class="external">poo#105440</a> has been completed.</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 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>
openQA Tests - action #96986 (Workable): [qe-core][sporadic][samba_adcli] net ads join / leave failshttps://progress.opensuse.org/issues/969862021-08-16T13:36:01Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><code>net ads join</code> occasionally fails in <a href="https://openqa.suse.de/tests/6838830#step/samba_adcli/55" class="external">samba_adcli</a></p>
<p>The command <code>net ads join --domain geeko.com -U Administrator --no-dns-updates -i</code> occasionally fails with:</p>
<pre><code>ads_print_error: AD LDAP ERROR: 53 (Server is unwilling to perform): 0000001F: SvcErr: DSID-031A1236, problem 5003 (WILL_NOT_PERFORM), data 0
</code></pre>
<p>similar issue for the command <code>net ads leave --domain geeko.com -U Administrator -i'</code></p>
<p>For now it has been softfailed.</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/6839956#step/samba_adcli/60" class="external">ge0r/os-autoinst-distri-opensuse#retry-adcli-join</a> (or more recent)</p>
openQA Tests - action #96983 (Workable): [qe-core][sporadic][samba_adcli] adcli joining domain failshttps://progress.opensuse.org/issues/969832021-08-16T13:24:46Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>adcli join fails in <a href="https://openqa.suse.de/tests/6840326/modules/samba_adcli/steps/220" class="external">samba_adcli</a></p>
<p>The command <code>adcli join -v -W --domain geeko.com -U Administrator -C</code> sporadically results in :</p>
<pre><code>Couldn't perform discovery search: Can't contact LDAP server
* Received NetLogon info from: WIN-NHOU56DRDK4.geeko.com
! Cannot set computer password: Authentication error
adcli: joining domain geeko.com failed: Cannot set computer password: Authentication error
</code></pre>
<p>Increasing the number of retries just reduces the frequency of the failure. For now it has been softfailed.</p>
<p>The expected output of the aforementioned <code>adcli join</code> command can be seen <a href="https://openqa.suse.de/tests/6839956#step/samba_adcli/226" class="external">here</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/6840326" class="external">ge0r/os-autoinst-distri-opensuse#retry-adcli-join</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/6839956" class="external">ge0r/os-autoinst-distri-opensuse#retry-adcli-join</a> (or more recent)</p>
openQA Tests - coordination #96980 (Workable): [qe-core][samba_adcli][epic] Tracker for samba_adc...https://progress.opensuse.org/issues/969802021-08-16T13:23:29Zgeorggkioulis@suse.comopenQA Tests - action #96513 (Workable): [qe-core][sporadic][samba_adcli] wbinfo failshttps://progress.opensuse.org/issues/965132021-08-03T12:18:07Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Server-DVD-Updates-aarch64-mau-extratests2@aarch64-virtio fails in<br>
<a href="https://openqa.suse.de/tests/6630974/modules/samba_adcli/steps/78" class="external">samba_adcli</a></p>
<p>Test samba_adcli sporadicly fails due to wbinfo failures<br>
eg <code>wbinfo -u</code> fails with <code>Error looking up domain users</code></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Run console tests against aggregated test repo</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/6630974" class="external">20210802-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/6628144" class="external">20210801-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=Server-DVD-Updates&machine=aarch64-virtio&test=mau-extratests2&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #95611 (Workable): [qe-core][samba_adcli] test fails in samba_adcli in s390...https://progress.opensuse.org/issues/956112021-07-19T08:30:46Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Server-DVD-Updates-s390x-Build20210719-1-mau-extratests2@s390x-kvm-sle12 fails in <a href="https://openqa.suse.de/tests/6483346#step/samba_adcli/60" class="external">samba_adcli</a></p>
<p>From what I understand, the samba_adcli module has never been run for s390. </p>
<p>The <code>adcli join -v -W --domain geeko.com -U Administrator -C</code> does not work, even with multiple retries, possibly is a network access problem on one of the lpars</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ol>
<li>Run a manual installation or use an image on an s390 kvm machine and/or lpar (zkvm), and try to run the steps manually</li>
<li>If step above works, trigger a job in openQA and use developer mode (Trigger the job with PAUSE_AT=samba_adcli and use <a href="https://confluence.suse.com/pages/viewpage.action?pageId=742719853" class="external">this page</a> to figure out how to connect to the running machine, possibly for s390 zkvm the procedure might be different, ping szarate) and debug the network (starting with trying to ssh Administrator@$AD_ip/windows machine).</li>
<li>Update test module/and/or modify host, create follow up tickets as needed</li>
</ol>
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 #91899 (Resolved): [qe-core] 15SP2 QU - An error occured during the install...https://progress.opensuse.org/issues/918992021-04-28T10:11:12Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Full-QR-ppc64le-RAID6@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/5891733/modules/setup_libyui/steps/3" class="external">setup_libyui</a></p>
<p>Installation of RAID6 using expert partitioner</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/5884567" class="external">390.3</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/5836424#step/setup_libyui/1" class="external">setup_libyui</a></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=ppc64le&distri=sle&flavor=Full-QR&machine=ppc64le&test=RAID6&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #72037 (Workable): [yast][security][qem][shim] Enable shim testing on barem...https://progress.opensuse.org/issues/720372020-09-28T16:37:18Zgeorggkioulis@suse.com
<p>Although we do have openQA runs with secure boot, there is need for <code>shim</code> testing on baremetal machine with secure boot.</p>
<p>probably the following would need to be scheduled:</p>
<ul>
<li>security/mokutil_sign.pm</li>
<li>console/verify_efi_mok.pm</li>
</ul>