openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-02-01T09:54:50ZopenSUSE Project Management Tool
Redmine qe-yam - action #154717 (Rejected): Adjust select_module_desktop to verify the existence of the m...https://progress.opensuse.org/issues/1547172024-02-01T09:54:50Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p>The skip_registration test <a href="https://openqa.suse.de/tests/13400788#step/select_module_desktop/1" class="external">fails for 15SP3</a> because, according to the yui logs, the addon_repos widget seems to have appeared and the module proceeds to select item with value=Desktop+Applications+Module , but in reality the item is not loaded yet and this is causing the Yast error that we mistakenly regarded as a bug result ( see <a href="https://bugzilla.suse.com/show_bug.cgi?id=1219403" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1219403</a> ). </p>
<p>yui logs:<br>
[2024-01-31T23:41:26.647742+01:00] [info] [pid:29717] skip_registration test module finished<br>
[2024-01-31T23:41:26.649364+01:00] [info] [pid:29717] select_module_desktop test module started<br>
[2024-01-31T23:41:26.649764+01:00] [debug] [pid:29717] Finding widget by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:27.652241+01:00] [error] [pid:29717] Widget not found by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:29.656276+01:00] [debug] [pid:29717] Finding widget by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:30.660504+01:00] [debug] [pid:29717] Sending action to widget by url: <a href="http://localhost:39103/v1/widgets?action=check&id=addon_repos&value=Desktop+Applications+Module" class="external">http://localhost:39103/v1/widgets?action=check&id=addon_repos&value=Desktop+Applications+Module</a><br>
[2024-01-31T23:41:31.664662+01:00] [debug] [pid:29717] Finding widget by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:32.667784+01:00] [error] [pid:29717] Widget not found by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:34.672477+01:00] [error] [pid:29717] Widget not found by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:36.675976+01:00] [error] [pid:29717] Widget not found by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:38.678876+01:00] [error] [pid:29717] Widget not found by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:40.681975+01:00] [error] [pid:29717] Widget not found by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a><br>
[2024-01-31T23:41:42.685466+01:00] [error] [pid:29717] Widget not found by url: <a href="http://localhost:39103/v1/widgets?id=addon_repos" class="external">http://localhost:39103/v1/widgets?id=addon_repos</a></p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<ul>
<li>Adjust the test module, in order to avoid similar failures in the future.</li>
</ul>
<a name="Additional-information"></a>
<h4 >Additional information<a href="#Additional-information" class="wiki-anchor">¶</a></h4>
<p>The module is used in many test suites for 15-SP{3..6}.<br>
The test suite is now moved to development job group: <a href="https://openqa.suse.de/group_overview/446" class="external">https://openqa.suse.de/group_overview/446</a></p>
qe-yam - action #152685 (New): Add typescript syntax check in Playwright repo CI/CDhttps://progress.opensuse.org/issues/1526852023-12-15T13:21:17Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In <a href="https://github.com/jknphy/e2e-agama-playwright" class="external">Playwright repo</a> we have currently set the basis for CI/CD <a href="https://progress.opensuse.org/issues/134441" class="external">poo#134441</a> after merging: <a href="https://github.com/jknphy/e2e-agama-playwright/pull/30" class="external">https://github.com/jknphy/e2e-agama-playwright/pull/30</a><br>
Currently, the only check available is the typescript formatting, according to file tsfmt.json (complying with the default formatting by vscode). We should enhance the checks by verifying the typescript syntax. In case there is a toll that can verify both syntax and formatting, the typescript-formatter can be completely removed from the workflow.</p>
<p><strong><em>Acceptance Criteria</em></strong></p>
<ul>
<li>The CI in Playwright repo should check the typescript syntax for errors.</li>
<li>Create test actions to verify expected failure and success of the CI.</li>
</ul>
qe-yam - action #152683 (New): Add check for existence of imported files in Playwright repo CI/CDhttps://progress.opensuse.org/issues/1526832023-12-15T13:16:36Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In <a href="https://github.com/jknphy/e2e-agama-playwright" class="external">Playwright repo</a> we have currently set the basis for CI/CD <a href="https://progress.opensuse.org/issues/134441" class="external">poo#134441</a> after merging: <a href="https://github.com/jknphy/e2e-agama-playwright/pull/30" class="external">https://github.com/jknphy/e2e-agama-playwright/pull/30</a><br>
Currently, the only check available is the typescript formatting, according to file tsfmt.json (complying with the default formatting by vscode). We should enhance the checks in the CI, by adding a step that will get the imported files (lib/actor/page etc) ignoring the "import { type Page } from '@playwright/test';" . It is recommended to create a script directory and place a script inside that will be called by the CI steps in .github/workflows/ci.yaml, instead of polluting the ci.yaml.</p>
<p><strong><em>Acceptance criteria</em></strong></p>
<ul>
<li>The CI should check if the imported files exist in the repo.</li>
<li>Create test actions to verify expected failure and success of the CI.</li>
</ul>
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>
qe-yam - action #130360 (Rejected): addon_products_via_SCC_yast2 in SLE12SP4/5 attempts to re-reg...https://progress.opensuse.org/issues/1303602023-06-05T07:38:46Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In Yast Maintenance Dev job group The module addon_products_via_SCC_yast2 tries to register an already registered system. We should check first the registration status and proceed if needed. </p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP5-Server-DVD-Updates-x86_64-mru-iscsi_server_normal_auth_backstore_hdd_dev@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11253708/modules/addon_products_via_SCC_yast2/steps/17" class="external">addon_products_via_SCC_yast2</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>. iSCSI multimachine test suite with manually configure the static network between SUTs. Authentication: 2way normal authentication, discovery authentication is not configured Backstore: plain drive Test data are included in enclosed yaml file. </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/10991058" class="external">20230426-1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (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=Server-DVD-Updates&machine=64bit&test=mru-iscsi_server_normal_auth_backstore_hdd_dev&version=12-SP5" class="external">latest</a></p>
qe-yam - action #128606 (Rejected): [sporadic] test fails in install_servicehttps://progress.opensuse.org/issues/1286062023-05-03T13:35:08Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After install_service module is attempting to install,enable and start vsftpd, it runs the /etc/bash/bash.local and we expect it to return no error ( $? = 0 ). Even though the script doesn't seem to fail, openqa is reporting <a href="https://openqa.suse.de/tests/11022849#step/install_service/197" class="external">failure</a> . Find the root cause and provide solution , in case there are false failures reported by openqa.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP5-Regression-on-Migration-from-SLE12-SPx-ppc64le-offline_sles12sp5_pscc_sdk-lp-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g fails in<br>
<a href="https://openqa.suse.de/tests/10918493/modules/install_service/steps/199" class="external">install_service</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.suse.de/tests/10905871" class="external">90.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/10849460" class="external">88.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=Regression-on-Migration-from-SLE12-SPx&machine=ppc64le-2g&test=offline_sles12sp5_pscc_sdk-lp-asmm-contm-lgm-tcm-wsm-pcm_all_full&version=15-SP5" class="external">latest</a></p>
qe-yam - action #128564 (Rejected): [sporadic] investigate failure for validate_first_disk_select...https://progress.opensuse.org/issues/1285642023-05-03T07:22:13Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>select_disk test runs on x86_64, aarch64 and ppc64le. For ppc, we see very often a failure of the test validation, to make the installation on the sda disk. We should investigate if our expectations make sense, contact the developers (possibly ask in linux mail list, in case yast developers are not certain). In case the disk selection cannot be guaranteed, we should disable the test for ppc. Otherwise open a bug report.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP5-Online-ppc64le-select_disk@ppc64le-hmc-4disk fails in<br>
<a href="https://openqa.suse.de/tests/9518220/modules/validate_first_disk_selection/steps/6" class="external">validate_first_disk_selection</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Test the selection of "first" disk with the guided setup in partitioning. This is also used as a prerequisite for real hardware tests to select the right disk for installation and not a "random" one.</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/9518220" class="external">21.1</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (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-4disk&test=select_disk&version=15-SP5" class="external">latest</a></p>
qe-yam - action #128558 (Rejected): [sporadic] test fails in shutdownhttps://progress.opensuse.org/issues/1285582023-05-03T06:59:40Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After typing the password, there is a blank screen that should be matching the needle here:<br>
<a href="https://openqa.suse.de/tests/10931763#step/shutdown/20" class="external">https://openqa.suse.de/tests/10931763#step/shutdown/20</a><br>
but it is failing. We should investigate if the shutdown module has been modified (also the libraries that it calls upon) or some needles been removed.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP5-Online-x86_64-create_hdd_gnome_libyui@svirt-xen-hvm fails in<br>
<a href="https://openqa.suse.de/tests/10388381/modules/shutdown/steps/21" class="external">shutdown</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Boot into gnome HDD, configure and republish image for tests that use libyui.</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/10187469" class="external">61.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/10942394" class="external">93.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=x86_64&distri=sle&flavor=Online&machine=svirt-xen-hvm&test=create_hdd_gnome_libyui&version=15-SP5" class="external">latest</a></p>
qe-yam - action #99261 (Rejected): [sporadic] s390x tests fail in first_boot and boot_to_desktop https://progress.opensuse.org/issues/992612021-09-24T16:47:24Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>This failure has occurred both for first_boot and boot_to_desktop on s390x. What happens is that handle_login function in lib/x11utils.pm is checking if the desktop matches with <a href="https://openqa.suse.de/tests/7218545#step/first_boot/9" class="external">gnome-activities</a> and then presses esc.</p>
<pre><code>249 if (match_has_tag('gnome-activities')) {
250 send_key('esc');
251 assert_screen([qw(generic-desktop opensuse-welcome)]);
252 }
</code></pre>
<p>After that it expects that the desktop will match with normal generic desktop, but we see no change. According to the autoinst.log the esc key is sent indeed. We need to check why the key takes no effect on the desktop. An idea would be to add a second check, for example: send_key('esc') if assert_screen "gnome-activities"; so that in case 'esc' is not accepted the first time, it would take effect, the second time.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-s390x-zfcp@s390x-zfcp fails in<br>
<a href="https://openqa.suse.de/tests/7218545/modules/first_boot/steps/11" class="external">first_boot</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>. Maintainer: QE Yast, mgriessmeier</p>
<p>Installation-only test configuring an s390x ZFCP storage.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/6950169" class="external">29.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (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-zfcp&test=zfcp&version=15-SP4" 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 #91425 (Rejected): [sporadic] aarch64 tests incomplete "associated worker re-conn...https://progress.opensuse.org/issues/914252021-04-20T12:35:04Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>We are seeing a lot of similar failures for aarch64.<br>
This ticket is created in order to collect statistics for the particular issue and for labeling the failures on production.</p>
qe-yam - action #90350 (Rejected): Add yast2_system_settings for ncurseshttps://progress.opensuse.org/issues/903502021-03-19T11:08:21Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Module yast2_system_settings is designed to run on gui, using libyui. The coverage can be extended for ncurses too. We can write a second module. The basic libyui code will be the same, but the x11 handling won't be needed. </p>
qe-yam - action #73093 (Rejected): [y] test fails in installationhttps://progress.opensuse.org/issues/730932020-10-07T14:29:35Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>There have been some failures in installation module for different test suites. Even though the yast installer is still running, the needle match doesn't recognize it. </p>
<p>example:<br>
openQA test in scenario sle-15-SP3-Online-x86_64-autoyast_home_encrypted@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4787697/modules/installation/steps/47" class="external">installation</a></p>
<p>Could be that the timeout in tests/installation/await_install.pm:74 might need to be increased, but as this is a sporadic failure it would need some verification runs.</p>
<p>Notice: The installation progress before and after failure is different, so this doesn't seem like an actual stall.</p>
qe-yam - action #67669 (Rejected): [y] Enable yast2_lan_restart_bond module for s390xhttps://progress.opensuse.org/issues/676692020-06-03T11:48:56Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Module yast2_lan_restart_bond is part of yast2_gui test suite.<br>
For s390x, it fails due to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1172444" class="external">bug#1172444</a>.</p>
<p>Check of the bug is fixed and modify the test suite schedule, accordingly. </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>