openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-06-08T11:36:34ZopenSUSE Project Management Tool
Redmine qe-yam - action #93641 (Closed): Create schedules for opensuse test suiteshttps://progress.opensuse.org/issues/936412021-06-08T11:36:34Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently, we are trying to replace the old partitioning_filesystem module with guided_setup. There are some opensuse tests that use the old partitioning and don't have a schedule. The scope of this ticket is to search which are these tests and create schedule for them. There are some tests that use partitioning_filesystem, but do not concern yast team.</p>
<p>Tumbleweed:<br>
<a href="https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=partitioning_filesystem&distri=microos&distri=opensuse&version=Tumbleweed&build=20210606&groupid=1#" class="external">https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=partitioning_filesystem&distri=microos&distri=opensuse&version=Tumbleweed&build=20210606&groupid=1#</a></p>
<p>Leap:<br>
<a href="https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=partitioning_filesystem&distri=opensuse&version=15.3&build=160.3&groupid=50#" class="external">https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=partitioning_filesystem&distri=opensuse&version=15.3&build=160.3&groupid=50#</a></p>
<p>Also check other products (like Tumbleweed Aarch64) if there are more tests.</p>
<p>This tool can be helpful: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/script/yaml_generator" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/script/yaml_generator</a></p>
qe-yam - action #93411 (Closed): Create test cases for Language, Keyboard and Product Selectionhttps://progress.opensuse.org/issues/934112021-06-02T15:29:17Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Please, see motivation in the parent ticket.</p>
<p>Task</p>
<pre><code>Create test cases for "Language, Keyboard and Product selection" Screen
Find the cases that already automated and mark them as "Automated" in test cases (If something is automated not exactly as a test case, then note that in the test cases file)
</code></pre>
<p>Test Cases Requirements</p>
<pre><code>Please, use the attached file template from parent ticket (test_cases_template.ods) (In future we'll move the test cases to Test Management system);
Each test case should end up with Expected result;
For each functionality, add positive test cases first then negative ones;
Scope: SLE and openSUSE.
</code></pre>
<p>Suggestions</p>
<p>In case of any ambiguity, make things clear by asking all the teams, e.g. testers, developers.</p>
qe-yam - action #93032 (Closed): Use accept_license module with libyui-rest-api in all test suite...https://progress.opensuse.org/issues/930322021-05-24T11:03:29Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>There is <code>accept_license</code> module, implemented with LibyuiClient already: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm</a>. It is already used in <a href="https://openqa.suse.de/tests/5951331" class="external">installer_extended</a> test suite. </p>
<a name="Scope"></a>
<h2 >Scope:<a href="#Scope" class="wiki-anchor">¶</a></h2>
<p>Job Groups: YaST, openSUSE Tumbleweed, openSUSE Leap 15<br>
Test Cases: #1 - Accept license agreement (Please, see test cases in <a href="https://progress.opensuse.org/issues/93282" class="external">https://progress.opensuse.org/issues/93282</a>).</p>
<a name="Task"></a>
<h2 >Task<a href="#Task" class="wiki-anchor">¶</a></h2>
<ol>
<li>Replace the old <code>accept_license</code> module with the new <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">accept_license</a> module in all the test suites for SLE15-SP3 YaST Job Group;</li>
<li>Adapt existing implementation to be used on Tumbleweed and openSUSE Leap 15 also (i.e. use DistributionFactory to provide the proper controller for TW and Leap, so that the test module remains same, but implementation of <code>get_license_agreement()->accept_license()</code> is different), as on TW and Leap there is no checkbox for accepting License.</li>
<li>Replace the old <code>accept_license</code> module with the new <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/licensing/accept_license.pm" class="external">accept_license</a> module in all the test suites for Tumbleweed and openSUSE Leap 15. </li>
</ol>
<p><strong>Important Notes:</strong><br>
All the cases that do not related to accepting license are out of scope:</p>
<ul>
<li><code>switch_keyboard_gnome/textmode</code> is out of scope and will be implemented in separate ticket, so for now please leave the old 'welcome' module there for such cases;</li>
<li>Product Selection Screen is out of scope, it will be implemented in separate ticket.</li>
</ul>
<p>The new module should replace the old "accept_license" used in SLE, and "welcome" module used in opensuse. It should work for both textmode and graphical installations. Please see identified scenarios in <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="action: [timeboxed:16h] Define all the test scenarios in welcome and accept_license test modules (Closed)" href="https://progress.opensuse.org/issues/88939">#88939</a> as additional help.</p>
qe-yam - action #93029 (Closed): Implement test module for Product selection using LibyuiClient i...https://progress.opensuse.org/issues/930292021-05-24T10:57:43Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Until now, we are using welcome module for product selection on SLE. This covers multiple scenarios, as identified in <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="action: [timeboxed:16h] Define all the test scenarios in welcome and accept_license test modules (Closed)" href="https://progress.opensuse.org/issues/88939">#88939</a>. We should separate the scenarios and create separate modules.</p>
<a name="Scope"></a>
<h2 >Scope:<a href="#Scope" class="wiki-anchor">¶</a></h2>
<p><strong>Job Groups:</strong> YaST<br>
<strong>Test Cases:</strong> #1 - Select product for installation (Please, see test cases in <a href="https://progress.opensuse.org/issues/93411" class="external">https://progress.opensuse.org/issues/93411</a>), use SLES as a product to select.</p>
<a name="Task"></a>
<h2 >Task:<a href="#Task" class="wiki-anchor">¶</a></h2>
<ol>
<li>Implement test module for the test case using <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/ui-framework-documentation.md" class="external">Page Object Model</a> and LibyuiClient;</li>
<li>Check that the proper product is installed: <code>cat /etc/os-release</code> and check NAME field;</li>
<li>Add this module to all the Test Suites where currently <strong>only project selection</strong> is made (That means: do NOT update test suites where some additional actions except product selection are made, e.g. switch keyboard or validate install source. That will be scope of another ticket).</li>
</ol>
qe-yam - action #91830 (Resolved): Investigate if a change of DH version for TLS negotiation can...https://progress.opensuse.org/issues/918302021-04-27T13:14:15Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>There is an open bug for this issue, that seems stale: <a href="https://bugzilla.opensuse.org/show_bug.cgi?id=1183082" class="external">https://bugzilla.opensuse.org/show_bug.cgi?id=1183082</a><br>
According to the developers' insight, we might need to change the TLS negotiation. We should investigate if the current test configuration makes sense or should be changed.</p>
<p>openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-remote_vnc_controller@64bit fails in<br>
<a href="https://openqa.opensuse.org/tests/1716077/modules/remote_controller/steps/19" class="external">remote_controller</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Controller performs remote installation via vnc to the target</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.opensuse.org/tests/1655743" class="external">20210303</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.opensuse.org/tests/1653115" class="external">20210302</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.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=remote_vnc_controller&version=Tumbleweed" class="external">latest</a></p>
qe-yam - action #91677 (Rejected): [sporadic] test fails in validate_fs_tablehttps://progress.opensuse.org/issues/916772021-04-24T19:31:25Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>We are expecting both filesystems for root and home to be xfs as instructed in the test_data, but quite frequently, btrfs is selected, thus filesystem validation fails. We should stabilize the test to select xfs on every run.</p>
<p>openQA test in scenario sle-15-SP3-Online-s390x-xfs@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/5846924/modules/validate_fs_table/steps/15" class="external">validate_fs_table</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 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/5840675" class="external">176.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/5825916" class="external">174.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=xfs&version=15-SP3" class="external">latest</a></p>
qe-yam - action #91350 (Closed): [timeboxed:16h][sporadic] test fails in verify_undelete_snapshotshttps://progress.opensuse.org/issues/913502021-04-19T10:19:46Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The module fails when the system is creating a new snapshot and it is expecting it to be marked as disposable. On successful runs, the number of the created snapshot is 18 and it is marked as disposable. When the number of the snapshot is 11, it's not marked as disposable. We need to figure out if this behavior is per design and adjust the module expectations or open a bug.</p>
<p>Blind guess, if it's on powerVM only, we should check if there is any test suite executed between image is created and this test suite. Therefore we should check that there are no extra snapshots in some runs and clean them up before the test execution to have the same setup in each run.</p>
<p>openQA test in scenario sle-15-SP3-Online-ppc64le-transactional_server_snapper@ppc64le-hmc-single-disk fails in<br>
<a href="https://openqa.suse.de/tests/5840500/modules/verify_undelete_snapshots/steps/23" class="external">verify_undelete_snapshots</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Test snapper features in a transactional update server</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/5119908" class="external">95.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/5814802" class="external">174.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=ppc64le&distri=sle&flavor=Online&machine=ppc64le-hmc-single-disk&test=transactional_server_snapper&version=15-SP3" class="external">latest</a></p>
qe-yam - action #91136 (Rejected): Textmode test suite fails for s390x-kvmhttps://progress.opensuse.org/issues/911362021-04-14T13:20:42Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After implementing libyui for the mentioned tests, there is a strange network failure. The url that libyui is trying to connect to seems correct but the app doesn't connect successfully. The failure is the same for all machines:<br>
<a href="https://openqa.suse.de/tests/5814857#step/bootloader_start/30" class="external">https://openqa.suse.de/tests/5814857#step/bootloader_start/30</a> </p>
<p>Similar issue is visible on powerVM: <a class="issue tracker-4 status-5 priority-5 priority-high3 closed" title="action: [timeboxed:16h] libyui REST API cannot be accessed on powerVM (Closed)" href="https://progress.opensuse.org/issues/90776">#90776</a>, so might be that it's same issue for the both backends</p>
qe-yam - action #91130 (Closed): Use libyui for btrfs_libstorage-ng ipmi and zVMhttps://progress.opensuse.org/issues/911302021-04-14T13:15:03Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently we are using the old modules for the btrfs_libstorage-ng on the mentioned architectures. The libyui functionality shoudl be working after merging <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12298" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12298</a></p>
<p>For guided partitioning, there need to be additional steps implemented that will choose the disk(s) for the installation.<br>
Module tests/installation/partitioning/guided_setup.pm does not cover this option:<br>
<a href="https://openqa.suse.de/tests/5821208#step/guided_setup/2" class="external">https://openqa.suse.de/tests/5821208#step/guided_setup/2</a></p>
qe-yam - action #89932 (Closed): [sporadic] stabilize partitioning_firstdisk https://progress.opensuse.org/issues/899322021-03-11T13:44:06Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Failing test: select_disk <a href="https://openqa.suse.de/tests/5646458" class="external">https://openqa.suse.de/tests/5646458</a><br>
The mentioned module is not stable due to the needle use. It can confuse sda with sdd, due to resemblance of the letters. Plus, the conditions of the function "select_first_hard_disk" don't seem to be well defined. When the test (passes)[[https://openqa.suse.de/tests/5553616#step/partitioning_firstdisk/3]] there seems to be an check for all checkboxes, but when the test (fails)[[https://openqa.suse.de/tests/5646458#step/partitioning_firstdisk/4]] this check is missing. </p>
<p>We could make modifications in the current function to make it more precise or we can rewrite the module and use libyui.</p>
<p>Scope is only screen for selecting disk for the partitions, other steps will be covered in <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="action: Rewrite partition creation with libyui REST API in guided setup (Closed)" href="https://progress.opensuse.org/issues/87919">#87919</a></p>
qe-yam - action #88480 (Closed): [sporadic] boot_encrypt doesn't unlock encrypted disk for cryptl...https://progress.opensuse.org/issues/884802021-02-08T12:35:56Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>It seems that the wrong password is typed.</p>
<p>openQA test in scenario sle-15-SP3-Online-ppc64le-cryptlvm@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/5422061/modules/first_boot/steps/3" class="external">first_boot</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=Online&machine=ppc64le&test=cryptlvm&version=15-SP3" class="external">latest</a></p>
<p>Acceptance criteria:</p>
<ul>
<li>Add a stabilization check so that if disk is not unlocked, the password will be entered again.</li>
<li>If there is a tools issue worth investigating, open a new ticket.</li>
</ul>
qe-yam - action #87646 (Closed): Create autoyast test using btrfs quota limithttps://progress.opensuse.org/issues/876462021-01-12T14:55:23Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Automation test for feature : <a href="https://jira.suse.com/browse/SLE-7742" class="external">https://jira.suse.com/browse/SLE-7742</a><br>
Autoyast installation with btrfs quota limit for one or more subvolumes.</p>
<p>Autoyast syntax:<br>
<a href="https://github.com/yast/yast-storage-ng/pull/1186" class="external">https://github.com/yast/yast-storage-ng/pull/1186</a></p>
<p>Scope is tumbleweed and SLES 64bit.</p>
<p>Validate that limit was set, after installation:<br>
#btrfs subvolume list /mountpoint (in case we want to find a subvolume id)<br>
#btrfs qgroup show -pcre /mountpoint</p>
<a name="Acceptance-criteria"></a>
<h3 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h3>
<ol>
<li>btrfs quota limit is set in the autoyast profile</li>
<li>The limit is validated to be set, after installation</li>
</ol>
qe-yam - action #81248 (Rejected): test fails in snapshots_small_root on aarch64https://progress.opensuse.org/issues/812482020-12-21T13:42:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The warning for small root partition is successfully handled, but the cancellation of the partitioning is not taking effect, so the module is expecting for a second warning, related to losing changes, tries to press "yes" and receives the following error:</p>
<pre><code>Test died: Timed out:
Not Found
{ "error" : "Widget not found" }
http://localhost:39106/v1/widgets?action=press&id=yes at /var/lib/openqa/cache/openqa.suse.de/tests/sle/lib/YuiRestClient/Http/HttpClient.pm line 35.
</code></pre>
<p>Seems that the "cancel" button is not pressed.</p>
<p>openQA test in scenario sle-15-SP3-Online-aarch64-btrfs+warnings@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/5201644/modules/snapshots_small_root/steps/15" class="external">snapshots_small_root</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Test for feature with insufficient disk space on btrfs partition with snapshots.</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/5194534" class="external">109.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/5162094" class="external">102.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=btrfs%2Bwarnings&version=15-SP3" class="external">latest</a></p>
qe-yam - action #80276 (Closed): [sporadic][timeboxed:12h] autoyast_reinstall@s390x-kvm-sle12 fai...https://progress.opensuse.org/issues/802762020-11-24T10:36:50Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>During installation on s390x-kvm-sle12, the worker is trying to use pty but even though grub seems to be loaded after failure, it might take longer than expected.</p>
<p>To try reproducing issue manually see <a href="https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/Manual_Testing_Guide.md#zkvm" class="external">https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/Manual_Testing_Guide.md#zkvm</a></p>
<p>Investigate the issue and the failure frequency.</p>
<p>Maybe increasing the timeout would solve it.</p>
<p>openQA test in scenario sle-15-SP3-Online-s390x-autoyast_reinstall@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/5056227/modules/installation/steps/21" class="external">installation</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Parent job produces autoyast profile after successful completion. This test uses generated profile to do autoyast installation.</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/4725426#step/installation/21" class="external">44.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/4965151" class="external">78.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=autoyast_reinstall&version=15-SP3" class="external">latest</a></p>
qe-yam - action #80272 (Closed): Adapt yast2_expert_partitioner (before: yast2_storage_ng) in ppc...https://progress.opensuse.org/issues/802722020-11-24T10:24:44Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-yast2_gui@64bit fails in<br>
<a href="https://openqa.suse.de/tests/5058960/modules/yast2_storage_ng/steps/21" class="external">yast2_storage_ng</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: zluo, riafarov</p>
<p>Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.</p>
<p>We can use perl code, need just to add setup part including port forwarding.<br>
After <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11643" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11643</a> we still need to setup libyui for ppc64le and enable this test there.</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/5032565" class="external">85.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/4965755" class="external">78.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=64bit&test=yast2_gui&version=15-SP3" class="external">latest</a></p>