openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-04-24T19:31:25ZopenSUSE Project Management Tool
Redmine 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 #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 #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 #75424 (Closed): [sporadic] test fails in force_scheduled_tasks https://progress.opensuse.org/issues/754242020-10-27T20:16:16Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Full medium test suites skip_registration and allmodules+allpatterns+registration fail sporadically for aarch64 in force_scheduled_tasks. The module is running in a loop:</p>
<pre><code>read load dummy < /proc/loadavg ; top -n1 -b| head -n30 ; test "${load/./}" -lt $limit && break ;
</code></pre>
<p>and is expected to be finished in 1005 seconds, but it times out.<br>
In all failures spotted so far, the serial returned the same output at the moment of timeout </p>
<pre><code>BTRFS info (device vda2): qgroup scan completed (inconsistency flag cleared)
</code></pre>
<p>so there could be some BTRFS inconsistency that is taking too long to be dealt with by the system.</p>
<p>As we cannot run proper performance tests and goal of the module is to improve stability of the tests.</p>
<p>failures:<br>
<a href="https://openqa.suse.de/tests/4893533/modules/force_scheduled_tasks/steps/6" class="external">allmodules+allpatterns+registration</a><br>
<a href="https://openqa.suse.de/tests/4893537#next_previous" class="external">skip_registration</a></p>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/4879296" class="external">67.1</a> </p>
<p><a href="https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Full&machine=aarch64&test=allmodules%2Ballpatterns%2Bregistration&version=15-SP3" class="external">latest allmodules+allpatterns+registration</a><br>
<a href="https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Full&machine=aarch64&test=skip_registration&version=15-SP3" class="external">latest skip_registration</a></p>
qe-yam - action #73096 (Rejected): [sporadic] msdos test fails in validate_fs_tablehttps://progress.opensuse.org/issues/730962020-10-07T15:14:47Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>During msdos partitioning, the home partition is selected to be created with UDF instead of xfs filesystem. Even though, the screen matches at xfs, there is an extra key sent and the result is that home filesystem is UDF and the filesystem validation fails:</p>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-msdos@svirt-xen-pv fails in<br>
<a href="https://openqa.suse.de/tests/4787764/modules/validate_fs_table/steps/28" class="external">validate_fs_table</a></p>
<p>Similar behavior has been seen before for SWAP partition but was not investigated:<br>
<a href="https://progress.opensuse.org/issues/71638" class="external">https://progress.opensuse.org/issues/71638</a></p>
<p>So we should stabilize test execution that we do not end up sending one extra key press, after wanted filesystem is selected.</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/4780316" class="external">51.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-pv&test=msdos&version=15-SP3" class="external">latest</a></p>
qe-yam - action #71116 (Closed): [y] Add OpenQA test for OneClickInstallhttps://progress.opensuse.org/issues/711162020-09-08T16:03:45Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Packages can be installed via .YMP files that contain the necessary information in XML form, using OneclickInstall.<br>
As root run<br>
#OneClickInstallCLI <br>
and verify that the package is installed successfully. Accordingly, test the OneClickInstall UI<br>
#OneClickInstallUI </p>
<p>YMP URL example: <a href="https://software.opensuse.org/ymp/openSUSE:Factory/standard/vim.ymp?base=openSUSE%3AFactory&query=vim" class="external">https://software.opensuse.org/ymp/openSUSE:Factory/standard/vim.ymp?base=openSUSE%3AFactory&query=vim</a></p>
<p>The test can run on both SLE and Tumbleweed, but with different YMP URLs, but only 64-bit for a start.</p>
openQA Tests - action #69751 (Resolved): [y] Module validate_encrypt fails on s390x-kvm-sle12https://progress.opensuse.org/issues/697512020-08-10T07:45:25Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Seems to be related to <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/0dabd841cf1cd34f5fb78e17970f08d1a97574f6" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/0dabd841cf1cd34f5fb78e17970f08d1a97574f6</a></p>
<p>openQA test in scenario sle-15-SP3-Online-s390x-lvm-encrypt-separate-boot@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/4554601/modules/validate_encrypt/steps/21" class="external">validate_encrypt</a></p>
<p>It's just zkvm affected</p>
<p>openQA test in scenario sle-15-SP2-Online-s390x-lvm-full-encrypt@s390x-kvm-sle12 and lvm-encrypt-separate-boot@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/4541327/modules/validate_encrypt/steps/21" class="external">validate_encrypt</a><br>
or <br>
<a href="https://openqa.suse.de/tests/4541308#step/validate_encrypt/22" class="external">validate_encrypt</a></p>
<p>Looks like the command </p>
<pre><code>command 'cryptsetup -v luksHeaderBackup /dev/disk/by-path/ccw-0.0.0000-part3 --header-backup-file /root//dev/disk/by-path/ccw-0.0.0000-part3
</code></pre>
<p>needs some modification for the particular machine.</p>
<p>The failure message is the bellow</p>
<pre><code># Test died: command 'cryptsetup -v luksHeaderBackup /dev/disk/by-path/ccw-0.0.0000-part3 --header-backup-file /root//dev/disk/by-path/ccw-0.0.0000-part3' failed at /var/lib/openqa/cache/openqa.suse.de/tests/sle/lib/validate_encrypt_utils.pm line 92.
</code></pre>
<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/4424857" class="external">209.2</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=lvm-full-encrypt&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #67732 (Resolved): [functional][y] Add yast2_lang module for other than 64...https://progress.opensuse.org/issues/677322020-06-04T10:57:53Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>On step :<br>
<a href="https://openqa.suse.de/tests/4312187#step/yast2_lang/27" class="external">https://openqa.suse.de/tests/4312187#step/yast2_lang/27</a></p>
<p>The needle matching area is not properly specified. As a result, when running the module on different architectures, Croatian is selected and the module fails.</p>
<p>Create new needle that will be more specific (code changes might be necessary) and delete old needles that shouldn't be used.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>yast2_lang is executed on all architectures</li>
</ol>
openQA Tests - action #67534 (Resolved): [functional][y] Change yast2_lan hostname validationhttps://progress.opensuse.org/issues/675342020-06-01T12:22:37Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In yast2_lan module, one of the steps is to verify that the hostname can be successfully changed. Currently in the code, the hostname used for the change comes from: <code>$hostname = get_var('HOSTNAME', 'susetest')</code> . For most architectures 'susetest' is also the hostname prior the change. So, in reality it doesn't verify if the hostname was changed ( <a href="https://openqa.suse.de/tests/4286250#step/yast2_lan/13" class="external">https://openqa.suse.de/tests/4286250#step/yast2_lan/13</a> ).</p>
<p>On some backends we cannot change hostname without breaking the setup (at least powerVM and zVM). So we might need to limit scope of test to qemu.</p>
<p>Running the module on xen hvm, where original hostname is not 'susetest', fails (<a href="https://openqa.suse.de/tests/4295089#step/yast2_lan/20" class="external">https://openqa.suse.de/tests/4295089#step/yast2_lan/20</a>).<br>
Running the module on x86, with different $hostname works (new needle needed for that to work) (<a href="http://falafel.suse.cz/tests/832#step/yast2_lan/23" class="external">http://falafel.suse.cz/tests/832#step/yast2_lan/23</a>).</p>
<p>Acceptance criteria:</p>
<ul>
<li>Change the code of yast2_lan so that the hostname after change is different than before.</li>
</ul>
qe-yam - action #67126 (Resolved): [functional][y] Add validation module for nis mm testshttps://progress.opensuse.org/issues/671262020-05-21T16:02:56Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In order to verify that "yast nis_server" and "yast nis" configuration on nis mm tests, works properly, a new module can be created for each test with following steps:</p>
<p>NIS server:<br>
(as root)</p>
<ul>
<li>useradd nis_user -> in the current test, /home/nis_user folder is created and shared via nfs, so in order to avoid extra steps, the user added should be "nis_user".</li>
<li>passwd nis_user</li>
<li>chmod nis_user:users /home/nis_user -> current owner of the folder is "root".</li>
<li>cd /var/yp </li>
<li>make -> nis database needs to be aware of the new user.</li>
<li>Check if /etc/defaultdomain and /etc/idmapd.conf contain the nis domain (nis.openqa.suse.de). At maps setup of nis_server module, all entries are selected. There can be a check in /var/yp/nis.openqa.suse.de/ if entries correspond</li>
</ul>
<p>NIS client:<br>
(after above actions on nis server are completed)</p>
<ul>
<li>ypcat passwd | grep nis_user / ypmatch nis_user passwd / getent passwd nis_user -> one option out of three, in order to verify that the client connection to nis server database is successful and new user is visible.</li>
<li>su - nis_user</li>
<li>pwd -> verify home directory of nis_user is /home/nis_user</li>
<li>echo "nis works"> file1 -> verify write </li>
<li>grep "nis works" -> verify read</li>
<li>Check if /etc/yp.conf exists and has the entry "ypserv"</li>
<li>Check if /etc/nsswitch.conf has expected entries e.g. "netgroup: files nis"</li>
<li>Check if /etc/defaultdomain contains the nis domain</li>
</ul>
<p>We should also extract settings to use same value for configuration and validation.</p>
openQA Tests - action #67117 (Resolved): [functional][y]test fails in yast2_proxy and yast2_dns_s...https://progress.opensuse.org/issues/671172020-05-21T12:03:55Zsyrianidou_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-SP2-Online-x86_64-yast2_ncurses_gnome@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4264234/modules/yast2_proxy/steps/23" class="external">yast2_proxy</a></p>
<p>When needle <a href="https://openqa.suse.de/tests/4264234#step/yast2_proxy/9">https://openqa.suse.de/tests/4264234#step/yast2_proxy/9</a> is matched, the system should choose "Start", verify the selection and then proceed with rest of the module yast2_proxy steps. In the autoinst logs:</p>
<pre><code>[2020-05-21T07:14:41.839 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_after_writing_conf", timeout=1)
�[32m[2020-05-21T07:14:41.961 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_start_after_writing_conf-20180827, similarity 1.00 @ 336/320
�[0m[2020-05-21T07:14:41.961 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:77 called testapi::send_key
[2020-05-21T07:14:41.962 CEST] [debug] <<< testapi::send_key(key="alt-a", wait_screen_change=0, do_wait=0)
[2020-05-21T07:14:42.297 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:78 called testapi::send_key
[2020-05-21T07:14:42.297 CEST] [debug] <<< testapi::send_key(key="end", do_wait=0, wait_screen_change=0)
[2020-05-21T07:14:42.565 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:79 called testapi::send_key_until_needlematch
[2020-05-21T07:14:42.565 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_on_boot_after_reboot", timeout=1)
�[37m[2020-05-21T07:14:42.910 CEST] [debug] no match: 2.7s, best candidate: yast2_proxy-yast2_ncurses_service_start_on_boot_after_reboot-20180827 (0.29)
</code></pre>
<p>Looks like the sent keys don't have the expected effect on the test. The worker is looking for the next needle "yast2_ncurses_service_start_on_boot_after_reboot" without actually verifying "yast2_ncurses_service_check_start_after_writing_conf" needle. </p>
<p>In test <a href="https://openqa.suse.de/tests/4231081#step/yast2_proxy/10">https://openqa.suse.de/tests/4231081#step/yast2_proxy/10</a> , where the result is the expected one, the autoinst logs:</p>
<pre><code>[2020-05-13T19:17:44.759 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_after_writing_conf", timeout=1)
[2020-05-13T19:17:44.968 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_start_after_writing_conf-20180827, similarity 1.00 @ 336/320
[2020-05-13T19:17:44.968 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:55 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:81 called testapi::send_key
[2020-05-13T19:17:44.969 CEST] [debug] <<< testapi::send_key(key="ret", do_wait=0, wait_screen_change=0)
[2020-05-13T19:17:45.255 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:55 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:82 called testapi::assert_screen
[2020-05-13T19:17:45.256 CEST] [debug] <<< testapi::assert_screen(mustmatch="yast2_ncurses_service_check_start_after_writing_conf", timeout=30)
[2020-05-13T19:17:45.945 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_check_start_after_writing_conf-20180827, similarity 1.00 @ 454/289
[2020-05-13T19:17:45.945 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:77 called testapi::send_key
[2020-05-13T19:17:45.945 CEST] [debug] <<< testapi::send_key(key="alt-a", wait_screen_change=0, do_wait=0)
[2020-05-13T19:17:46.281 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:78 called testapi::send_key
[2020-05-13T19:17:46.282 CEST] [debug] <<< testapi::send_key(key="end", do_wait=0, wait_screen_change=0)
[2020-05-13T19:17:46.552 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:79 called testapi::send_key_until_needlematch
[2020-05-13T19:17:46.552 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_on_boot_after_reboot", timeout=1)
[2020-05-13T19:17:46.879 CEST] [debug] no match: 2.7s, best candidate: yast2_proxy-yast2_ncurses_service_start_on_boot_after_reboot-20180827 (0.29)
</code></pre>
<p>looks like after the first needle much, 'ret' should be sent instead of 'alt-a' and 'end' that would be expected after the matching "yast2_proxy-yast2_ncurses_service_check_start_after_writing_conf" .</p>
<p>The issue needs further investigation and possibly, follow up ticket with tools team.</p>
openQA Tests - action #64466 (Resolved): [functional][y][hyper-v][timeboxed:16h] test fails in sh...https://progress.opensuse.org/issues/644662020-03-12T13:14:17Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Sporadic failure in shutdown module. Two types of failures observed:</p>
<ul>
<li>Display at password prompt is distorted and cause needle match failure ( <a href="https://openqa.suse.de/tests/3969518#step/shutdown/10">https://openqa.suse.de/tests/3969518#step/shutdown/10</a> )</li>
<li>After password is entered, system doesn't show desktop. ( <a href="https://openqa.suse.de/tests/3982260#step/shutdown/15">https://openqa.suse.de/tests/3982260#step/shutdown/15</a> ). According to autoinst-log, provided password was incorrect and then system "Stopped target Current graphical user session."</li>
</ul>
<p>As per Yanis, it fails constantly on uefi. Seems that it's issues with openQA setup, as Yanis managed to shutdown the system and it worked just fine. So we need to identify the actions needed to fix it.</p>
<p>[ 675.237199] gnome-keyring-daemon[2603]: couldn't initialize slot with master password: The password or PIN is incorrect</p>
<p>[ 675.297939] gdm-password][4597]: gkr-pam: unlocked login keyring</p>
<p>[2020-03-12T12:29:22.895 CET] [debug] tests/shutdown/shutdown.pm:28 called power_action_utils::power_action -> lib/power_action_utils.pm:255 called testapi::select_console -> lib/susedistribution.pm:883 called x11utils::ensure_unlocked_desktop -> lib/x11utils.pm:126 called testapi::wait_still_screen<br>
[2020-03-12T12:29:22.895 CET] [debug] <<< testapi::wait_still_screen(similarity_level=47, timeout=30, stilltime=1)<br>
[ 675.471356] systemd[4428]: Stopped target Current graphical user session.</p>
<p>[ 675.803774] systemd[4428]: Stopped target GNOME X11 Session (session: gnome-login).</p>
<p>[ 675.914330] gdm-Xorg-:1[4408]: (II) event3 - Microsoft Vmbus HID-compliant Mouse: device removed</p>
<p>[ 675.994240] gdm-Xorg-:1[4408]: (II) event4 - Power Button: device removed</p>
<p>[ 676.108023] gdm-Xorg-:1[4408]: (II) event2 - AT Translated Set 2 keyboard: device removed</p>
<p>[ 676.167890] gdm-Xorg-:1[4408]: (II) event0 - AT Translated Set 2 keyboard: device removed</p>
<p>[ 676.223982] gdm-Xorg-:1[4408]: (II) event1 - TPPS/2 IBM TrackPoint: device removed</p>
<p>[ 676.276254] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.316927] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.358856] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.418850] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.487558] gdm-Xorg-:1[4408]: (II) UnloadModule: "libinput"</p>
<p>[ 676.546600] gdm-Xorg-:1[4408]: (II) Server terminated successfully (0). Closing log file.</p>
<p>[ 676.648098] gnome-session[4457]: gnome-session-binary[4457]: WARNING: Lost name on bus: org.gnome.SessionManager</p>
<p>[ 676.732171] gdm-launch-environment][4424]: pam_unix(gdm-launch-environment:session): session closed for user gdm</p>
<p>[ 676.834667] systemd[4428]: Stopped target GNOME Session.</p>
<p>[ 676.908222] gnome-session[4457]: Unable to init server: Could not connect: Connection refused</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Full-x86_64-skip_registration@svirt-hyperv fails in<br>
<a href="https://openqa.suse.de/tests/3982260/modules/shutdown/steps/14" class="external">shutdown</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/3658083#step/shutdown/10" class="external">101.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/3978952" class="external">154.1</a></p>
openQA Tests - action #63814 (Resolved): [functional][y][virtualization][hyperv][timeboxed:12h] m...https://progress.opensuse.org/issues/638142020-02-25T12:24:34Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Even though same module works for other architectures, validate_fs_table cannot verify that partitions were successfully created.</p>
<p>The point of the code that fails is when the output of command "lsblk -n", split at every new line, is saved in @lsblk_output and it is parsed by:</p>
<p>foreach (@lsblk_output) {<br>
if ($_ =~ /(?\Q$args->{mount_point}\E\z)/) {<br>
$check = $+{check};<br>
last;<br>
}</p>
<p>On step <a href="https://openqa.suse.de/tests/3904536#step/validate_fs_table/14" class="external">https://openqa.suse.de/tests/3904536#step/validate_fs_table/14</a><br>
it is shown that the mount point "/" is indeed created, but it cannot be identified by "$_ =~ /(?\Q$args->{mount_point}\E\z)/".</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Online-x86_64-msdos@svirt-hyperv fails in<br>
<a href="https://openqa.suse.de/tests/3904536/modules/validate_fs_table/steps/16" class="external">validate_fs_table</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Always.</p>