openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-08-01T11:49:49ZopenSUSE Project Management Tool
Redmine qe-yam - action #133616 (Rejected): agama full_disk_encryption and lvm tests fail due to changes...https://progress.opensuse.org/issues/1336162023-08-01T11:49:49Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The latest changes in Agama live image is that only dolomite is available for installation, no ALM micro or server. Therefore, we need to adjust our playwright test lvm and full_disk_encryption that currently fail. The Tumbleweed test will remain as is, because tumbleweed is still available.</p>
<p><a href="https://openqa.opensuse.org/tests/overview?distri=alp&version=agama-2.1-staging&build=2.17&groupid=96" class="external">https://openqa.opensuse.org/tests/overview?distri=alp&version=agama-2.1-staging&build=2.17&groupid=96</a></p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario alp-agama-2.1-staging-agama-live-default-Playwright-x86_64-agama_dolomite_full_disk_encryption@64bit-2G fails in<br>
<a href="https://openqa.opensuse.org/tests/3470423/modules/agama_full_disk_encryption/steps/6" class="external">agama_full_disk_encryption</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>The base test suite is used for job templates defined in YAML documents. It has no settings of its own.</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/3468486" class="external">2.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.opensuse.org/tests/3457233" class="external">2.5</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=alp&flavor=agama-live-default-Playwright&machine=64bit-2G&test=agama_dolomite_full_disk_encryption&version=agama-2.1-staging" class="external">latest</a></p>
openQA Tests - action #68764 (Rejected): [functional][y] yast2_gui@svirt-xen-hvm fails when retri...https://progress.opensuse.org/issues/687642020-07-08T12:25:12Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Test suite yast2_gui@svirt-xen-hvm is set to START_AFTER_TEST=create_hdd_gnome. When a new build is triggering all test suites, create_hdd_gnome@svirt-xen-hvm fails and yast2_gui@svirt-xen-hvm is skipped as expected. <br>
<a href="https://openqa.suse.de/tests/4342327#dependencies" class="external">https://openqa.suse.de/tests/4342327#dependencies</a></p>
<p>If we trigger yast2_gui@svirt-xen-hvm, it would be expected that create_hdd_gnome@svirt-xen-hvm should be triggered as well but this doesn't happen, resulting in failure as the dependent test can't find HDD_1.<br>
<a href="https://openqa.suse.de/tests/4424999" class="external">https://openqa.suse.de/tests/4424999</a></p>
<pre><code>[error] [pid:6204] Failed to download SLES-15-SP2-x86_64-Build209.2@svirt-xen-hvm-gnome.qcow2 to /var/lib/openqa/cache/openqa.suse.de/SLES-15-SP2-x86_64-Build209.2@svirt-xen-hvm-gnome.qcow2
</code></pre> 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 #67672 (Rejected): [functional][y] Extend coverage of yast2_gui test moduleshttps://progress.opensuse.org/issues/676722020-06-03T12:02:54Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>There are some modules on the test that fail, due to needle mismatch. Currently the modules are removed from the schedule for the architectures that fail.</p>
<p>s390-> yast2_datetime, yast2_bootloader, yast2_lang <br>
xen-hvm -> yast2_network_settings<br>
ppc -> yast2_bootloader, yast2_lang<br>
aarch64 -> yast2_bootloader</p>
<p>Create the necessary needles and enable the modules on the yast2_gui schedule. For ppc and aarch64, possible the same needles created for s390 would work.</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 #67120 (Resolved): [functional][y]test fails in zypper_ref while trying to ...https://progress.opensuse.org/issues/671202020-05-21T12:50:28Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Related to this change: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10288">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10288</a></p>
<p>openQA test in scenario sle-15-SP2-Online-ppc64le-lvm@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/4264225/modules/zypper_ref/steps/2" class="external">zypper_ref</a></p>
<p><a href="https://openqa.suse.de/tests/4247142" class="external">Last good</a> was using root-console, but after <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/4e9cca349646152944d403c221b8322ac6842a72#diff-aff3537aeb29a78d33dc1fc514ab716dR26">https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/4e9cca349646152944d403c221b8322ac6842a72#diff-aff3537aeb29a78d33dc1fc514ab716dR26</a><br>
the module is attempting to use virtio console due to <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/opensusebasetest.pm#L1098">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/opensusebasetest.pm#L1098</a> , but fails. Even though the commit looks like it's 22 days old and last good already had VIRTIO_CONSOLE=1, it didn't use the root-virtio-console. </p>
<p>Last good autoinst.log:</p>
<pre><code>[2020-05-16T11:57:49.052 CEST] [debug] ||| starting zypper_ref tests/console/zypper_ref.pm
[2020-05-16T11:57:49.053 CEST] [debug] tests/console/zypper_ref.pm:25 called testapi::select_console
[2020-05-16T11:57:49.053 CEST] [debug] <<< testapi::select_console(testapi_console="root-console")
[2020-05-16T11:57:49.859 CEST] [debug] tests/console/zypper_ref.pm:25 called testapi::select_console -> lib/susedistribution.pm:883 called testapi::assert_screen
[2020-05-16T11:57:49.859 CEST] [debug] <<< testapi::assert_screen(mustmatch="root-console", timeout=30, no_wait=1)
[2020-05-16T11:57:50.025 CEST] [debug] >>> testapi::_handle_found_needle: found root-console-top-20200304, similarity 1.00 @ 96/2
[2020-05-16T11:57:50.025 CEST] [debug] tests/console/zypper_ref.pm:26 called utils::zypper_enable_install_dvd -> lib/utils.pm:554 called utils::zypper_call -> lib/utils.pm:509 called testapi::script_run
</code></pre>
<p>Failed tests:</p>
<pre><code>�[0m�[1;34m[2020-05-21T05:14:21.047 CEST] [debug] ||| starting zypper_ref tests/console/zypper_ref.pm
�[0m[2020-05-21T05:14:21.047 CEST] [debug] tests/console/zypper_ref.pm:26 called opensusebasetest::select_serial_terminal -> lib/opensusebasetest.pm:1115 called testapi::select_console
[2020-05-21T05:14:21.047 CEST] [debug] <<< testapi::select_console(testapi_console="root-virtio-terminal")
[2020-05-21T05:14:21.048 CEST] [debug] <<< consoles::virtio_terminal::open_pipe(pipe_prefix="/var/lib/openqa/pool/8/virtio_console")
�[33m[2020-05-21T05:14:21.049 CEST] [info] ::: consoles::virtio_terminal::open_pipe: Set PIPE_SZ from 1048576 to 1048576
�[0m�[33m[2020-05-21T05:14:21.049 CEST] [info] ::: consoles::virtio_terminal::open_pipe: Set PIPE_SZ from 1048576 to 1048576
�[0m�[37m[2020-05-21T05:14:21.049 CEST] [debug] activate_console, console: root-virtio-terminal, type: virtio-terminal
�[0m[2020-05-21T05:14:21.050 CEST] [debug] tests/console/zypper_ref.pm:26 called opensusebasetest::select_serial_terminal -> lib/opensusebasetest.pm:1115 called testapi::select_console -> lib/susedistribution.pm:746 called serial_terminal::login -> lib/serial_terminal.pm:82 called bmwqemu::log_call
[2020-05-21T05:14:21.050 CEST] [debug] <<< serial_terminal::login()
[2020-05-21T05:14:21.050 CEST] [debug] tests/console/zypper_ref.pm:26 called opensusebasetest::select_serial_terminal -> lib/opensusebasetest.pm:1115 called testapi::select_console -> lib/susedistribution.pm:746 called serial_terminal::login -> lib/serial_terminal.pm:87 called testapi::wait_serial
[2020-05-21T05:14:21.050 CEST] [debug] <<< testapi::wait_serial(timeout=5, record_output=undef, expect_not_found=0, quiet=1, buffer_size=undef, regexp=qr/login:\s*$/ui, no_regex=0)
[2020-05-21T05:14:21.050 CEST] [debug] <<< consoles::serial_screen::read_until(quiet=1, expect_not_found=0, buffer_size=undef, pattern="(?^ui:login:\\s*\$)", timeout=5, json_cmd_token="sEJFMwpt", cmd="backend_wait_serial", no_regex=0, regexp="(?^ui:login:\\s*\$)", record_output=undef)
�[32m[2020-05-21T05:14:26.056 CEST] [debug] >>> testapi::wait_serial: (?^ui:login:\s*$): fail
�[0m[2020-05-21T05:14:26.056 CEST] [debug] tests/console/zypper_ref.pm:26 called opensusebasetest::select_serial_terminal -> lib/opensusebasetest.pm:1115 called testapi::select_console -> lib/susedistribution.pm:746 called serial_terminal::login -> lib/serial_terminal.pm:90 called testapi::type_string
[2020-05-21T05:14:26.056 CEST] [debug] <<< testapi::type_string(text="\n")
[2020-05-21T05:14:26.057 CEST] [debug] <<< consoles::serial_screen::type_string(cmd="backend_type_string", text="\n", json_cmd_token="CJjINXgN")
[2020-05-21T05:14:26.057 CEST] [debug] tests/console/zypper_ref.pm:26 called opensusebasetest::select_serial_terminal -> lib/opensusebasetest.pm:1115 called testapi::select_console -> lib/susedistribution.pm:746 called serial_terminal::login -> lib/serial_terminal.pm:91 called testapi::wait_serial
[2020-05-21T05:14:26.057 CEST] [debug] <<< testapi::wait_serial(regexp=qr/login:\s*$/ui, buffer_size=undef, no_regex=0, quiet=undef, expect_not_found=0, record_output=undef, timeout=90)
[2020-05-21T05:14:26.058 CEST] [debug] <<< consoles::serial_screen::read_until(pattern="(?^ui:login:\\s*\$)", timeout=90, json_cmd_token="zVPhpmAp", quiet=undef, expect_not_found=0, buffer_size=undef, record_output=undef, regexp="(?^ui:login:\\s*\$)", cmd="backend_wait_serial", no_regex=0)
�[32m[2020-05-21T05:15:56.106 CEST] [debug] >>> testapi::wait_serial: (?^ui:login:\s*$): fail
�[0m�[33m[2020-05-21T05:15:56.106 CEST] [info] ::: basetest::runtest: # Test died: Failed to wait for login prompt at /var/lib/openqa/cache/openqa.suse.de/tests/sle/lib/serial_terminal.pm line 91.
</code></pre>
<p>Further investigation is needed and possibly follow up ticket with tools' team.</p>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/4261497" class="external">197.1</a></p>
<p>Last good: <a href="https://openqa.suse.de/tests/4247142" class="external">195.1</a> (or more recent)</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>
qe-yam - action #67078 (Rejected): [functional][y] Implement workaround for shutdown failure on H...https://progress.opensuse.org/issues/670782020-05-20T10:01:38Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Shutdown module fails on Hyper-V for test suites with DESKTOP=gnome, in scenarios where previous module leaves system in tty2 or tty6, due to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1171290" class="external">bug#1171290</a>. OpenQA failure could be replaced with soft failure until the bug is fixed. An easy way would be to create a needle for the <a href="https://openqa.suse.de/tests/4203853#step/shutdown/11" class="external">stall screen</a> and when matched, any window (e.g. terminal) would maximize and minimize. The movement of the window should resolve the stall screen and the shutdown module should then be able to be completed successfully.</p>
<p>Parent ticket: </p>
<ul>
<li><a href="https://progress.opensuse.org/issues/64466" class="external">https://progress.opensuse.org/issues/64466</a></li>
</ul>
<p>Acceptance criteria:</p>
<ul>
<li>Shutdown module finishes with soft failure.</li>
</ul>
openQA Tests - action #64688 (Resolved): [functional][y] Travis check detect_unused_modules is ta...https://progress.opensuse.org/issues/646882020-03-20T14:54:54Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The original ticket: <a href="https://progress.opensuse.org/issues/47894" class="external">https://progress.opensuse.org/issues/47894</a><br>
is mentioning a constant check for unused modules. What the implemented check is doing, is verifying on every push build, that all modules in repository are used somewhere. This looks like an overkill as it takes about 4 minutes to be completed. We could investigate if this can be replaced by a more targeted check on the particular push and additionally a complete check running daily (like a cron job) that will parse the whole repository.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Unused modules detection is performed on the scope of the changes in the PR only</li>
</ol>
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 #64325 (Resolved): [functional][y] Add check in autoyast installation test ...https://progress.opensuse.org/issues/643252020-03-09T13:04:41Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>When users manually provide the path for the autoyast profile, there can be typos. After the system displays an error that the profile cannot be found, changing the path to the correct one, should work. </p>
<p>(Recently, I tried the above action manually and faced some unexpected warning messages. See <a href="https://bugzilla.suse.com/show_bug.cgi?id=1165464" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1165464</a> )</p>
<p>Challenge with implementing the above check in openQA is that if the given autoyast profile path is not correct, openQA will not proceed to run the test.</p>
<p>use LWP::Simple 'head' can be used</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Accessibility of the autoyast profile is validated before test is executed</li>
</ol>
openQA Tests - action #64204 (Resolved): [functional][y] test fails in yast2_lan_restarthttps://progress.opensuse.org/issues/642042020-03-04T15:46:31Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>It seems that x11/yast2_lan_restart.pm line 95, is expecting the network to be restarted after harware device name change, but there is no recorded restart of network in journal.log (according to lib/y2lan_restart_common.pm line 153, see <a href="https://progress.opensuse.org/issues/62465" class="external">https://progress.opensuse.org/issues/62465</a>). This leads to test failure.</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/3953889#step/yast2_lan_restart/213" class="external">150.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/3931089" class="external">146.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-SP2" class="external">latest</a></p>
openQA Tests - action #63922 (Rejected): [functional][y] Sporadic failure of mediacheck module in...https://progress.opensuse.org/issues/639222020-02-27T15:14:42Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After build 131.1, it is observed that while module "mediacheck" runs on hyperV, "Check installation media" is selected, but instead of actually checking the media, test goes back to grub menu and selects "installation". Test fails when warning for Beta distribution appears, after timing out. </p>
<p><a href="https://openqa.suse.de/tests/3928000#step/mediacheck/11" class="external">https://openqa.suse.de/tests/3928000#step/mediacheck/11</a></p>
<p>The issue happens sporadically.</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/3915652" class="external">143.1</a> (or more recent)</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>