openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-09-06T18:08:00ZopenSUSE Project Management Tool
Redmine openQA Tests - action #135269 (Rejected): [security] test fails in system_preparehttps://progress.opensuse.org/issues/1352692023-09-06T18:08:00Ztjyrinki_susetjyrinki+redmine@suse.de
<p>openQA test in scenario sle-15-SP4-Server-DVD-Updates-s390x-mru-install-desktop-with-addons@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/11970473/modules/system_prepare/steps/2" class="external">system_prepare</a></p>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/11970473" class="external">20230831-1</a> (current job)<br>
Last good: <a href="https://openqa.suse.de/tests/11942027" class="external">20230829-1</a> (or more recent)</p>
<p>Fails with "ssh: connect to host s390kvm082.suse.de port 22: No route to host".</p>
<p>Likely an infrastructure issue related to the moves, but should be seen if it can be workarounded or if something needs changing due to hardware moves.</p>
openQA Tests - action #134237 (Rejected): [security][ALP] Manual Testing for ALP Dolomite Build 5.6https://progress.opensuse.org/issues/1342372023-08-15T08:20:39Ztjyrinki_susetjyrinki+redmine@suse.de
<p>While openQA automated testing was running already, recently everything broke over there and we should likely do manual testing still of the latest ALP Dolomite build 5.6.</p>
<ul>
<li>Download: <a href="https://download.suse.de/ibs/SUSE:/ALP:/Products:/Dolomite:/1.0:/ToTest/images/ALP-Dolomite.x86_64-1.0-Default-encrypted-Build5.6.raw" class="external">https://download.suse.de/ibs/SUSE:/ALP:/Products:/Dolomite:/1.0:/ToTest/images/ALP-Dolomite.x86_64-1.0-Default-encrypted-Build5.6.raw</a></li>
<li>Documentation: <a href="https://documentation.suse.com/alp/dolomite/html/alp-dolomite/concept-alp-deployment.html" class="external">https://documentation.suse.com/alp/dolomite/html/alp-dolomite/concept-alp-deployment.html</a></li>
</ul>
<p>Steps:</p>
<ul>
<li>Raw image setup with TPM</li>
<li>Fallback to password disk decryption when TPM is removed</li>
<li>Check <code>audit.log</code> for AVC deny</li>
</ul>
<p>See previous similar ticket <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: [security][ALP] Manual Testing for ALP Dolomite Build 2.1 (Resolved)" href="https://progress.opensuse.org/issues/133265">#133265</a></p>
openQA Tests - action #128252 (Rejected): [security] test fails in logs_from_installation_system ...https://progress.opensuse.org/issues/1282522023-04-25T06:55:35Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-QR-s390x-fips_install_lvm_encrypt_separate_boot@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/10959954/modules/logs_from_installation_system/steps/6" class="external">logs_from_installation_system</a></p>
<p>This is an old issue but I don't see an existing ticket for it.</p>
openQA Tests - action #125279 (Rejected): [security] test fails in verify_efi_mok - create_hdd_te...https://progress.opensuse.org/issues/1252792023-03-02T11:51:26Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-QR-aarch64-aarch64_secureboot@aarch64 fails in <a href="https://openqa.suse.de/tests/10609863/modules/verify_efi_mok/steps/101" class="external">verify_efi_mok</a>. Last good: <a href="https://openqa.suse.de/tests/10019854" class="external">172.1</a> (or more recent)</p>
<p><em>Unlike</em> ticket <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: [security] test fails in verify_efi_mok on 15-SP4 QU / aarch64 (Resolved)" href="https://progress.opensuse.org/issues/125264">#125264</a> where it was identified that a passing verify_efi_mok had UEFI_PFLASH_VARS = <a href="mailto:sle-15-SP4-aarch64-172.1-textmode@aarch64-uefi-vars_sb.qcow2">sle-15-SP4-aarch64-172.1-textmode@aarch64-uefi-vars_sb.qcow2</a> but now has UEFI_PFLASH_VARS = /usr/share/qemu/aavmf-aarch64-ms-vars.bin</p>
<p>... <em>drumroll</em> create_hdd_textmode_secureboot@aarch64 has it the other way around - it now has UEFI_PFLASH_VARS <a href="mailto:sle-15-SP4-aarch64-179.1-textmode@aarch64-uefi-vars.qcow2">sle-15-SP4-aarch64-179.1-textmode@aarch64-uefi-vars.qcow2</a> while when also verify_efi_mok worked create_hdd_textmode_secureboot@aarch64 had (<a href="https://openqa.suse.de/tests/9881708#settings" class="external">https://openqa.suse.de/tests/9881708#settings</a>) UEFI_PFLASH_VARS /usr/share/qemu/aavmf-aarch64-ms-vars.bin</p>
<p>This could explain why there seems to be a mismatch between what state the image is when it's created vs what it's later expected to be at.</p>
openQA Tests - action #123682 (Rejected): [security] aarch64 Failed to connect to '/tmp/mytpm12/s...https://progress.opensuse.org/issues/1236822023-01-26T06:05:08Ztjyrinki_susetjyrinki+redmine@suse.de
<p>See <a href="https://openqa.suse.de/tests/10375321" class="external">https://openqa.suse.de/tests/10375321</a> or always the latest at <a href="https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=security_tpm2_swtpm&version=15-SP5" class="external">https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=security_tpm2_swtpm&version=15-SP5</a></p>
<p>Swtpm device is incorrectly defined?</p>
openQA Tests - action #107341 (Rejected): [qe-core] test fails in vnc_two_passwordshttps://progress.opensuse.org/issues/1073412022-02-23T12:54:08Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>A failure in this module is currently linked to a flaky test tracker, but currently the error seems permanent in vnc_two_passwords.</p>
<hr>
<p>openQA test in scenario sle-15-SP4-Online-x86_64-extra_tests_gnome@svirt-xen-hvm fails in<br>
<a href="https://openqa.suse.de/tests/8216688/modules/vnc_two_passwords/steps/23" class="external">vnc_two_passwords</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. Extra tests which were designed to run on gnome , VNC_STALL_THRESHOLD is needed for xen svirt to don't turn off the scrreen after default 4 sec</p>
<p>New version of extra_tests_on_gnome for yaml scheduling</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/7935805" class="external">79.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=svirt-xen-hvm&test=extra_tests_gnome&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #107320 (Rejected): [qe-core] test fails in prepare_test_data - sshd[2171]:...https://progress.opensuse.org/issues/1073202022-02-23T10:10:57Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>ssh connection is consistently dropping between the SUT and openQA at prepare_test_data, preventing further tests. </p>
<p>openQA test in scenario sle-15-SP4-Online-s390x-extra_tests_gnome@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/8207530/modules/prepare_test_data/steps/10" class="external">prepare_test_data</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. Extra tests which were designed to run on gnome , VNC_STALL_THRESHOLD is needed for xen svirt to don't turn off the scrreen after default 4 sec</p>
<p>New version of extra_tests_on_gnome for yaml scheduling</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC:0</strong> Switch the test to use root console to remove the initial failure/urgency</li>
<li><strong>AC:1</strong> Investigate: sshd[2171]: error: kex_exchange_identification: Connection closed by remote host</li>
<li><strong>AC:2</strong> Investigate if this test can be unscheduled. Tests may be able or already are downloading the necessary test data themselves. No need to download unneeded data.</li>
<li><strong>AC:3</strong> Make sure that the ssh console is necessary for s390, given that we have a working serial console</li>
<li><strong>AC:4</strong> Investigate if it is a backend/hardware problem with grenache/s390 machine</li>
<li><strong>AC:5</strong> Investigate if the problem is caused by the choice of <code>user-console</code></li>
</ul>
<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/7618963" class="external">61.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=s390x&distri=sle&flavor=Online&machine=s390x-kvm-sle12&test=extra_tests_gnome&version=15-SP4" class="external">latest</a></p>
qe-yam - action #97289 (Rejected): [qem][qu] test fails in await_install in 15-SP3 QUhttps://progress.opensuse.org/issues/972892021-08-20T08:46:33Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Online-QR-ppc64le-crypt_no_lvm@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/6903766/modules/await_install/steps/3" class="external">await_install</a></p>
<p>This was passing in 188.13 which was before git commit "Fix YaST-related tests in QR Updates for SP3", maybe even if not directly affected something was changed around that time that fixed others but broke this?</p>
<p>It is however passing for aarch64 and x86: <a href="https://openqa.suse.de/tests/6872059" class="external">https://openqa.suse.de/tests/6872059</a> <a href="https://openqa.suse.de/tests/6872114" class="external">https://openqa.suse.de/tests/6872114</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: riafarov. Test installation with encrypted partitions but without lvm enabled. This is supported only by storage-ng, hence, do NOT enable test suite on distris without storage-ng.</p>
<p>(crypt-)LVM installations can take longer, especially on non-x86_64 architectures.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/6641855" class="external">188.14</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/6590507" class="external">188.13</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-QR&machine=ppc64le&test=crypt_no_lvm&version=15-SP3" class="external">latest</a></p>
qe-yam - action #91196 (Rejected): Add existing qe-yast Product QE tests to QEMhttps://progress.opensuse.org/issues/911962021-04-15T06:25:12Ztjyrinki_susetjyrinki+redmine@suse.de
<p>After comparing test coverage of SLE 15 SP2 and SP3 in opneQA I identified several tests that are exclusive to either pre-release or post-release testing and could be easily used to increase our coverage just by using what we already have.</p>
<p>It is possible that are some errors and some of the tests from the list are already being used. It is also just my opinion, therefor review from other colleagues is more then welcome.</p>
<p>These are the YaST tests that run only before release and could be used also after the release (product QE -> QEM)</p>
<p>tests/console/yast2_cmdline.pm<br>
tests/console/yast2_dns_server.pm<br>
tests/console/yast2_kdump.pm<br>
tests/console/yast2_lan_hostname.pm<br>
tests/console/yast2_ntpclient.pm<br>
tests/console/yast2_proxy.pm<br>
tests/console/yast2_rmt.pm<br>
tests/console/yast2_samba.pm<br>
tests/console/yast2_settings.pm<br>
tests/console/yast2_snapper_ncurses.pm<br>
tests/console/yast2_vnc.pm<br>
tests/network/wireguard.pm<br>
tests/security/yast2_apparmor/manually_add_profile.pm<br>
tests/security/yast2_apparmor/scan_audit_logs.pm<br>
tests/security/yast2_apparmor/settings_disable_enable_apparmor.pm<br>
tests/security/yast2_apparmor/settings_toggle_profile_mode.pm<br>
tests/security/yast2_users/add_users.pm</p>
openQA Tests - action #91184 (Rejected): [qe-core] Add existing network QEM tests to Product QEhttps://progress.opensuse.org/issues/911842021-04-15T06:17:20Ztjyrinki_susetjyrinki+redmine@suse.de
<p>After comparing test coverage of SLE 15 SP2 and SP3 in opneQA I identified several tests that are exclusive to either pre-release or post-release testing and could be easily used to increase our coverage just by using what we already have.</p>
<p>It is possible that are some errors and some of the tests from the list are already being used. It is also just my opinion, therefor review from other colleagues is more then welcome.</p>
<p>These are the tests that run only after release and could be used also before the release (QEM -> product QE)</p>
<p>tests/network/autofs_client.pm & tests/network/autofs_server.pm<br>
tests/network/salt_master.pm<br>
tests/network/salt_minion.pm<br>
tests/network/samba/samba_adcli.pm</p>
openQA Tests - action #91178 (Rejected): [kernel-default][qem] Add existing kernel Product QE tes...https://progress.opensuse.org/issues/911782021-04-15T06:14:00Ztjyrinki_susetjyrinki+redmine@suse.de
<p>After comparing test coverage of SLE 15 SP2 and SP3 in opneQA I identified several tests that are exclusive to either pre-release or post-release testing and could be easily used to increase our coverage just by using what we already have.</p>
<p>It is possible that are some errors and some of the tests from the list are already being used. It is also just my opinion, therefor review from other colleagues is more then welcome.</p>
<p>These are the kernel tests that run only before release and could be used also after the release (product QE -> QEM)</p>
<p>tests/kernel/blktests.pm<br>
tests/kernel/kdump.pm<br>
tests/kernel/numa_irqbalance.pm<br>
tests/kernel/pressure_stall_information.pm<br>
tests/kernel/tuned.pm</p>
qe-yam - action #91175 (Rejected): [qe-yast][qem] Add existing Product QE tests to QEMhttps://progress.opensuse.org/issues/911752021-04-15T06:11:54Ztjyrinki_susetjyrinki+redmine@suse.de
<p>After comparing test coverage of SLE 15 SP2 and SP3 in opneQA I identified several tests that are exclusive to either pre-release or post-release testing and could be easily used to increase our coverage just by using what we already have.</p>
<p>It is possible that are some errors and some of the tests from the list are already being used. It is also just my opinion, therefor review from other colleagues is more then welcome.</p>
<p>These are the YaST tests that run only before release and could be used also after the release (product QE -> QEM)</p>
<p>tests/console/vsftpd.pm<br>
tests/console/yast2_cmdline.pm<br>
tests/console/yast2_dns_server.pm<br>
tests/console/yast2_kdump.pm<br>
tests/console/yast2_lan_hostname.pm<br>
tests/console/yast2_ntpclient.pm<br>
tests/console/yast2_proxy.pm<br>
tests/console/yast2_rmt.pm<br>
tests/console/yast2_samba.pm<br>
tests/console/yast2_settings.pm<br>
tests/console/yast2_snapper_ncurses.pm<br>
tests/console/yast2_vnc.pm<br>
tests/security/yast2_apparmor/manually_add_profile.pm<br>
tests/security/yast2_apparmor/scan_audit_logs.pm<br>
tests/security/yast2_apparmor/settings_disable_enable_apparmor.pm<br>
tests/security/yast2_apparmor/settings_toggle_profile_mode.pm<br>
tests/security/yast2_users/add_users.pm</p>
qe-yam - action #91172 (Rejected): Add existing QEM YaST tests to Product QEhttps://progress.opensuse.org/issues/911722021-04-15T06:10:09Ztjyrinki_susetjyrinki+redmine@suse.de
<p>After comparing test coverage of SLE 15 SP2 and SP3 in opneQA I identified several tests that are exclusive to either pre-release or post-release testing and could be easily used to increase our coverage just by using what we already have.</p>
<p>It is possible that are some errors and some of the tests from the list are already being used. It is also just my opinion, therefor review from other colleagues is more then welcome.</p>
<p>These are the YaST tests that run only after release and could be used also before the release (QEM -> product QE)</p>
<p>tests/console/yast2_registration.pm<br>
tests/yast2_gui/yast2_instserver.pm<br>
tests/yast2_gui/yast2_keyboard.pm<br>
tests/yast2_gui/yast2_storage_ng.pm</p>
qe-yam - action #87716 (Rejected): [qem][QU] test fails in scc_registration (Full image)https://progress.opensuse.org/issues/877162021-01-13T15:58:33Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Full-QR-s390x-zfcp@s390x-zfcp fails in<br>
<a href="https://openqa.suse.de/tests/5259306/modules/scc_registration/steps/5" class="external">scc_registration</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: mgriessmeier, okurz</p>
<p>Installation-only test configuring an s390x ZFCP storage.</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/5182066" class="external">376.10</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>This is the first time the test is tried to run on Full images.<br>
Also SP3 Yast tests do not test multipath on Full: <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP3&build=124.5&groupid=129" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP3&build=124.5&groupid=129</a></p>
<p>This task might be for QE Yast to enable zfcp testing on Full images at some point.</p>
<p>This could be also simply unscheduled from Full testing.</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=Full-QR&machine=s390x-zfcp&test=zfcp&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #87713 (Rejected): [qe-yast][qe-core][qem][QU] test fails in scc_registrati...https://progress.opensuse.org/issues/877132021-01-13T15:57:47Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Full-QR-ppc64le-multipath@ppc64le-no-tmpfs fails in<br>
<a href="https://openqa.suse.de/tests/5281463/modules/scc_registration/steps/5" class="external">scc_registration</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: okurz</p>
<p>Test installation on machine with virtual multipath hardware. Only tests succesful detection of multipath and installation. No functional testing of multipath itself.</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/5182046" class="external">376.10</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>See Online-QR's result at: <a href="https://openqa.suse.de/tests/5259394" class="external">https://openqa.suse.de/tests/5259394</a><br>
This is the first time the test is tried to run on Full images.<br>
Also SP3 Yast tests do not test multipath on Full: <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP3&build=124.5&groupid=129" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP3&build=124.5&groupid=129</a></p>
<p>This task might be for QE Yast to enable multipath testing on Full images at some point.</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=Full-QR&machine=ppc64le-no-tmpfs&test=multipath&version=15-SP2" class="external">latest</a></p>