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 #157963 (In Progress): [qe-core][ppc64le][s390x]test fails in libgit2, we c...https://progress.opensuse.org/issues/1579632024-03-26T06:50:00Zrfan1richard.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-extra_tests_textmode@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/13872419/modules/libgit2/steps/60" class="external">libgit2</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, asmorodskyi,dheidler. Mainly console extratest </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/13846513" class="external">71.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/13828608" 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=extra_tests_textmode&version=15-SP6" class="external">latest</a></p>
openQA Tests - action #157960 (In Progress): [qe-core][qem]test fails in krb5 [sporadic issue, so...https://progress.opensuse.org/issues/1579602024-03-26T06:41:45Zrfan1richard.fan@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-aarch64-mau-extratests1@aarch64-virtio fails in<br>
<a href="https://openqa.suse.de/tests/13872578/modules/krb5/steps/78" class="external">krb5</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>. Run console tests against aggregated test repo</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/13870364" class="external">20240325-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/13854553" class="external">20240324-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=aarch64&distri=sle&flavor=Server-DVD-Updates&machine=aarch64-virtio&test=mau-extratests1&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #157957 (New): [qe-core][functional] job setting is wrong for test 'minimal...https://progress.opensuse.org/issues/1579572024-03-26T06:36:53Zrfan1richard.fan@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.suse.de/tests/13849145" class="external">https://openqa.suse.de/tests/13849145</a></p>
<p>Reason: asset failure: Failed to download <a href="mailto:SLES-15-SP6-ppc64le-71.1@ppc64le-spvm-unregistered.qcow2">SLES-15-SP6-ppc64le-71.1@ppc64le-spvm-unregistered.qcow2</a> to /var/lib/openqa/cache/openqa.suse.de/<a href="mailto:SLES-15-SP6-ppc64le-71.1@ppc64le-spvm-unregistered.qcow2">SLES-15-SP6-ppc64le-71.1@ppc64le-spvm-unregistered.qcow2</a></p>
<p>For powerVM setup, there is no qcow2 image can be re-used, so we may need to adjust our job settings</p>
<a name="Action-items"></a>
<h2 >Action items<a href="#Action-items" class="wiki-anchor">¶</a></h2>
<ol>
<li>check the parent job and make sure they are using the same <code>machine type</code></li>
<li>remove the 'HDD_1' job setting [or change the machine type to ppc64le]</li>
</ol>
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 Tests - action #157876 (In Progress): [qe-core][leap 15.6]test fails in orphaned_packages_...https://progress.opensuse.org/issues/1578762024-03-25T11:35:07Zrfan1richard.fan@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario opensuse-15.6-DVD-Backports-Incidents-x86_64-install_with_updates_kde@uefi-2G fails in<br>
<a href="https://openqa.opensuse.org/tests/4036510/modules/orphaned_packages_check/steps/15" class="external">orphaned_packages_check</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/4011543" class="external">20240314-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/4009232" class="external">20240313-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-Backports-Incidents&machine=uefi-2G&test=install_with_updates_kde&version=15.6" 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 #156004 (New): [qe-core]test fails in desktop_mainmenu, it might be caused ...https://progress.opensuse.org/issues/1560042024-02-26T02:21:01Zrfan1richard.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-we-module@64bit-2gbram fails in<br>
<a href="https://openqa.suse.de/tests/13582505/modules/desktop_mainmenu/steps/3" class="external">desktop_mainmenu</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>Execute WE-related tests on SLE15 installations with WE module enabled (for products earlier than SLE15, the scenarios are we, we-ftp, we-http).</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/13241344" class="external">46.40</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-2gbram&test=we-module&version=15-SP6" class="external">latest</a></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 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 #129083 (Workable): [qem][qe-core] Enhance firewall zones/services configur...https://progress.opensuse.org/issues/1290832023-05-11T03:02:45Zrfan1richard.fan@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>We may need to make sure the system installed via autoyast can get the same firewall configuration as we do with interactive installation.<br>
However, currently we are maintaining a single configuration file for each sle15/sle12 platform. </p>
<p>So I will try to do some enhancement to current autoyast template file. But we may need to do enough VRs to make sure the changes don't introduce new issues.</p>
<a name="Action-items"></a>
<h2 >Action items<a href="#Action-items" class="wiki-anchor">¶</a></h2>
<ol>
<li>Current firewall configuration seems fine, but we may consider the service <code>ssh</code> and port <code>22</code> due to different requirements on each platform
[for s390x and powerVM, we need unblock it due to remote worker access needs ssh port open]</li>
<li>Use as few lines as we can to define firewall, then we can get default firewall setting [the same configuration as we do via interactive install]</li>
<li>Don't change the default firewall behavior as interactive installation, that will cause problems and will miss test coverage.</li>
</ol>
openQA Tests - action #115079 (New): [qe-core][qem&functional] Many test failures due to low perf...https://progress.opensuse.org/issues/1150792022-08-08T01:49:38Zrfan1richard.fan@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>In past few weeks, I have hit many sporadic (but very frequent) issues which we have to restart them several time to make them pass.<br>
Most of these issues can only be seen on aarch64 platform, and work fine on x86_64 and s390x based on openQA's test results.</p>
<a name="What-issue-we-have-seen"></a>
<h2 >What issue we have seen<a href="#What-issue-we-have-seen" class="wiki-anchor">¶</a></h2>
<ul>
<li>Tests reach the max job time limit, that means the tests need more time than x86_64 and s390x</li>
<li>"Send_key" operation doesn't work fine or can't get response even with some retry logic there</li>
<li>"script_run" command needs more time to get return code on aarch64 platform, especially scrap logs within serial console </li>
<li>For some installation tests, "QEMURAM=1024" fail can be seen very often, but no such issue with x86_64 and s390x</li>
</ul>
<a name="Current-workaroundsfixes"></a>
<h2 >Current workarounds/fixes<a href="#Current-workaroundsfixes" class="wiki-anchor">¶</a></h2>
<ul>
<li>Increase the resource for each job [used to increase memory size]</li>
<li>Increase timeout value for the scripts</li>
<li>Remove some test modules which don't impact the test function but often fail with perf issues</li>
<li>Add some re-try logic for the commands within the test scripts</li>
</ul>
<a name="Expected-results"></a>
<h2 >Expected results<a href="#Expected-results" class="wiki-anchor">¶</a></h2>
<p>I don't know if low performance issue is expected on aarch64 platform. however, we may have to handle these failures during the daily openQA review.<br>
My personal suggestions are:</p>
<ol>
<li>Order new arm workers with higher performance [e.g. new CPU modules/high speed storage]</li>
<li>Check with kernel team/performance team to see if we can have some fixes/patches to fix the performance issue on aarch64 platform.</li>
</ol>
openQA Project - action #110229 (New): [tools][qemu] Managing device boot order with bootindexhttps://progress.opensuse.org/issues/1102292022-04-24T12:39:11Zrfan1richard.fan@suse.com
<p>Hello tool team experts,</p>
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>Can I ask for your kindly help to see if we can set boot order for VMs with qemu backend?</p>
<p>We used to set bootindex=0 for disk or cdrom, but I don't know if we can set the boot order for different devices with bootindex proertity.</p>
<p>For example, I need set:</p>
<p>DISK->bootindex=0<br>
CDROM->bootindex=1<br>
NET->bootindex=2</p>
<a name="Expect-result"></a>
<h2 >Expect result<a href="#Expect-result" class="wiki-anchor">¶</a></h2>
<p>If we have multiple boot devices, we can set the boot order for them.</p>