openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-26T07:09:51ZopenSUSE Project Management Tool
Redmine openQA Tests - action #157966 (New): [qe-core][ppc64le][multi-machine]test fails in boot_to_deskt...https://progress.opensuse.org/issues/1579662024-03-26T07:09:51Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP6-Online-ppc64le-ping_server@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/13872790/modules/boot_to_desktop/steps/6" class="external">boot_to_desktop</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Multimachine Ping server test. Maintainer: <a href="mailto:dheidler@suse.de">dheidler@suse.de</a> </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/13872790" class="external">71.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/13828796" class="external">67.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=ping_server&version=15-SP6" class="external">latest</a></p>
openQA Tests - action #157885 (New): [qe-core]test fails in django, need to double confirm with d...https://progress.opensuse.org/issues/1578852024-03-25T12:12:18Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP6-Online-x86_64-stack_tests_python@64bit fails in<br>
<a href="https://openqa.suse.de/tests/13848328/modules/django/steps/26" class="external">django</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>.</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/13493806" class="external">54.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=stack_tests_python&version=15-SP6" class="external">latest</a></p>
openQA Tests - action #157879 (New): [qe-core][functional]test fails in apache, can't read /usr/...https://progress.opensuse.org/issues/1578792024-03-25T11:55:36Zrfan1richard.fan@suse.com
<a name="Need-to-double-check-if-the-file-location-is-changed-or-a-product-bug"></a>
<h2 >Need to double check if the file location is changed or a product bug.\<a href="#Need-to-double-check-if-the-file-location-is-changed-or-a-product-bug" class="wiki-anchor">¶</a></h2>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP6-Online-x86_64-default@64bit fails in<br>
<a href="https://openqa.suse.de/tests/13847316/modules/apache/steps/137" class="external">apache</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 Core</p>
<p>The standard scenario where we mainly just follow installation suggestions without any adjustments.</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/13829256" class="external">67.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/13792585" class="external">64.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=64bit&test=default&version=15-SP6" class="external">latest</a></p>
openQA Project - action #157282 (New): [tools] openQA seems show wrong VNC access infromation in ...https://progress.opensuse.org/issues/1572822024-03-15T01:37:59Zrfan1richard.fan@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>On non-qemu backend openQA setups, take s390x-kvm as an example, when I try to debug some issue with developer mode,<br>
we can get the information from openqa web UI like:<br>
<code>You might be able to connect to the SUT at worker32.oqa.prg2.suse.org:5994 via VNC with shared mode enabled (eg. vncviewer workerxx.xx.org:5994 -Shared for TigerVNC)</code>.</p>
<p>However, it can not work for s390x-kvm setup since it is remote access. we may need to access the setup with below methods:</p>
<ol>
<li>ssh to vm directly </li>
<li>vncviewer to access with ip addr of s390x-SUT with right port</li>
<li>accss to s390x-SUT and use <code>virsh console</code> command to access the serial terminal/console</li>
</ol>
<p>Please see attached file.</p>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<ol>
<li>OpenQA can show test the right VNC port or right method to access the setup</li>
<li>For no qemu backend, openQA may show some warning messages that the VNC access information is not usable.</li>
</ol>
openQA Tests - action #154312 (Rejected): [qe-core][slem6.0][uefi encrypt]test fails in disk_boothttps://progress.opensuse.org/issues/1543122024-01-26T06:31:17Zrfan1richard.fan@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>Default-encrypted image failed to start in UEFI Mode with error message:</p>
<p>'Dependency failed for local encrypted volumes'</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-micro-6.0-Default-encrypted-x86_64-slem_image_default@uefi-virtio-vga fails in<br>
<a href="https://openqa.suse.de/tests/13344633/modules/disk_boot/steps/22" class="external">disk_boot</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>SLE Micro image boot with ignition disk and default tests. Default tests are transactional-update, rebootmgr, health_check, cockpit service and some other checks specific to SLE Micro.</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/13276547" class="external">8.48</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-micro&flavor=Default-encrypted&machine=uefi-virtio-vga&test=slem_image_default&version=6.0" class="external">latest</a></p>
openQA Tests - action #154303 (Rejected): [qe-core][slem6.0]disk boot failed with encrypt root di...https://progress.opensuse.org/issues/1543032024-01-26T03:00:04Zrfan1richard.fan@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>I don't know if we have some test module to handle encrypted root disk for slem 6.0. if not, we may need to fix it</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-micro-6.0-Default-encrypted-x86_64-slem_image_default@64bit fails in<br>
<a href="https://openqa.suse.de/tests/13344631/modules/disk_boot/steps/3" class="external">disk_boot</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>SLE Micro image boot with ignition disk and default tests. Default tests are transactional-update, rebootmgr, health_check, cockpit service and some other checks specific to SLE Micro.</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/13276546" class="external">8.48</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-micro&flavor=Default-encrypted&machine=64bit&test=slem_image_default&version=6.0" class="external">latest</a></p>
openQA Tests - action #153163 (Rejected): [qe-core] Move install tests in openSUSE Leap 15.5/15....https://progress.opensuse.org/issues/1531632024-01-05T11:43:18Zrfan1richard.fan@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>As discussed in:<br>
<a href="https://suse.slack.com/archives/C02CSAZLAR4/p1704447006033209" class="external">https://suse.slack.com/archives/C02CSAZLAR4/p1704447006033209</a></p>
<p>We can move the installation tests to use autoyast, which can resolve install time issues and improve code readability</p>
<p><a href="https://openqa.opensuse.org/group_overview/114" class="external">leap 15.5 incidents</a><br>
<a href="https://openqa.opensuse.org/group_overview/97" class="external">leap 15.4 incidents</a></p>
<p>For autoyast template, we can find them in <a href="https://github.com/rfan1/os-autoinst-distri-opensuse/blob/7e81fe1ea9f126ff471dd3db131df5ca7e1b1b1e/data/autoyast_opensuse/opensuse_leap.xml.ep" class="external">link</a></p>
<p>However, for encrypted system, we may need to build a new one [may be we can clone from installed system]</p>
openQA Tests - action #152617 (Rejected): [qe-core]s390x zkvm installation, serial output gets st...https://progress.opensuse.org/issues/1526172023-12-14T05:18:31Zrfan1richard.fan@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>The issue might have something to do with the backend btrfs qgroup scan process.<br>
I can see serial terminal output gets stuck with messages:</p>
<pre><code>*** Starting YaST ***
WARNING: Nokogiri was built against LibXML version 2.9.14, but has dynamically loaded 2.10.3
[ 600.404515][ T163] BTRFS info (device vda2): qgroup scan completed (inconsistency flag cleared)
</code></pre>
<p>We may need to refresh it</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP5-Server-DVD-Updates-s390x-qam-gnome@s390x-kvm fails in<br>
<a href="https://openqa.suse.de/tests/13046131/modules/installation/steps/24" class="external">installation</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>.</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/12996713" class="external">20231207-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/12986621" class="external">20231206-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=Server-DVD-Updates&machine=s390x-kvm&test=qam-gnome&version=15-SP5" class="external">latest</a></p>
qe-yam - action #138473 (Rejected): Kick off reduction of yaml files in YaM scope for other inter...https://progress.opensuse.org/issues/1384732023-10-25T07:20:59Zrfan1richard.fan@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>As starting point we have 429 yaml files in <code>schedule/yast</code> after applying solution based on default without further adjustment. There is plenty of space for improvement and now we are in position to tackle individual test test suites without affecting much or break other areas.</p>
<p>One of the main motivation is to have a test case that can be run across products, sle, sle micro, openSUSE Tumblewee, openSUSE Leap, etc, so first we need to create `schedule/yam/test_cases/ . Inside this folder we will place our yaml that will be valid (in theory) for each product (we have to see what techniques we will use in each case to make this possible and we will document those).</p>
<p>This are all the installation, (we didn't go too far how to apply this for other than installation that contains steps and it fits quite well, so for now the scope are only the interactive installation, not AutoYaST ones):<br>
<a href="https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=accept_license&module_re=&distri=sle&version=15-SP5&build=102.1&groupid=129#" class="external">https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=accept_license&module_re=&distri=sle&version=15-SP5&build=102.1&groupid=129#</a></p>
<p>Let's go in the order that are displayed for example, first one is USBInstall, it has been done via <a href="https://progress.opensuse.org/issues/132971" class="external">https://progress.opensuse.org/issues/132971</a></p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Kick off the reduction of yaml files except USBInstall, <br>
<strong>AC2</strong>: Following the the steps mentioned in <a href="https://confluence.suse.com/pages/viewpage.action?pageId=1364165336" class="external">https://confluence.suse.com/pages/viewpage.action?pageId=1364165336</a><br>
<strong>AC3</strong>: We may use this ticket as a parent one and create child jobs for different install scenarios (or just create more similar tickets as this one)[Need to check with PO/SM] </p>
openQA Tests - action #135881 (New): [tools][ppc64le][qemu-backend]openqa fails to publish qcow2 ...https://progress.opensuse.org/issues/1358812023-09-18T08:40:54Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.suse.de/tests/12161670">https://openqa.suse.de/tests/12161670</a><br>
From the test log, it can not complete due to error messages as below:</p>
<pre><code class="html syntaxhl" data-language="html">[2023-09-18T08:09:11.039556+02:00] [debug] [pid:25632] running `nice ionice qemu-img convert -c -O qcow2 /var/lib/openqa/pool/2/raid/hd0-overlay4 assets_public/SLES-15-SP6-ppc64le-Build20.1-12SP5-15-SP4-ph0.qcow2`
[2023-09-18T08:09:11.132952+02:00] [debug] [pid:25632] qemu-img: Could not open '/var/lib/openqa/pool/2/raid/hd0-overlay4': Could not open backing file: Could not open backing file: Could not open backing file: Could not open backing file: Could not open backing file: Could not open '/var/lib/openqa/pool/2/SLES-12-SP5-ppc64le-GM-allpatterns.qcow2': No such file or directory
[2023-09-18T08:09:11.133967+02:00] [warn] [pid:25632] !!! bmwqemu::serialize_state: unable to extract assets: runcmd 'nice ionice qemu-img convert -c -O qcow2 /var/lib/openqa/pool/2/raid/hd0-overlay4 assets_public/SLES-15-SP6-ppc64le-Build20.1-12SP5-15-SP4-ph0.qcow2' failed with exit code 1: 'qemu-img: Could not open '/var/lib/openqa/pool/2/raid/hd0-overlay4': Could not open backing file: Could not open backing file: Could not open backing file: Could not open backing file: Could not open backing file: Could not open '/var/lib/openqa/pool/2/SLES-12-SP5-ppc64le-GM-allpatterns.qcow2': No such file or directory' at /usr/lib/os-autoinst/osutils.pm line 89.
osutils::runcmd("nice", "ionice", "qemu-img", "convert", "-c", "-O", "qcow2", "/var/lib/openqa/pool/2/raid/hd0-overlay4", ...) called at /usr/lib/os-autoinst/OpenQA/Qemu/Proc.pm line 329
OpenQA::Qemu::Proc::export_blockdev_images(OpenQA::Qemu::Proc=HASH(0x1000f309f70), qr(^hd0$)u, "assets_public", "SLES-15-SP6-ppc64le-Build20.1-12SP5-15-SP4-ph0.qcow2", 1) called at /usr/lib/os-autoinst/backend/qemu.pm line 515
backend::qemu::do_extract_assets(backend::qemu=HASH(0x1000f94e1b8), HASH(0x1000f37c540)) called at /usr/lib/os-autoinst/backend/driver.pm line 79
backend::driver::extract_assets(backend::driver=HASH(0x10011073c98), HASH(0x1000f37c540)) called at /usr/lib/os-autoinst/OpenQA/Isotovideo/Utils.pm line 230
eval {...} called at /usr/lib/os-autoinst/OpenQA/Isotovideo/Utils.pm line 230
OpenQA::Isotovideo::Utils::handle_generated_assets(OpenQA::Isotovideo::CommandHandler=HASH(0x1000f317ce0), 1) called at /usr/bin/isotovideo line 161
eval {...} called at /usr/bin/isotovideo line 122
</code></pre>
<a name="Defects"></a>
<h2 >Defects<a href="#Defects" class="wiki-anchor">¶</a></h2>
<p>So far, I can only hit the issue on ppc64le platform. I think it will impact all power+kvm tests which try to publish qcow2 images.<br>
I will try to monitor next sle15sp6 build to see how many cases are impacted, and then check with POs and tool team experts if we can set a higher priority.</p>
<p>can you please help take a look at it? more detail log can be found at detached file.</p>
openQA auto review - openqa-force-result #134873 (New): [qe-core][tools]test fails in update_inst...https://progress.opensuse.org/issues/1348732023-08-31T02:24:21Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Server-DVD-Incidents-Install-aarch64-qam-incidentinstall@aarch64-virtio fails in<br>
<a href="https://10.145.10.207/tests/11954791/modules/update_install/steps/65" class="external">update_install</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>. Incident Installation TEST<br>
MAX_JOB_TIME=9000 due to long texlive update</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://10.145.10.207/tests/11950582" class="external">:30387:amazon-ecs-init</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://10.145.10.207/tests/11948020" class="external">:30381:MozillaFirefox</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://10.145.10.207/tests/latest?arch=aarch64&distri=sle&flavor=Server-DVD-Incidents-Install&machine=aarch64-virtio&test=qam-incidentinstall&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #134684 (Rejected): [qe-core]test fails in setup_online_reposhttps://progress.opensuse.org/issues/1346842023-08-28T08:50:33Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario opensuse-15.5-DVD-Backports-Incidents-x86_64-install_with_updates_gnome@64bit-2G fails in<br>
<a href="https://openqa.opensuse.org/tests/3530121/modules/setup_online_repos/steps/15" class="external">setup_online_repos</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.opensuse.org/tests/3529663" class="external">20230826-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.opensuse.org/tests/3529504" class="external">20230825-3</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD-Backports-Incidents&machine=64bit-2G&test=install_with_updates_gnome&version=15.5" class="external">latest</a></p>
openQA Tests - action #134681 (Rejected): [qe-core][leap15.4][leap15.5]test fails on many places ...https://progress.opensuse.org/issues/1346812023-08-28T08:44:48Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario opensuse-15.4-DVD-Updates-x86_64-textmode@64bit fails in<br>
<a href="https://openqa.opensuse.org/tests/3530364/modules/patch_and_reboot/steps/96" class="external">patch_and_reboot</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Installation in textmode and selecting the textmode "desktop" during installation.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.opensuse.org/tests/3529816" class="external">20230827-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.opensuse.org/tests/3529578" class="external">20230826-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.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD-Updates&machine=64bit&test=textmode&version=15.4" class="external">latest</a></p>
openQA Infrastructure - action #132827 (Workable): [tools][qe-core]test fails in rsync_client/sal...https://progress.opensuse.org/issues/1328272023-07-17T04:05:44Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>I can see that some tests are failing due to DNS resolve issue on workers "sapworker*", especially on multi-machine tests.can someone help check?</p>
<p>Some error messages as below:<br>
<a href="https://openqa.suse.de/tests/11593878#step/salt_master/15" class="external">https://openqa.suse.de/tests/11593878#step/salt_master/15</a><br>
<a href="http://openqa.suse.de/tests/11594635#step/rsync_client/12" class="external">http://openqa.suse.de/tests/11594635#step/rsync_client/12</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.suse.de/tests/overview?result=failed&result=incomplete&result=timeout_exceeded&arch=&flavor=&machine=&test=&modules=salt_master%2Crsync_client&module_re=&distri=sle&build=20230716-1&groupid=414#" class="external">Failed test links</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>I Tried with another worker to run the rsync tests without any issue: <a href="http://openqa.suse.de/tests/11594925#dependencies" class="external">http://openqa.suse.de/tests/11594925#dependencies</a></p>
<a name="Rollback-steps"></a>
<h2 >Rollback steps<a href="#Rollback-steps" class="wiki-anchor">¶</a></h2>
<ul>
<li>Add back production worker class on sapworker{1,2,3}, i.e. revert <a href="https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/564" class="external">https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/564</a></li>
<li>Add back "tap" worker class to openqaworker1 and sapworker{1,2,3}</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>May be some network problems with workers "sapworker*", based on my tests [at least for rsync test result], the same test can pass with "worker5" but fail with "sapworker1"</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>First ensure that all openQA workers have the salt state applied cleanly, e.g. <code>sudo salt --no-color -C 'G@roles:worker' state.apply</code></li>
<li>Maybe the failure can be improved on the os-autoinst side, like a better "die"message/reason</li>
<li>As temporary measure consider disabling the "tap" class from affected workers, e.g. make it tap_pooXXX</li>
<li>Debug multi-machine capabilities according to <a href="http://open.qa/docs/#_verify_the_setup" class="external">http://open.qa/docs/#_verify_the_setup</a></li>
<li>Ensure that our salt states ensure all what is needed to run stable multi-machine tests</li>
<li>Add back production worker classes for all affected machines openqaworker1, sapworker{1-7}</li>
</ul>
openQA Tests - action #130826 (Closed): [qem][qe-core]test fails in rmt_feature, SCC API request ...https://progress.opensuse.org/issues/1308262023-06-14T05:28:41Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP1-Server-DVD-Updates-x86_64-qam_rmt@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11340170/modules/rmt_feature/steps/41" class="external">rmt_feature</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</a>. Meant for scheduling rmt tests on QAM Updates</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/11337988" class="external">20230613-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/11322299" class="external">20230612-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=Server-DVD-Updates&machine=64bit&test=qam_rmt&version=15-SP1" class="external">latest</a></p>