openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-09-22T06:11:38ZopenSUSE Project Management Tool
Redmine openQA Tests - action #136298 (Resolved): Leap Micro test fails in transactional_updatehttps://progress.opensuse.org/issues/1362982023-09-22T06:11:38Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario leap-micro-5.5-MicroOS-Image-x86_64-microos_image_default@64bit fails in<br>
<a href="https://openqa.opensuse.org/tests/3591732/modules/transactional_update/steps/96" class="external">transactional_update</a></p>
<p>As the job says, there should be an expected change when <a href="https://openqa.opensuse.org/tests/3591732#step/transactional_update/23" class="external">installing the local rpm</a><br>
<code>transactional-update -n ptf install update-test-trivial/update-test-security-5.1-1.20.x86_64.rpm</code><br>
and <a href="https://openqa.opensuse.org/tests/3591732#step/transactional_update/73" class="external">adding the utt repo</a> along with <code>transactional-update -n cleanup up</code>. </p>
<p>The local package is <code>/data/microos/utt-opensuse-x86_64.tgz</code> and the repo is <code>/data/microos/utt-leap.repo</code>, both in the data directory:<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/data/microos" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/data/microos</a></p>
<p>This was working on Leap Micro 5.4 (no existing jobs), so for some reason now the packages seem to be the same or the local rpm is already a higher version than the one in the repo, and zypper says <code>zypper: nothing to update</code>.</p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>MicroOS image boot with ignition disk and default tests. Default tests are transactional-update, rebootmgr, health_check, cockpit service and some other checks specific to MicroOS.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since the beginning.</p>
openQA Tests - action #129601 (Feedback): bootloader_uefi fails too often in aarch64https://progress.opensuse.org/issues/1296012023-05-19T05:49:51Zjlausuchjalausuch@suse.com
<p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/bootloader_uefi.pm" class="external">installation/bootloader_uefi.pm</a> times out quite often because openQA does not have time to enter uefi grub2 configuration screen before the 10s grub timeout.</p>
<p>e.g. <br>
<a href="https://openqa.suse.de/tests/11157624#step/bootloader_uefi/11">https://openqa.suse.de/tests/11157624#step/bootloader_uefi/11</a><br>
<a href="https://openqa.suse.de/tests/11157620#step/bootloader_uefi/11">https://openqa.suse.de/tests/11157620#step/bootloader_uefi/11</a><br>
<a href="https://openqa.suse.de/tests/11157622#step/bootloader_uefi/11">https://openqa.suse.de/tests/11157622#step/bootloader_uefi/11</a></p>
<p>The culprit is that the first <code>bootloader-grub2</code> takes too long to match.</p>
<p>This is a successful run:</p>
<pre><code>[2023-05-17T22:29:48.135632+02:00] [debug] [pid:78975] <<< testapi::assert_screen(mustmatch=[
"bootloader-shim-import-prompt",
"bootloader-grub2"
], timeout=90)
[2023-05-17T22:29:49.928958+02:00] [warn] [pid:79369] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.82 seconds for 14 candidate needles - make your needles more specific
[2023-05-17T22:29:49.929428+02:00] [debug] [pid:79369] no match: 89.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:29:50.104691+02:00] [debug] [pid:79369] no change: 88.0s
[2023-05-17T22:29:50.588948+02:00] [debug] [pid:79369] no match: 88.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:29:51.105278+02:00] [debug] [pid:79369] no change: 87.0s
[2023-05-17T22:29:51.589146+02:00] [debug] [pid:79369] no match: 87.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:29:52.105972+02:00] [debug] [pid:79369] no change: 86.0s
[2023-05-17T22:29:52.589983+02:00] [debug] [pid:79369] no match: 86.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:00.232487+02:00] [warn] [pid:79369] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 7.13 seconds for 14 candidate needles - make your needles more specific
[2023-05-17T22:30:00.232953+02:00] [debug] [pid:79369] no match: 85.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:00.248237+02:00] [debug] [pid:79369] no change: 77.8s
[2023-05-17T22:30:00.733227+02:00] [debug] [pid:79369] no match: 77.8s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:01.236512+02:00] [debug] [pid:79369] no change: 76.9s
[2023-05-17T22:30:01.743323+02:00] [warn] [pid:79369] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.51 seconds for 14 candidate needles - make your needles more specific
[2023-05-17T22:30:01.743772+02:00] [debug] [pid:79369] no match: 76.9s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:09.594737+02:00] [warn] [pid:79369] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 7.36 seconds for 14 candidate needles - make your needles more specific
[2023-05-17T22:30:09.595227+02:00] [debug] [pid:79369] no match: 75.9s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:10.332028+02:00] [warn] [pid:79369] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.71 seconds for 14 candidate needles - make your needles more specific
[2023-05-17T22:30:10.332520+02:00] [debug] [pid:79369] no match: 68.5s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:11.328004+02:00] [warn] [pid:79369] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.72 seconds for 14 candidate needles - make your needles more specific
[2023-05-17T22:30:11.328472+02:00] [debug] [pid:79369] no match: 67.5s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:12.205373+02:00] [warn] [pid:79369] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.59 seconds for 14 candidate needles - make your needles more specific
[2023-05-17T22:30:12.205867+02:00] [debug] [pid:79369] no match: 66.5s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:19.704649+02:00] [warn] [pid:79369] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 7.09 seconds for 14 candidate needles - make your needles more specific
[2023-05-17T22:30:19.705116+02:00] [debug] [pid:79369] no match: 65.5s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-17T22:30:20.417002+02:00] [debug] [pid:78975] >>> testapi::_handle_found_needle: found bootmenu-jeos-20201204, similarity 1.00 @ 101/208
[2023-05-17T22:30:20.419694+02:00] [debug] [pid:78975] tests/installation/bootloader_uefi.pm:124 called bootloader_setup::uefi_bootmenu_params -> lib/bootloader_setup.pm:383 called testapi::send_key_until_needlematch
[2023-05-17T22:30:20.420160+02:00] [debug] [pid:78975] <<< testapi::check_screen(mustmatch="grub2-enter-edit-mode", timeout=0)
</code></pre>
<p>And this is a failed run:</p>
<pre><code>[2023-05-18T22:31:23.112731+02:00] [debug] [pid:20579] <<< testapi::assert_screen(mustmatch=[
"bootloader-shim-import-prompt",
"bootloader-grub2"
], timeout=90)
[2023-05-18T22:31:24.904170+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.82 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:24.904637+02:00] [debug] [pid:21382] no match: 89.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:25.081871+02:00] [debug] [pid:21382] no change: 88.0s
[2023-05-18T22:31:25.580143+02:00] [debug] [pid:21382] no match: 88.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:26.094924+02:00] [debug] [pid:21382] no change: 87.0s
[2023-05-18T22:31:26.569793+02:00] [debug] [pid:21382] no match: 87.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:27.083393+02:00] [debug] [pid:21382] no change: 86.0s
[2023-05-18T22:31:27.553981+02:00] [debug] [pid:21382] no match: 86.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:35.276260+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 7.19 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:35.276731+02:00] [debug] [pid:21382] no match: 85.0s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:36.083159+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.78 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:36.083646+02:00] [debug] [pid:21382] no match: 77.8s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:36.279755+02:00] [debug] [pid:21382] no change: 76.8s
[2023-05-18T22:31:37.020384+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.74 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:37.020854+02:00] [debug] [pid:21382] no match: 76.8s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:44.628366+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 7.35 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:44.628834+02:00] [debug] [pid:21382] no match: 75.8s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:45.401250+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.74 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:45.401731+02:00] [debug] [pid:21382] no match: 68.4s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:46.386500+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.74 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:46.386994+02:00] [debug] [pid:21382] no match: 67.4s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:47.387270+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.74 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:47.387869+02:00] [debug] [pid:21382] no match: 66.4s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:55.130059+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 7.48 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:55.130529+02:00] [debug] [pid:21382] no match: 65.4s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:55.715449+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.56 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:55.715931+02:00] [debug] [pid:21382] no match: 57.9s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:31:56.143795+02:00] [debug] [pid:21382] no change: 56.9s
[2023-05-18T22:31:56.669176+02:00] [warn] [pid:21382] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.52 seconds for 14 candidate needles - make your needles more specific
[2023-05-18T22:31:56.669652+02:00] [debug] [pid:21382] no match: 56.9s, best candidate: bootloader_uefi-20210917 (0.00)
[2023-05-18T22:32:04.606465+02:00] [debug] [pid:20579] >>> testapi::_handle_found_needle: found bootmenu-jeos-20201204, similarity 1.00 @ 101/208
[2023-05-18T22:32:04.610142+02:00] [debug] [pid:20579] tests/installation/bootloader_uefi.pm:124 called bootloader_setup::uefi_bootmenu_params -> lib/bootloader_setup.pm:383 called testapi::send_key_until_needlematch
[2023-05-18T22:32:04.610684+02:00] [debug] [pid:20579] <<< testapi::check_screen(mustmatch="grub2-enter-edit-mode", timeout=0)
</code></pre>
<p>So, in the first case, the needle takes around 25s to be matched after the VM is started, but in the second case it takes ~45s, which makes the grub to pick the default option and boot the system without a chance to go to the <code>grub2-enter-edit-mode</code> screen.</p>
ALP - action #125855 (Resolved): Create OBS-sync scripts for ALP Micro and Bedrockhttps://progress.opensuse.org/issues/1258552023-03-13T07:52:34Zjlausuchjalausuch@suse.com
<p>Create new sync scripts in <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">openqa-trigger-from-obs</a></p>
<p>Currently we have 2 sync scripts that we used for the ALP December prototype:<br>
<a href="https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE:ALP:ToTest.xml" class="external">https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE:ALP:ToTest.xml</a><br>
<a href="https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE:ALP:Staging.xml" class="external">https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE:ALP:Staging.xml</a></p>
<p>But this project in IBS is obsolete and we should now sync the new images from the 2 new IBS projects:<br>
<a href="https://build.opensuse.org/project/show/SUSE:ALP:Products:Micro:0.1" class="external">https://build.opensuse.org/project/show/SUSE:ALP:Products:Micro:0.1</a><br>
<a href="https://build.opensuse.org/project/show/SUSE:ALP:Products:Bedrock:0.1" class="external">https://build.opensuse.org/project/show/SUSE:ALP:Products:Bedrock:0.1</a></p>
<p><a href="https://download.opensuse.org/repositories/SUSE:/ALP:/Products:/" class="external">https://download.opensuse.org/repositories/SUSE:/ALP:/Products:/</a></p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create new sync script for ALP Micro in <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">openqa-trigger-from-obs</a></li>
<li>Create new sync script for ALP Bedrock in <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">openqa-trigger-from-obs</a></li>
</ul>
ALP - action #125852 (Resolved): Create 2 new job groups in openqa.opensuse.org to hold the 2 new...https://progress.opensuse.org/issues/1258522023-03-13T07:44:11Zjlausuchjalausuch@suse.com
<p>So far, we have been using a <a href="https://openqa.opensuse.org/group_overview/100" class="external">job group</a> for ALP images, but that product in IBS is obsolete.</p>
<p>Instead, we now have 2 flavors corresponding to the 2 new products (see epic).</p>
<p>For now, we can keep the set of test suites the same as we had for ALP December, and we can do modifications as needed.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create 2 new jobs in O3: <code>ALP-Micro</code> and <code>ALP-Bedrock</code></li>
<li>Create corresponding mediums</li>
<li>Create the content of the groups in <a href="https://github.com/os-autoinst/opensuse-jobgroups" class="external">opensuse-jobgroups</a></li>
</ul>
ALP - action #114935 (Resolved): Add standard container host tests for ALP prototype in O3https://progress.opensuse.org/issues/1149352022-08-03T07:39:42Zjlausuchjalausuch@suse.com
<p>There are currently no container tests for ALP prototype.</p>
<p>The idea is to enable the same set of tests that are run for MicroOS/Leap-Micro, e.g. <a href="https://openqa.opensuse.org/tests/2433988" class="external">https://openqa.opensuse.org/tests/2433988</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria:<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<p>Create a new jobs <code>alp_containers</code> for the flavors <code>kvm-and-xen</code> and <code>kvm-and-xen_NonTransactional</code> which schedules the following modules:</p>
<pre><code>- toolbox
- podman
- image_podman
- podman_3rd_party_images
- podman_pods
- rootless_podman
</code></pre> ALP - action #112826 (Resolved): Fix ALP SelfInstall jobshttps://progress.opensuse.org/issues/1128262022-06-21T21:27:06Zjlausuchjalausuch@suse.com
<p>These jobs fail booting the image:<br>
<a href="https://openqa.opensuse.org/tests/2427880#step/bootloader_uefi/2" class="external">https://openqa.opensuse.org/tests/2427880#step/bootloader_uefi/2</a></p>
<p>Expected result (Leap Micro):<br>
<a href="https://openqa.opensuse.org/tests/2426647#step/bootloader_uefi/3" class="external">https://openqa.opensuse.org/tests/2426647#step/bootloader_uefi/3</a></p>
ALP - action #112427 (Resolved): 5. Adapt transactional server related test cases for ALPhttps://progress.opensuse.org/issues/1124272022-06-14T16:09:51Zjlausuchjalausuch@suse.com
<p>The idea for the first PoC for ALP testing in openQA is to copy what we already have for Leap Micro/MicroOS.<br>
So, taking this job as an example: <a href="https://openqa.opensuse.org/tests/2351803" class="external">https://openqa.opensuse.org/tests/2351803</a><br>
we should basically get the same results but executing them on ALP images.</p>
<p>The used schedule in this case is <a href="https://openqa.opensuse.org/tests/2351803/settings/schedule/sle-micro/raw_image.yaml" class="external">https://openqa.opensuse.org/tests/2351803/settings/schedule/sle-micro/raw_image.yaml</a><br>
But a different approach could be used (e.g <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/products/microos/main.pm" class="external">main.pm</a>).</p>
ALP - action #112424 (Resolved): 4. Enable OBS sync for ALP images for openQAhttps://progress.opensuse.org/issues/1124242022-06-14T16:06:33Zjlausuchjalausuch@suse.com
<p>To be able to trigger new openQA test for every build of ALP images, we need to enable this configuration into <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">https://github.com/os-autoinst/openqa-trigger-from-obs</a>.</p>
<p>The OBS project to sync is: <code>devel:LEO/ALP</code>: <a href="https://build.opensuse.org/package/show/devel:LEO/ALP" class="external">https://build.opensuse.org/package/show/devel:LEO/ALP</a><br>
The images are available for download here: <a href="https://download.opensuse.org/repositories/devel:/LEO/images/" class="external">https://download.opensuse.org/repositories/devel:/LEO/images/</a><br>
We need to sync the following flavors (for now):</p>
<ul>
<li>kvm-and-xen</li>
<li>kvm-and-xen_NonTransactional</li>
<li>SelfInstall</li>
<li>SelfInstall_NonTransactional</li>
</ul>
<p>and also sync the repository so that we can use the <code>SCC_URL</code> variable pointing to local assets.</p>
ALP - action #112421 (Resolved): 3. Create a new product in os-autoinst-distri-opensusehttps://progress.opensuse.org/issues/1124212022-06-14T16:03:47Zjlausuchjalausuch@suse.com
<p>Since we are going to use <code>DISTRI=alp</code> for new ALP tests in openQA, we need to add the product to<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/products" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/products</a><br>
And also in O3 machine (ariel).</p>
<pre><code>/var/lib/openqa/share/tests> ll
total 4
lrwxrwxrwx 1 geekotest nogroup 8 Apr 5 10:34 d-installer -> opensuse
lrwxrwxrwx 1 root root 8 Sep 4 2017 kubic -> opensuse
lrwxrwxrwx 1 geekotest nogroup 8 Mar 30 15:36 leap-micro -> opensuse
lrwxrwxrwx 1 geekotest nogroup 8 Apr 16 2019 microos -> opensuse
drwxr-xr-x 5 geekotest nogroup 121 Feb 11 2020 obs
lrwxrwxrwx 1 root root 6 Jan 16 2019 openQA -> openqa
drwxr-xr-x 6 geekotest nogroup 166 Oct 11 2021 openqa
drwxr-xr-x 15 geekotest nogroup 4096 Jun 13 12:08 opensuse
drwxr-xr-x 4 geekotest nogroup 65 Apr 16 2020 repositories
lrwxrwxrwx 1 root root 8 Jul 22 2016 windows -> opensuse
</code></pre>
<p>we would need another symlinc to <code>alp -> opensuse</code>.</p>
ALP - action #112418 (Resolved): 2. Create new job group for ALP in openqa.opensuse.orghttps://progress.opensuse.org/issues/1124182022-06-14T16:01:12Zjlausuchjalausuch@suse.com
<p>I created <a href="https://openqa.opensuse.org/group_overview/100" class="external">https://openqa.opensuse.org/group_overview/100</a><br>
but it's missing all the yaml content. </p>
<p>The products depend on the mediums defined <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: 1. Create new mediums for ALP in openqa.opensuse.org (Resolved)" href="https://progress.opensuse.org/issues/112412">#112412</a></p>
<p>The test suites can be similar to what we do today for <a href="https://openqa.opensuse.org/group_overview/94" class="external">Leap Micro images</a>.<br>
My proposal would be:<br>
<code>alp_image_default</code> (regular transactional-update, rebootmgr and health-checker test cases).<br>
<code>alp_containers</code> (test suite running podman, toolbox and other container tests)</p>
ALP - action #112412 (Resolved): 1. Create new mediums for ALP in openqa.opensuse.orghttps://progress.opensuse.org/issues/1124122022-06-14T15:56:38Zjlausuchjalausuch@suse.com
<p>The new mediums should have:</p>
<p><code>distri = alp</code><br>
<code>version = 0.1</code><br>
<code>arch = x86_64</code> (aarch64 might come later)</p>
<p><em>4 flavors (mediums):</em></p>
<ul>
<li><code>kvm-and-xen</code></li>
<li><code>kvm-and-xen_NonTransactional</code></li>
<li><code>SelfInstall</code></li>
<li><code>SelfInstall_NonTransactional</code></li>
</ul>
openQA Tests - action #107062 (Feedback): Multiple failures due to network issueshttps://progress.opensuse.org/issues/1070622022-02-18T08:27:41Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>I will use this ticket to collect the different errors I observe in our tests (at least for QE-C squad) that fail due to network issues.<br>
Normally a restart helps to get the job green again (in case we need it green), but this is not the ideal solution.</p>
<p>The idea of this ticket is to collect more potential issues caught by reviewers and propose solutions for some of them, in the code (retry same command several times might help) or in the infra side. </p>
<p>There is an example for each error I found, but from my experience reviewing jobs every day, these failures happen multiple times a day and randomly (difficult to predict).</p>
<p>1) <strong>SUSEConnect timeouts</strong> -> <a href="https://openqa.suse.de/tests/8189768#step/docker/34">https://openqa.suse.de/tests/8189768#step/docker/34</a><br>
<code>Test died: command 'SUSEConnect -p sle-module-containers/${VERSION_ID}/${CPU} ' timed out at /usr/lib/os-autoinst/testapi.pm line 1039.</code></p>
<p>Or <a href="https://openqa.suse.de/tests/8193554#step/suseconnect_scc/8">https://openqa.suse.de/tests/8193554#step/suseconnect_scc/8</a><br>
<code>Test died: command 'SUSEConnect -r $regcode' timed out at /usr/lib/os-autoinst/testapi.pm line 950.</code></p>
<p>2) <strong><a href="updates.suse.com" class="external">updates.suse.com</a> not reachable</strong> -> <a href="https://openqa.suse.de/tests/8189697#step/image_docker/1110">https://openqa.suse.de/tests/8189697#step/image_docker/1110</a></p>
<pre><code>Retrieving: kmod-25-6.10.1.aarch64.rpm [.........error]
Abort, retry, ignore? [a/r/i/...? shows all options] (a): a
Download (curl) error for 'https://updates.suse.com/SUSE/Updates/SLE-Module-Basesystem/15-SP2/aarch64/update/aarch64/kmod-25-6.10.1.aarch64.rpm?nE0jiYdfiOdLYjH0o-llNN2xIDXncon0vYw8z1aBPGx00H9S1eN413vUsfSJnzFrVz-CoZoGtSdsPKIDRAOQy3Xw2Tac3Yx5_1i8TPomSNiqhDJ0Ayxro23n46NHHB-XHq669RlHs17wiUFSJiSMCSh-YzdGdFw':
Error code: Connection failed
Error message: Could not resolve host: updates.suse.com
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.
</code></pre>
<p>3) <strong>SCC timeouts</strong> -> <a href="https://openqa.suse.de/tests/8189613#step/image_docker/316">https://openqa.suse.de/tests/8189613#step/image_docker/316</a></p>
<pre><code>docker run --entrypoint /usr/lib/zypp/plugins/services/container-suseconnect-zypp -i zypper_docker_derived lp
...
2022/02/18 07:16:19 Installed product: SLES-12.3-x86_64
2022/02/18 07:16:19 Registration server set to https://scc.suse.com
2022/02/18 07:16:30 Get https://scc.suse.com/connect/subscriptions/products?arch=x86_64&identifier=SLES&version=12.3: dial tcp: lookup scc.suse.com on 10.0.2.3:53: read udp 172.17.0.2:37151->10.0.2.3:53: i/o timeout
</code></pre>
<p>4) <strong>zypper ref timeout or error</strong> -> <a href="https://openqa.opensuse.org/tests/2193730#step/image_podman/124">https://openqa.opensuse.org/tests/2193730#step/image_podman/124</a></p>
<pre><code>podman run -i --name 'refreshed' --entrypoint '' registry.opensuse.org/opensuse/leap/15.3/images/totest/containers/opensuse/leap:15.3 zypper -nv ref
...
Retrieving: cb71cb070e8aac79327e6f1b6edc5317122ca1f72970299c3cb2cf505e18b27f-deltainfo.xml.gz [........................done (82.3 KiB/s)]
Retrieving: 832729371fe20bc1a4d27e59d76c10ffe2c0b5a1ff71c4e934e7a11baa24a74b-primary.xml.gz [............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................error (87.0 KiB/s)]
WJdDM-124-
</code></pre>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> All existing subtasks are resolved, no additional work needed on top</li>
</ul>
openQA Tests - action #93339 (Resolved): test fails in validate_btrfshttps://progress.opensuse.org/issues/933392021-06-01T09:16:42Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Server-DVD-Updates-x86_64-sle_image_on_sle_host@64bit fails in<br>
<a href="https://openqa.suse.de/tests/6149331/modules/validate_btrfs/steps/39" class="external">validate_btrfs</a><br>
Other failures:<br>
All Container jobs, e.g. <a href="https://openqa.suse.de/tests/6151606" class="external">https://openqa.suse.de/tests/6151606</a><br>
All Public Cloud jobs, e.g. <a href="https://openqa.suse.de/tests/6149926#step/validate_btrfs/39" class="external">https://openqa.suse.de/tests/6149926#step/validate_btrfs/39</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/6149331" class="external">20210601-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=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=sle_image_on_sle_host&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #89287 (Resolved): test fails in yast2_lanhttps://progress.opensuse.org/issues/892872021-03-01T14:48:17Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-JeOS-for-MS-HyperV-x86_64-jeos-main@svirt-hyperv fails in<br>
<a href="https://openqa.suse.de/tests/5552124/modules/yast2_lan/steps/21" class="external">yast2_lan</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<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/5462492" class="external">23.32</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=JeOS-for-MS-HyperV&machine=svirt-hyperv&test=jeos-main&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #58148 (Rejected): [kernel][multipath] Timeout in qa_kernel_multipathhttps://progress.opensuse.org/issues/581482019-10-14T15:19:53Zjlausuchjalausuch@suse.com
<p>The test times out after 2 hours. Need to investigate why.</p>
<p><a href="https://openqa.suse.de/tests/3470142" class="external">https://openqa.suse.de/tests/3470142</a><br>
<a href="https://openqa.suse.de/tests/3470021" class="external">https://openqa.suse.de/tests/3470021</a></p>