openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-10-01T15:10:12ZopenSUSE Project Management Tool
Redmine openQA Tests - action #72184 (New): [virtualization][y] Select_console fails sporadically for svi...https://progress.opensuse.org/issues/721842020-10-01T15:10:12Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>There is a sporadic failure of approximately 17%, for prepare_data module for yast2_gui test suite. The SUT seems to be freezing with black screen, when select_console is called.</p>
<p>It is notable that by simplifying the module to:</p>
<pre><code>sub run {
select_console 'root-console';
}
1;
</code></pre>
<p>it still displays the same percentage of failure.</p>
<p>The issue is not present in case of using xterm and chvt 6.</p>
<pre><code>sub run {
x11_start_program('xterm');
wait_still_screen(5);
become_root;
assert_script_run "chvt 6";
assert_screen "tty6-selected";
}
1;
</code></pre>
<p>Unfortunately, the logs are not helpful. When successfully switching to tty6, the autoinst logs contain:<br>
[2020-09-30T17:28:05.896 CEST] [debug] <<< testapi::select_console(testapi_console="root-console")<br>
....<br>
[ 82.601276] <strong>systemd[1]: Started Getty on tty6.</strong></p>
<p>Looking at the logs from failed runs, the above phrase is missing.</p>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-yast2_gui@svirt-xen-hvm fails in<br>
<a href="https://openqa.suse.de/tests/4718229/modules/prepare_test_data/steps/3" class="external">prepare_test_data</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.suse.de/tests/4752856" class="external">48.1</a></p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=svirt-xen-hvm&test=yast2_gui&version=15-SP3" class="external">latest</a></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>
qe-yam - action #71122 (Resolved): [y][timeboxed:12h] Organize and open tickets for yast-matepack...https://progress.opensuse.org/issues/711222020-09-08T16:46:08Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The following parts of yast-metapackage-handler package code, are considered to be the basis for the unit test:</p>
<p><a href="#" onclick="$('#collapse-dfc13c7d-show, #collapse-dfc13c7d-hide').toggle(); $('#collapse-dfc13c7d').fadeToggle(150);; return false;" id="collapse-dfc13c7d-show" class="icon icon-collapsed collapsible">src/modules/OneClickInstall.rb</a><a href="#" onclick="$('#collapse-dfc13c7d-show, #collapse-dfc13c7d-hide').toggle(); $('#collapse-dfc13c7d').fadeToggle(150);; return false;" id="collapse-dfc13c7d-hide" class="icon icon-expanded collapsible" style="display:none;">src/modules/OneClickInstall.rb</a><div id="collapse-dfc13c7d" class="collapsed-text" style="display:none;"><p>Load<br>
xpath_element<br>
xpath_text<br>
GetRequiredRepositories<br>
GetNonRequiredRepositories<br>
SetNonRequiredRepository<br>
SetRequiredRepositories<br>
GetRepositoryName<br>
GetRepositorySummary<br>
GetRepositoryDescription<br>
GetRequiredSoftware<br>
GetRequiredPackages<br>
GetRequiredPatterns<br>
GetRequiredRemoveSoftware<br>
SetRequiredSoftware<br>
GetNonRequiredSoftware<br>
GetNonRequiredRemoveSoftware<br>
SetNonRequiredSoftware<br>
SetRequiredSoftwares<br>
GetSoftwareSummary<br>
GetSoftwareDescription<br>
HaveRepositories<br>
HaveSoftware<br>
HavePackagesToInstall<br>
HavePatternsToInstall<br>
HaveRepositoriesToInstall<br>
HaveRemovalsToInstall<br>
HaveRemovals<br>
HaveAnythingToDo<br>
HaveAnyRecommended<br>
makeXMLFriendly<br>
fromXMLFriendly<br>
SetupXML<br>
ToXML<br>
FromXML</p>
</div></p>
<p><a href="#" onclick="$('#collapse-e3927105-show, #collapse-e3927105-hide').toggle(); $('#collapse-e3927105').fadeToggle(150);; return false;" id="collapse-e3927105-show" class="icon icon-collapsed collapsible">src/modules/OneClickInstallWorkerFunctions.rb</a><a href="#" onclick="$('#collapse-e3927105-show, #collapse-e3927105-hide').toggle(); $('#collapse-e3927105').fadeToggle(150);; return false;" id="collapse-e3927105-hide" class="icon icon-expanded collapsible" style="display:none;">src/modules/OneClickInstallWorkerFunctions.rb</a><div id="collapse-e3927105" class="collapsed-text" style="display:none;"><p>FuzzyMatch<br>
DeDupe<br>
AddRepositories<br>
InitSlideShow<br>
InstallPackages<br>
InstallPatterns<br>
RemovePackages<br>
RemoveAddedRepositories</p>
</div></p>
<p>There is already small part of the unit test, waiting to be reviewed in PR: <a href="https://github.com/yast/yast-metapackage-handler/pull/22" class="external">https://github.com/yast/yast-metapackage-handler/pull/22</a><br>
The objective is to create various smaller tickets for completing the unit test of the above functions. The second file contains more complicated functions.<br>
Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
<p>As an outcome we should get the list of methods to cover in each of the mentioned classes.</p>
qe-yam - action #71116 (Closed): [y] Add OpenQA test for OneClickInstallhttps://progress.opensuse.org/issues/711162020-09-08T16:03:45Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Packages can be installed via .YMP files that contain the necessary information in XML form, using OneclickInstall.<br>
As root run<br>
#OneClickInstallCLI <br>
and verify that the package is installed successfully. Accordingly, test the OneClickInstall UI<br>
#OneClickInstallUI </p>
<p>YMP URL example: <a href="https://software.opensuse.org/ymp/openSUSE:Factory/standard/vim.ymp?base=openSUSE%3AFactory&query=vim" class="external">https://software.opensuse.org/ymp/openSUSE:Factory/standard/vim.ymp?base=openSUSE%3AFactory&query=vim</a></p>
<p>The test can run on both SLE and Tumbleweed, but with different YMP URLs, but only 64-bit for a start.</p>
openQA Tests - action #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>
qe-yam - action #69634 (Resolved): [y][timeboxed:24h] Add unit test for yast-metapackage-handlerhttps://progress.opensuse.org/issues/696342020-08-06T08:52:54Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently, yast-metapackage-handler has no unit test at all. The goal is to test basic functions of the package for 1-click-install.</p>
<p>YaST team has advised to create a pull request as soon as the first working part of the unit test is ready.</p>
<p>As a first step we should figure out how to inject the unit tests and how to write them.<br>
In the scope of the ticket we should learn how to write those and execute.</p>
<p>And after that create follow-up tickets for exact classes/modules we want to cover with unit tests.</p>
openQA Project - action #69313 (Resolved): When using refspec for ppc for a particular job, PRODU...https://progress.opensuse.org/issues/693132020-07-24T10:25:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>While attempting to run refspecs for test "autoyast_reinstall" job on various architectures, I faced an issue specifically on ppc64le. The PRODUCTDIR needs to be set manually like following: <br>
<code>openqa-clone-custom-git-refspec https://github.com/sofiasyria/os-autoinst-distri-opensuse/tree/ac68803 https://openqa.suse.de/tests/4427385 ASSET_1="04427383-autoinst.xml" YAML_TEST_DATA=test_data/yast/autoyast_reinstall/autoyast_reinstall_ppc64le-hmc.yaml PRODUCTDIR="os-autoinst-distri-opensuse/products/sle"</code></p>
<p>If the above command is used without the PRODUCTDIR specification, the variable gets the value "os-autoinst-distri-opensuseos-autoinst-distri-opensuse/products/sle" which leads to test failure as here:<br>
<a href="https://openqa.suse.de/tests/4482090" class="external">https://openqa.suse.de/tests/4482090</a></p>
<p>The particular test suite runs for ppc64le-2g, ppc64le-hmc-single-disk, 64bit, s390x and aarch64. For both the ppc machines, the PRODUCTDIR needs to be set manually. For rest of them, it's not necessary.</p>
<p>I have unsuccessfully tried to reproduce the issue with other jobs on ppc.</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 #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>
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>
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 #63460 (Rejected): serial console stopped working on hypervhttps://progress.opensuse.org/issues/634602020-02-14T12:51:49Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>I cannot find a single hyperv test that does not fail.</p>
<p>Looks like the tests fail either on bootloader_start with error like :</p>
<p>SHA256 checksum does not match for ISO:<br>
Calculated: <br>
Expected: aac524d3a46967c89bb8d8761bc6e9f2986b40bc1a1ae60abc746dff01b001ee</p>
<p>or after first boot, while running commands that time out.</p>
<p><strong>Test suite | Failed module</strong><br>
skip_registration@svirt-hyperv : integration_services [1]<br>
skip_registration@svirt-hyperv-uefi : bootloader_start<br>
lvm+RAID1@svirt-hyperv(/uefi) : validate_lvm_raid1 [2]<br>
mediacheck@svirt-hyperv(/uefi) : bootloader_hyperv<br>
minimal+base_yast@svirt-hyperv : system_prepare [3]<br>
minimal+base_yast@svirt-hyperv-uefi : first_boot [4]</p>
<p>[1] Test died: command 'curl -f -v <a href="http://10.160.0.147:20103/V0WsZ7j56nMjfBev/current_script">http://10.160.0.147:20103/V0WsZ7j56nMjfBev/current_script</a> > /tmp/scriptHwmlo.sh' timed out at /usr/lib/os-autoinst/distribution.pm line 260.<br>
[2] Test died: script timeout: lvscan | awk '{print $2}' | sed s/\'//g at /usr/lib/os-autoinst/testapi.pm line 1104.<br>
[3] Test died: command 'chown bernhard /dev/ttyS0 && usermod -a -G tty,dialout,$(stat -c %G /dev/ttyS0) bernhard' timed out at /var/lib/openqa/cache/openqa.suse.de/tests/sle/lib/utils.pm line 1185.<br>
[4] Test died: no candidate needle with tag(s) 'linux-login, emergency-shell, emergency-mode' matched (<--- looks like system hang on grub menu)</p>
<p>Example:</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-lvm+RAID1@svirt-hyperv fails in<br>
<a href="https://openqa.suse.de/tests/3885844/modules/validate_lvm_raid1/steps/11" class="external">validate_lvm_raid1</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: slindomansilla, jrauch</p>
<p>Combination of LVM and RAID1, installation of RAID1 on top of LVM using expert partitioner.</p>
<p>(crypt-)LVM installations can take longer, especially on non-x86_64 architectures.</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/3881706" class="external">139.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/3868027" class="external">136.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-hyperv&test=lvm%2BRAID1&version=15-SP2" class="external">latest</a></p>
openQA Project - action #62243 (Resolved): After latest updates, openQA has problematic behavior ...https://progress.opensuse.org/issues/622432020-01-17T12:44:19Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After updating my workstation, OpenQA started having issue to run any job. The job remains on schedule, even though sometimes it runs. Sometimes it gets terminated without any error messages or logs. Sometimes I get the error "os-autoinst command server not available, job is likely not running" even though job runs. Video or Live view are never available. Initially, I thought this was a problem with Tumpleweed, so I formatted the workstation and installed Leap. I have the exact same behavior on Leap as well. Also in containerized version.</p>
<p>Link to OpenQA in container:<br>
<a href="http://falafel.suse.cz/" class="external">http://falafel.suse.cz/</a></p>