openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-15T07:34:18ZopenSUSE Project Management Tool
Redmine openQA Tests - action #157306 (Workable): [security][QU] seahorse_sshkey fails to enable WE exten...https://progress.opensuse.org/issues/1573062024-03-15T07:34:18Ztjyrinki_susetjyrinki+redmine@suse.de
<p>openQA test in scenario sle-15-SP5-Online-QR-x86_64-fips_env_mode_tests_crypt_x11@64bit fails in<br>
<a href="https://openqa.suse.de/tests/13708414/modules/seahorse_sshkey/steps/18" class="external">seahorse_sshkey</a></p>
<p>This was earlier attributed to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1217071" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1217071</a> but it has been reportedly fixed also in 15-SP5 now.</p>
openQA Tests - action #156658 (Feedback): [security][QU] audit_remote_libvirt fails in 15-SP5 due...https://progress.opensuse.org/issues/1566582024-03-05T12:43:14Ztjyrinki_susetjyrinki+redmine@suse.de
<p>This seems similar to ticket <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: [security][15-SP6] Update test audit_remote_libvirt for new libvirt behaviour (Resolved)" href="https://progress.opensuse.org/issues/137627">#137627</a> which was at the time only done for 15-SP6.</p>
<p>openQA test in scenario sle-15-SP5-Online-QR-x86_64-cc_audit-remote-libvirt@64bit fails in<br>
<a href="https://openqa.suse.de/tests/13708530/modules/audit_remote_libvirt/steps/13" class="external">audit_remote_libvirt</a></p>
<p>Last good: <a href="https://openqa.suse.de/tests/13102161" class="external">127.10</a> (or more recent)</p>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online-QR&machine=64bit&test=cc_audit-remote-libvirt&version=15-SP5" class="external">latest</a></p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Fix audit_remove_libvirt to pass also on 15-SP5.</li>
</ol>
openQA Tests - action #152897 (Feedback): [security][qu] SCC_REGCODE_LIVE not defined in QU test ...https://progress.opensuse.org/issues/1528972023-12-22T11:48:20Ztjyrinki_susetjyrinki+redmine@suse.de
<p>openQA test in scenario sle-15-SP5-Online-QR-x86_64-fips_ker_mode_tests_crypt_tool@64bit fails in<br>
<a href="https://openqa.suse.de/tests/13123377/modules/suseconnect/steps/3" class="external">suseconnect</a></p>
<p>The new suseconnect test module needs SCC_REGCODE_LIVE, but for some reason this is not defined in QU. This is likely to be fixed in medium types settings.</p>
<p>The variable is included in 15-SP6 (<a href="https://openqa.suse.de/tests/13085715#" class="external">https://openqa.suse.de/tests/13085715#</a>) and maintenance (<a href="https://openqa.suse.de/tests/13134299#" class="external">https://openqa.suse.de/tests/13134299#</a>), and in those cases the module passes.</p>
openQA Tests - action #152671 (Blocked): [security][slem] dirmngr_setup and dirmngr_daemon need t...https://progress.opensuse.org/issues/1526712023-12-15T09:49:55Ztjyrinki_susetjyrinki+redmine@suse.de
<p>dirmngr_setup tries to use zypper so likely misses ALP compatibility, possibly completely (not just is_slemicro >= 6.0 but also is_alp in general missing).</p>
<p>We have not yet executed this same test module on Dolomite.</p>
<p>openQA test in scenario sle-micro-6.0-Default-x86_64-fips_ker_mode_tests_crypt_core@uefi fails in<br>
<a href="https://openqa.suse.de/tests/13062087/modules/dirmngr_setup/steps/25" class="external">dirmngr_setup</a></p>
openQA Tests - action #133766 (Blocked): [security][QU] selinux test fails in audit2allow on both...https://progress.opensuse.org/issues/1337662023-08-03T13:24:13Ztjyrinki_susetjyrinki+redmine@suse.de
<p>In 15-SP5 QU:</p>
<p>openQA test in scenario sle-15-SP5-Online-QR-x86_64-selinux@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11730010/modules/audit2allow/steps/20" class="external">audit2allow</a></p>
<p>This started happening in 15-SP4 already, but has not happened always:</p>
<p>openQA test in scenario sle-15-SP4-Online-QR-x86_64-selinux@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11624079/modules/audit2allow/steps/20" class="external">audit2allow</a></p>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/11575626" class="external">191.4</a></p>
<p>Last good: <a href="https://openqa.suse.de/tests/11052257" class="external">190.2</a> (or more recent)</p>
<p>(15-SP5) Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online-QR&machine=64bit&test=selinux&version=15-SP5" class="external">latest</a></p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Find out what is going wrong, is it a product change between SP4 190.2 and 191.4 builds, or something in tests that changed?</li>
<li>Adjust the test suitably (or file a product bug), and test on 15-SP5 (15-SP4 not needed since no new QUs there)</li>
</ol>
openQA Project - action #127238 (New): It's not possible to remove own force_result comments, and...https://progress.opensuse.org/issues/1272382023-04-05T06:42:05Ztjyrinki_susetjyrinki+redmine@suse.de
<p>Here is an example:</p>
<p><a href="https://openqa.suse.de/tests/10848924#comments" class="external">https://openqa.suse.de/tests/10848924#comments</a></p>
<p>The soft-fail forcing was done erronously, and would be wanted to be removed. However, when trying to remove the comment Forbidden message is given to the person who made the comment (the person is also Administrator).</p>
<p>This ticket looks like opposite of ticket <a class="issue tracker-4 status-1 priority-3 priority-lowest" title="action: It's possible to delete force_result comments (New)" href="https://progress.opensuse.org/issues/107239">#107239</a>, so I'm not sure what to do. However, in the recent months it feels there has been more related changes - now these un-deletable comments are also carried over automatically to new runs, and those carried over comments are also undeletable. If this kind of comment would happen in maintenance tests and couldn't be corrected (without availability of someone who has more direct rights than even Administrator has), it could mean even accidentally giving green light to an erronous update if the correction would be delayed.</p>
openQA Tests - action #124931 (Resolved): [security][QU] 15-SP4 fips_install_lvm_encrypt_seprate_...https://progress.opensuse.org/issues/1249312023-02-22T10:05:07Ztjyrinki_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-x86_64-fips_install_lvm_encrypt_separate_boot@64bit fails in<br>
<a href="https://openqa.suse.de/tests/10551434/modules/first_boot/steps/9" class="external">first_boot</a> (Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online-QR&machine=64bit&test=fips_install_lvm_encrypt_separate_boot&version=15-SP4" class="external">latest</a>) Last good: <a href="https://openqa.suse.de/tests/9997617" class="external">171.2</a> (or more recent)</p>
<p>This is likely due to the changes by YaM (YaST) team.</p>
qe-yam - action #99159 (Closed): 15-SP3 QU minimal+proxy_SCC-postreg_SUSEconnect is not correctly...https://progress.opensuse.org/issues/991592021-09-24T05:50:28Ztjyrinki_susetjyrinki+redmine@suse.de
<p>See eg <a href="https://openqa.suse.de/tests/7196920" class="external">https://openqa.suse.de/tests/7196920</a></p>
<p>This has never passed in QU but was recently added for the Full media and sounds like a good idea to test. As it's a new test from QU perspective, it's not a blocker for QU validation though.</p>
qe-yam - action #98811 (Closed): 15-SP3 QU1 test fails in validate_multipath - topology changedhttps://progress.opensuse.org/issues/988112021-09-17T08:12:35Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>It seems the topology was changed, there's now new 200G section which is not accepted. Is this due to <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/2856ff3dbd71bfb8f36eaa8c29086f1d67f6d17f" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/2856ff3dbd71bfb8f36eaa8c29086f1d67f6d17f</a> and something should be done to schedule/qam/QR/15-SP3/zfcp.yaml too?</p>
<p>openQA test in scenario sle-15-SP3-Online-QR-s390x-zfcp@s390x-zfcp fails in<br>
<a href="https://openqa.suse.de/tests/7141435/modules/validate_multipath/steps/25" class="external">validate_multipath</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>. Maintainer: QE Yast, mgriessmeier</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/7141435" class="external">188.16</a> (current job)</p>
<p>topology: <a href="https://openqa.suse.de/tests/7141435#step/validate_multipath/25" class="external">https://openqa.suse.de/tests/7141435#step/validate_multipath/25</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/6872082" class="external">188.15</a> (or more recent)</p>
<p>topology: <a href="https://openqa.suse.de/tests/6872082#step/validate_multipath/23" class="external">https://openqa.suse.de/tests/6872082#step/validate_multipath/23</a></p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online-QR&machine=s390x-zfcp&test=zfcp&version=15-SP3" class="external">latest</a></p>
qe-yam - action #98805 (Closed): Missing schedule qam/QR/15-SP3/ext4\@yast-xen-pv.yamlhttps://progress.opensuse.org/issues/988052021-09-17T07:34:01Ztjyrinki_susetjyrinki+redmine@suse.de
<p>A Quarterly Update test is failing due to a missing schedule: <a href="https://openqa.suse.de/tests/7149299" class="external">https://openqa.suse.de/tests/7149299</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>
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>
openSUSE admin - tickets #80354 (Rejected): ns3.opensuse.org reports wrong IP to meet.opensuse.orghttps://progress.opensuse.org/issues/803542020-11-25T09:58:45Ztjyrinki_susetjyrinki+redmine@suse.de
<p>The new meet.o.o server was put into place, and it's at 195.135.221.174. However, ns3.opensuse.org disagrees and reports 173, which breaks meet.o.o for everyone (unless using direct IP).</p>
<p>Meanwhile, ns2 and ns4 are also down, possibly something to look at as well and verify if they'll eventually agree on the IP of meet.o.o.</p>
<p>-Timo </p>
openQA Tests - action #58673 (Resolved): libqt5_qtbase fails on 15 SP2https://progress.opensuse.org/issues/586732019-10-25T06:31:45Ztjyrinki_susetjyrinki+redmine@suse.de
<p>The new test just merged seems to be working elsewhere but needles fail on 15 SP2.</p>
<p><a href="https://openqa.suse.de/tests/3527794" class="external">https://openqa.suse.de/tests/3527794</a></p>
openQA Project - action #56789 (New): New needles from git repository not working with openqa-clo...https://progress.opensuse.org/issues/567892019-09-11T08:14:09Ztjyrinki_susetjyrinki+redmine@suse.de
<p>Use case:</p>
<p>To be able to test tests in production (openqa.opensuse.org or openqa.suse.de) before merging the needles and tests themselves, since results have proven to vary on those loaded machines compared to local openQA instance or VM.</p>
<p>It is currently working if there are no new needles involved, but this issue describes the problem with custom needles which would be theoretically supported by openqa-clone-custom-git-refspec but not working in practice.</p>
<p>Problem description:</p>
<p>First of all, documentation [1] says "Path to needles subdirectory to use, defaults to "needles" within PRODUCTDIR. Can be a git repository URL, comparable to CASEDIR", and CASEDIR states "for example <a href="mailto:git@github.com">git@github.com</a>:os-autoinst/os-autoinst-distri-opensuse.git#feature/test".</p>
<p>[1] <a href="https://github.com/os-autoinst/os-autoinst/blob/master/doc/backend_vars.asciidoc" class="external">https://github.com/os-autoinst/os-autoinst/blob/master/doc/backend_vars.asciidoc</a></p>
<p>However,</p>
<pre><code>openqa-clone-custom-git-refspec https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8332 https://openqa.opensuse.org/tests/xxxxxxxx --apikey=XXX --apisecret=XXX NEEDLES_DIR=git@github.com:tjyrinki/os-autoinst-needles-opensuse.git#poo-12345
</code></pre>
<p>results in:</p>
<pre><code>Could not create directory '/var/lib/empty/.ssh'.
Host key verification failed.
fatal: Could not read from remote repository.
</code></pre>
<p>Using https instead (NEEDLES_DIR=<a href="https://github.com/tjyrinki/os-autoinst-needles-opensuse.git" class="external">https://github.com/tjyrinki/os-autoinst-needles-opensuse.git</a>) gets one further, but openQA complains about wrong needles location:</p>
<pre><code>init needles from /var/lib/openqa/pool/15/os-autoinst-needles-opensuse
Needle /var/lib/openqa/pool/15/os-autoinst-needles-opensuse/ssh-login-ok-20160813.json is not under project directory /var/lib/openqa/cache/xxx at /usr/lib/os-autoinst/needle.pm line 63.
</code></pre>
<p>Oliver Kurz suggested playing around with the PRODUCTDIR to try to workaround the forbidding use of (correctly checked out) needles dir which I did but it didn't get any better with trying to set that to eg pool/... directories, which also changes on every run.</p>