openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-04-17T07:59:50ZopenSUSE Project Management Tool
Redmine openQA Project - action #127739 (New): ASSET_1 gets outdated value when using openqa-clone-custom...https://progress.opensuse.org/issues/1277392023-04-17T07:59:50Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>When using openqa-clone-custom-git-refspec in order to clone a job, the value of ASSET_1 or any other ASSET get's the value from settings. But usually, the ASSET uploaded after the original job is run, gets another file name. For example, if ASSET_1=dev_tools.dud in settings, the original job will have uploaded ASSET_1=10931294-dev_tools.dud and the cloned job will fail because it cannot find dev_tools.dud with error:<br>
[info] [<a class="issue tracker-4 status-5 priority-4 priority-default closed" title="action: Breadcrumbs (Closed)" href="https://progress.opensuse.org/issues/555">#555</a>] Downloading "dev_tools.dud" from "<a href="http://openqa.suse.de/tests/10932003/asset/other/dev_tools.dud" class="external">http://openqa.suse.de/tests/10932003/asset/other/dev_tools.dud</a>"<br>
[info] [<a class="issue tracker-4 status-5 priority-4 priority-default closed" title="action: Breadcrumbs (Closed)" href="https://progress.opensuse.org/issues/555">#555</a>] Download of "/var/lib/openqa/cache/openqa.suse.de/dev_tools.dud" failed: 404 Not Found</p>
<p>In order to have a successful cloning, ASSET_1 has to be manually set to ASSET_1=10931294-dev_tools.dud while typing the refspec command.<br>
#openqa-clone-custom-git-refspec <a href="https://github.com/sofiasyria/os-autoinst-distri-opensuse/tree/master" class="external">https://github.com/sofiasyria/os-autoinst-distri-opensuse/tree/master</a> <a href="https://openqa.suse.de/tests/10931666" class="external">https://openqa.suse.de/tests/10931666</a> ASSET_1='10931294-dev_tools.dud'</p>
<p>It would be useful to automate the above process. </p>
openQA Infrastructure - action #127337 (Resolved): Some s390x workers have been failing for all j...https://progress.opensuse.org/issues/1273372023-04-06T09:04:57Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>There are quite a few s390x failures on booting, so after comparing test results, the observation that workers:<br>
<a href="https://openqa.suse.de/admin/workers/1328" class="external">grenache-1:30</a><br>
<a href="https://openqa.suse.de/admin/workers/1348" class="external">grenache-1:40</a><br>
<a href="https://openqa.suse.de/admin/workers/1809" class="external">grenache-1:43</a><br>
<a href="https://openqa.suse.de/admin/workers/1812" class="external">grenache-1:44</a></p>
<p>have been constantly failing for all jobs for the last 11 months. It seeems that before this period of time, the workers (besides grenache-1:44 which was still s390x) were used for ipm and ppc tests and they are now switched to s390x service.</p>
<p>A very frequent error message is : Test died: unexpected end of data at /usr/lib/os-autoinst/consoles/VNC.pm line 187. <a href="https://openqa.suse.de/tests/10869590#step/bootloader_start/39" class="external">example</a> </p>
<p>Possibly related with: <a href="https://progress.opensuse.org/issues/108266" class="external">https://progress.opensuse.org/issues/108266</a></p>
<p>Note: we noticed this issue, after creating a generic s390x-kvm machine, to take advantage of s390-kvm WORKER_CLASS. It seems that other current s390x jobs that are designated to use s390x-kvm-sle12/15 do not run on these workers. For more information, see : <a href="https://progress.opensuse.org/issues/126293" class="external">https://progress.opensuse.org/issues/126293</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>
openQA Project - action #87725 (New): MULTIPATH backend variable doesn't set HDDMODEL for aarch64https://progress.opensuse.org/issues/877252021-01-13T16:48:15Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>According to the definition of the variable, if MULTIPATH=1:<br>
"Add HDD drives as multipath devices. Override HDDMODEL to virtio-scsi-pci"</p>
<p>That indeed happens when used on 64bit or ppc64le, but for aarch64, HDDMODEL remains to default value "virtio-blk-device". Test fails with error: "Device 'virtio-blk-device' can't go on SCSI bus". In order for the test to work, HDDMODEL needs to be set to "scsi-hd".</p>
qe-yam - action #81310 (Resolved): [sporadic][timeboxed:10h] test fails in mediacheck on svirt uefihttps://progress.opensuse.org/issues/813102020-12-23T13:09:35Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>We need to investigate what happens, as we already saw some issues with unexpected reboots of the VMs.</p>
<p>@Joaquin should be able to help to find the bug entry ;)</p>
<p>It seems like the function "select_bootmenu_more" doesn't select the expected item in the grub menu. For UEFI, there are some additional steps in the function:</p>
<pre><code> if (get_var('UEFI')) {
send_key 'e';
send_key 'down' for (1 .. 4);
send_key 'end';
# newer versions of qemu on arch automatically add 'console=ttyS0' so
# we would end up nowhere. Setting console parameter explicitly
# See https://bugzilla.suse.com/show_bug.cgi?id=1032335 for details
push @params, 'console=tty1' if get_var('MACHINE') =~ /aarch64/;
# Hyper-V defaults to 1280x1024, we need to fix it here
push @params, get_hyperv_fb_video_resolution if check_var('VIRSH_VMM_FAMILY', 'hyperv');
type_boot_parameters(" @params ");
save_screenshot;
send_key 'f10';
}
</code></pre>
<p>All look good until f10 is pressed. The mediacheck is supposed to start at this point, but instead, the grub menu appears.</p>
<p>related ticket : <a href="https://progress.opensuse.org/issues/70228" class="external">https://progress.opensuse.org/issues/70228</a> </p>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-mediacheck@svirt-hyperv-uefi fails in<br>
<a href="https://openqa.suse.de/tests/5212695/modules/mediacheck/steps/27" class="external">mediacheck</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Select the mediacheck option from the installation menu and assert a successful media check.</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/5212695" class="external">114.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: <a href="https://openqa.suse.de/tests/5194446" class="external">109.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=svirt-hyperv-uefi&test=mediacheck&version=15-SP3" class="external">latest</a></p>
qe-yam - action #76882 (Resolved): Unit test for yast2-metapackage-handler OneClickInstall.rb (pa...https://progress.opensuse.org/issues/768822020-11-02T19:05:32Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for OneClickInstall.rb (<a href="https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstall.rb" class="external">https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstall.rb</a>)</p>
<ul>
<li>Load</li>
<li>makeXMLFriendly</li>
<li>fromXMLFriendly</li>
<li>SetupXML</li>
<li>ToXML</li>
<li>FromXML</li>
</ul>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>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>
qe-yam - action #73306 (Closed): [y][timeboxed:20h] test fails in await_installhttps://progress.opensuse.org/issues/733062020-10-13T17:35:49Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Installation takes too long, resulting in test failure. The issue demonstrates similarity with already fixed bugs:<br>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1177415" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1177415</a><br>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1177434" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1177434</a></p>
<p>Possibly related could be the follow up bug which is not resolved yet: <a href="https://bugzilla.suse.com/show_bug.cgi?id=1177546" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1177546</a></p>
<p>It might be related to load on the network as downloading speed is very low in the failed runs, which might be the case when there are a lot of jobs running. We have triggered <a href="https://openqa.suse.de/tests/4854207" class="external">https://openqa.suse.de/tests/4854207</a> , let's see if it works.</p>
<p>openQA test in scenario sle-15-SP3-Online-ppc64le-ssh-X@ppc64le-hmc-single-disk fails in<br>
<a href="https://openqa.suse.de/tests/4818494/modules/await_install/steps/69" class="external">await_install</a></p>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Online&machine=ppc64le-hmc-single-disk&test=ssh-X&version=15-SP3" class="external">latest</a></p>
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>
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>
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 #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 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>