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 #152296 (Rejected): Optimize gitlab repo CIhttps://progress.opensuse.org/issues/1522962023-12-08T12:16:45Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently, our <a href="https://gitlab.suse.de/qe-yam/openqa-job-groups" class="external">gitlab repo</a> for openqa job groups is running on a simple checks CI. There is a yamllint check, a check for schedule and data files existence and then the openqa-cli command that checks if it can post the job group . We should make some tests to see if the above checks provide failure and pass when expected.</p>
<p>Note: A specific scenario to look into is if we want to move a test suite to another Job group, within the repo , one MR with two commits, will it pass or will it provide error that the test suite already exists in another Job group?</p>
<p><strong>Acceptance criteria</strong></p>
<ul>
<li>Run tests for different scenarios to verify the CI functionality</li>
<li>Open follow-up tickets for any improvements if needed.</li>
</ul>
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 #102074 (Rejected): Create test scenario for displaying a custom proposal set dur...https://progress.opensuse.org/issues/1020742021-11-08T12:56:19Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Motivation here: <a href="https://github.com/yast/yast-installation/pull/980" class="external">https://github.com/yast/yast-installation/pull/980</a><br>
and<br>
<a href="https://trello.com/c/Bnc4V82U/2666-3-sle-15-sp3-l3-1190294-proposals-selection-does-not-work-in-autoyast" class="external">https://trello.com/c/Bnc4V82U/2666-3-sle-15-sp3-l3-1190294-proposals-selection-does-not-work-in-autoyast</a></p>
<p>Currently we do not have any automated autoyast test that uses custom proposal and checks overview tabs.</p>
<p>Acceptance criteria:</p>
<ol>
<li>Research how the feature works.</li>
<li>Evaluate if it is practical to create a new test suite or implement the feature testing in an existing ay test suite.</li>
<li>Create a ticket with comprehensible steps for automation testing.</li>
</ol>
qe-yam - action #101370 (Rejected): test fails in yast2_firewall due to recent modification the i...https://progress.opensuse.org/issues/1013702021-10-22T10:34:39Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>According to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1191608" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1191608</a> , eth0 will be set to public by default from now on.<br>
Scope of this ticket is to add the public option, create new needle and check if this change doesn't break any previous version tests.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-x86_64-yast2_gui@64bit fails in<br>
<a href="https://openqa.suse.de/tests/7487123/modules/yast2_firewall/steps/47" class="external">yast2_firewall</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: zluo, riafarov</p>
<p>Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.</p>
<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/7087278" class="external">31.2</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=Online&machine=64bit&test=yast2_gui&version=15-SP4" class="external">latest</a></p>
qe-yam - action #97328 (Rejected): test fails in yast2_lan_restart_*https://progress.opensuse.org/issues/973282021-08-22T15:05:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After renaming a device, the network should be reloaded: <a href="https://progress.opensuse.org/issues/64761" class="external">https://progress.opensuse.org/issues/64761</a>. After opening settings and closing without making any changes, there should not be restart or reload. The modules seem to either have wrong expectations or perform the wrong actions. We see these failures for all archs that the modules run.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-ppc64le-yast2_gui@ppc64le-2g fails in<br>
<a href="https://openqa.suse.de/tests/6914088/modules/yast2_lan_restart_bridge/steps/56" class="external">yast2_lan_restart_bridge</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: zluo, riafarov</p>
<p>Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.</p>
<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/6907845" class="external">26.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=ppc64le&distri=sle&flavor=Online&machine=ppc64le-2g&test=yast2_gui&version=15-SP4" class="external">latest</a></p>
qe-yam - action #92245 (Rejected): Create textmode qcow with libyui pre-installedhttps://progress.opensuse.org/issues/922452021-05-06T13:39:52Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>For motivation see ticket: <a href="https://progress.opensuse.org/issues/90368" class="external">https://progress.opensuse.org/issues/90368</a></p>
<p>For gnome, we are booting into the qcow created by create_hdd_gnome, we clean and reregister the system, install libyui packages, open firewall ports and republish the image that then can be used by libyui tests (see PR: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12468" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12468</a>). We want the same to happen for textmode. A small catch that the system complains if we try to add development module without desktop module.</p>
<p>Currently the only test that is booting into textmode image and is using libyui is yast2_firstboot_textmode.</p>
qe-yam - coordination #92242 (Rejected): Create the conditions for libyui tests on textmode runni...https://progress.opensuse.org/issues/922422021-05-06T13:35:39Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently, we use libyui for running system on textmode image only for firstboot_textmode.<br>
We should create libyui image with installed libyui packages and open firewall ports (similar to gnome : <a href="https://progress.opensuse.org/issues/90368" class="external">https://progress.opensuse.org/issues/90368</a> ) and use it for yast2_firstboot_textmode and potentially for yast2_ncurses_textmode, if there are libyui modules that can be enabled.</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>
openQA Infrastructure - action #90692 (Rejected): [sporadic] script_output getting wrong output o...https://progress.opensuse.org/issues/906922021-04-06T07:50:59Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Only for aarch64, the following command:<br>
script_output("cat /proc/sys/kernel/sysrq");<br>
should return the content of the sysrq file, but 10% of the times it returns the character [, which seemt to be taken mistakenly by the serial console.<br>
Failure:<br>
<a href="https://openqa.suse.de/tests/5754960#step/yast2_system_settings/51" class="external">https://openqa.suse.de/tests/5754960#step/yast2_system_settings/51</a></p>
qe-yam - action #89494 (Rejected): Validate editing partition for mount_by optionshttps://progress.opensuse.org/issues/894942021-03-04T12:45:10Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In ticket : <a href="https://progress.opensuse.org/issues/88533" class="external">https://progress.opensuse.org/issues/88533</a> a new test scenario "fstab_mount_by" was implemented , for mount_by option validation after installation. The scenario covers editing the fstab options for new partitions added in the partitioning. </p>
<p>The objective of this follow-up ticket is to extend coverage and perform installation on the image created by "fstab_mount_by" scenario and, while partitioning, edit the existing partitions, check if the existing mount_by option for each partition is recognized correctly by the expert partitioner and validate after installation if the new options take effect correctly.</p>
qe-yam - action #80474 (Rejected): Implement check for emergency shell in case bootloader is stuckhttps://progress.opensuse.org/issues/804742020-11-26T16:49:08Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In the scenario where the bootloader screen is stuck, the worker will detect stall and enter post_fail_hook. During post_fail_hook, it has occurred that select_console('root') induced the emergency shell. In this case, there is no check that will redirect any logs to the serial console, like <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/utils.pm#L1042-L1066" class="external">handle_emergency</a> function.</p>
<p>We cannot add the check in <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/susedistribution.pm#L683" class="external">activate_console</a> , as the function is called repeatedly in many tests. </p>
<p>A solution would be to find out which step of the activate_console function is triggering the emergency shell and see if we can implement a check for stuck bootloader screen in <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/opensusebasetest.pm#L971" class="external">wait_boot_past_bootloader</a> or post_fail_hook, try to trigger emergency shell and if successful, collect logs.</p>
<p>Failure example:<br>
<a href="https://openqa.suse.de/tests/4922078" class="external">https://openqa.suse.de/tests/4922078</a></p>
<p>It may not be easy to reproduce the scenario, as it is sporadic for SUTs with RAID0 root partition, during firstboot. <br>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1178515" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1178515</a></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>
openQA Tests - action #71638 (Rejected): [y] test fails in validate_fs_tablehttps://progress.opensuse.org/issues/716382020-09-22T10:50:02Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>During msdos partitioning, the SWAP partition is selected to be created with UDF instead of swap filesystem. Even though, the screen matches at swap, there is an extra key sent and the result is that SWAP partition is missing and the filesystme validation fails:</p>
<p>[2020-09-22T04:58:41.696 CEST] [debug] <<< testapi::check_screen(mustmatch="partitioning_swap-format-selected", timeout=5)<br>
�[37m[2020-09-22T04:58:42.046 CEST] [debug] load of /var/lib/openqa/cache/openqa.suse.de/tests/sle/products/sle/needles/partitioning_swap-format-selected-20200217.png took 0.35 seconds<br>
�[0m�[32m[2020-09-22T04:58:44.670 CEST] [debug] >>> testapi::_handle_found_needle: found partitioning_swap-format-selected-20200121, similarity 1.00 @ 368/351<br>
�[0m[2020-09-22T04:58:44.670 CEST] [debug] tests/installation/partitioning/msdos_partition_table.pm:27 called Installation::Partitioner::LibstorageNG::v4::ExpertPartitionerController::add_partition_msdos -> lib/Installation/Partitioner/LibstorageNG/v4/ExpertPartitionerController.pm:168 called Installation::Partitioner::LibstorageNG::v4::ExpertPartitionerController::add_new_partition -> lib/Installation/Partitioner/LibstorageNG/v4/ExpertPartitionerController.pm:180 called Installation::Partitioner::AbstractExpertPartitionerController::_set_partition_options -> lib/Installation/Partitioner/AbstractExpertPartitionerController.pm:114 called Installation::Partitioner::FormattingOptionsPage::select_mount_device_radiobutton -> lib/Installation/Partitioner/FormattingOptionsPage.pm:96 called testapi::assert_screen<br>
[2020-09-22T04:58:44.670 CEST] [debug] <<< testapi::assert_screen(mustmatch="partition-format", timeout=30)<br>
�[32m[2020-09-22T04:58:44.791 CEST] [debug] >>> testapi::_handle_found_needle: found partitioning-format-20160504, similarity 1.00 @ 275/273<br>
�[0m[2020-09-22T04:58:44.792 CEST] [debug] tests/installation/partitioning/msdos_partition_table.pm:27 called Installation::Partitioner::LibstorageNG::v4::ExpertPartitionerController::add_partition_msdos -> lib/Installation/Partitioner/LibstorageNG/v4/ExpertPartitionerController.pm:168 called Installation::Partitioner::LibstorageNG::v4::ExpertPartitionerController::add_new_partition -> lib/Installation/Partitioner/LibstorageNG/v4/ExpertPartitionerController.pm:180 called Installation::Partitioner::AbstractExpertPartitionerController::_set_partition_options -> lib/Installation/Partitioner/AbstractExpertPartitionerController.pm:114 called Installation::Partitioner::FormattingOptionsPage::select_mount_device_radiobutton -> lib/Installation/Partitioner/FormattingOptionsPage.pm:97 called testapi::send_key<br>
[2020-09-22T04:58:44.792 CEST] [debug] <<< testapi::send_key(key="alt-o", do_wait=0, wait_screen_change=0)</p>
<p><a href="https://openqa.suse.de/tests/4711745#step/msdos_partition_table/86">https://openqa.suse.de/tests/4711745#step/msdos_partition_table/86</a></p>
<p><a href="https://openqa.suse.de/tests/4711745/modules/validate_fs_table/steps/35">https://openqa.suse.de/tests/4711745/modules/validate_fs_table/steps/35</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Installation with MSDOS partition table.</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/4686599" class="external">33.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/4636012" class="external">23.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&test=msdos&version=15-SP3" 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>