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>
openQA Tests - action #69754 (Resolved): [y][u] tests fail in bootloader_start for ppc64le - Powe...https://progress.opensuse.org/issues/697542020-08-10T08:09:03Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>For the time being, some machines are turned off, see: <a href="https://mailman.suse.de/mlarch/SuSE/maxtorhof/2020/maxtorhof.2020.08/msg00005.html" class="external">https://mailman.suse.de/mlarch/SuSE/maxtorhof/2020/maxtorhof.2020.08/msg00005.html</a></p>
<p>All openqa ppc64le-hmc-single-disk or ppc64le-hmc-4disk test suites fail in bootloader_start or bootloader with the following error message<br>
<a href="https://openqa.suse.de/tests/4543002/modules/bootloader_start/steps/6" class="external">bootloader_start</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since 9th of August (<a href="https://openqa.suse.de/tests/4541148" class="external">https://openqa.suse.de/tests/4541148</a>)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good 6th of August (<a href="https://openqa.suse.de/tests/4528757" class="external">https://openqa.suse.de/tests/4528757</a>)</p>
openQA Tests - action #69658 (Resolved): [y] test fails in yast2_control_centerhttps://progress.opensuse.org/issues/696582020-08-06T14:17:05Zsyrianidou_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_gui@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4528958/modules/yast2_control_center/steps/84" class="external">yast2_control_center</a></p>
<p>The needle yast2-control-center-security-center is too generic and validation can be premature, leading to test failure. </p>
<p>In this case, the needle matching happened before typing was finished and assert_and_click did not work as expected:<br>
<a href="https://openqa.suse.de/tests/4528958#step/yast2_control_center/81" class="external">https://openqa.suse.de/tests/4528958#step/yast2_control_center/81</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Sporadic failure</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/4446522" class="external">209.2</a> (or more recent)</p>
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>