openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-01-30T09:02:49ZopenSUSE Project Management Tool
Redmine openSUSE Release Process - action #154528 (Resolved): [security] Expand journal_check ALP white l...https://progress.opensuse.org/issues/1545282024-01-30T09:02:49Ztjyrinki_susetjyrinki+redmine@suse.de
<p>Check bug_refs.json if there's anything from our side that needs additions if sle-micro 6.0 job group gets journal_check enabled.</p>
openQA Tests - action #134012 (New): [qe-core] Repository QA:/Head/SLE-15-SP6 missinghttps://progress.opensuse.org/issues/1340122023-08-09T05:43:01Ztjyrinki_susetjyrinki+redmine@suse.de
<p>Hello QE Core. Can we request enabling the repository mentioned in the subject, or is there some other path to go for?</p>
<p>See openQA test in scenario sle-15-SP6-Online-x86_64-fips_tests_crypt_openvpn_server@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11769917/modules/openvpn_server/steps/86" class="external">openvpn_server</a> - always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=fips_tests_crypt_openvpn_server&version=15-SP6" class="external">latest</a></p>
<p>"[zypp-core] Exception.cc(log):186 - [qa-head|<a href="http://dist.suse.de/ibs/QA:/Head/SLE-15-SP6" class="external">http://dist.suse.de/ibs/QA:/Head/SLE-15-SP6</a>] Repository type can't be determined."</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 #96842 (Closed): [qe-yast][qu] test fails in new_partitioning_gpt in 15-SP3 QUhttps://progress.opensuse.org/issues/968422021-08-13T13:13:18Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Could you check why this repeatedly fails complaining about bootability? Compare to <a href="https://openqa.suse.de/tests/6590552#step/new_partitioning_gpt/3" class="external">https://openqa.suse.de/tests/6590552#step/new_partitioning_gpt/3</a> in the previous build.</p>
<p>openQA test in scenario sle-15-SP3-Online-QR-x86_64-lvm-encrypt-separate-boot@64bit fails in<br>
<a href="https://openqa.suse.de/tests/6837970/modules/new_partitioning_gpt/steps/4" class="external">new_partitioning_gpt</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Same as lvm-full-encrypt, but with separate boot not encrypted partition, only installation to not repeat everything again with small risk.<br>
Maintainer: riafarov</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/6641890" 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/6590552" 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=x86_64&distri=sle&flavor=Online-QR&machine=64bit&test=lvm-encrypt-separate-boot&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #94832 (New): [qe-core] Development collaboration service automated deploym...https://progress.opensuse.org/issues/948322021-06-29T06:44:38Ztjyrinki_susetjyrinki+redmine@suse.de
<p>A test case for a site with scaling ready development collaboration, including automated deployment and monitoring.</p>
<p>Ideas/examples about implementation details:</p>
<ul>
<li>Rancher/K3S for the Kubernetes solution</li>
<li>Ansible for automated deployment (actual user wouldn't use openQA for deployment)</li>
<li>Monitoring with Grafana</li>
<li>Gitlab for the collaboration service</li>
</ul>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>A default installation target container as the automation target</li>
<li>One-command (like ansible-playbook deploy.yml) deployment once the target is available for the test to use</li>
<li>A development collaboration platform running</li>
<li>Ready to scale outside the initial container</li>
<li>A monitoring solution deployment for the cluster/service status (no need to configure actual alerts, but that the capability is there using a popular software)</li>
</ul>
openQA Tests - action #93210 (New): [migration][qe-core] sssd openldap/389-ds basic testing, modi...https://progress.opensuse.org/issues/932102021-05-28T08:22:13Ztjyrinki_susetjyrinki+redmine@suse.de
<p>In ticket 89479 the goals for QE Core were fulfilled to modernize directory service testing. However, QE Migration would also like to test sssd with openldap (older SLE) and 389-ds (newer SLE) and testing how the functionality remains after upgrade to newer SLE.</p>
<p>There is a draft design for such tests at <a href="https://confluence.suse.com/display/qasleapac1/Draft+service+check+design+and+implementation" class="external">https://confluence.suse.com/display/qasleapac1/Draft+service+check+design+and+implementation</a> - once there it is fully agreed that we want to go ahead with such architecture, this test, which is probably one of the more important migration tests, should be modified towards that. Whether done by people from QE Core or QE Migration is likely depending on a resource issue, now that developer of 89479 is moving to yet another squad. Community contribution would be of course always welcome as well, although for that the design plan should be incorporated to this ticket. tl;dr; divide the test to 1. install_service, 2. configure_service, 3. enable_service, 4. start_service, 5. check_service, 6. check_function, of which 1-6 are done before distro upgrade and 5-6 after. Maybe it could be possibly to do just division to two steps, and execute either both or just the latter? Ticket will be updated once the draft solidifies.</p>
<a name="Further-Information"></a>
<h2 >Further Information<a href="#Further-Information" class="wiki-anchor">¶</a></h2>
<p>See discussion at <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12528" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12528</a> and <a href="https://progress.opensuse.org/issues/89479" class="external">https://progress.opensuse.org/issues/89479</a></p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<p>AC1: Modify test so that it continues to execute as is, but is split so that distro upgrade (migration) tests can be also run using the same module.</p>
openQA Tests - coordination #91193 (New): [epic][qe-core][qem] Add existing console Product QE te...https://progress.opensuse.org/issues/911932021-04-15T06:23:53Ztjyrinki_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 console tests that run only before release and could be used also after the release (product QE -> QEM)</p>
<p><del>tests/console/btrfsmaintenance.pm (runs on mau-filesystem)</del><br>
<del>tests/console/journald_fss.pm</del><br>
<del>tests/console/lvm_thin_check.pm</del><br>
tests/console/ndctl.pm<br>
<del>tests/console/network_hostname.pm</del><br>
tests/console/nvme_checks.pm<br>
<del>tests/console/openvswitch_ssl.pm</del><br>
tests/console/snapper_cleanup_timeline.pm<br>
tests/console/systemd_nspawn.pm<br>
tests/console/verify_default_target.pm<br>
tests/console/verify_network.pm<br>
<del>tests/console/vsftpd.pm</del></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong> All aforementioned tests are scheduled in maintenance tests (aggregated or incidents), in their corresponding categories (When in doubt ask in qe-core channel)</li>
<li><strong>AC2</strong> Cross reference with <a href="https://github.com/ge0r/openQA-module-mapper" class="external">openqa-module-mapper</a> to figure what's already done and what's running where.</li>
<li><strong>AC3</strong> If a test module needs black magic to work (i.e, takes more than half a day), a corresponding ticket is created and it is removed from this list.</li>
</ul>
openQA Tests - action #91190 (New): [kernel][qem] Add existing btrfs-progs Product QE tests to QEMhttps://progress.opensuse.org/issues/911902021-04-15T06:23:06Ztjyrinki_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 btrfs-progs tests that run only before release and could be used also after the release (product QE -> QEM)</p>
<p>tests/btrfs-progs/generate_report.pm<br>
tests/btrfs-progs/install.pm<br>
tests/btrfs-progs/run.pm</p>
openQA Tests - action #91187 (Resolved): [qe-core] Add existing tomcat test module to Product QE ...https://progress.opensuse.org/issues/911872021-04-15T06:17:58Ztjyrinki_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 X11 tests that run only after release and could be used also before the release (QEM -> product QE)</p>
<p>tests/x11/piglit/piglit.pm<br>
tests/x11/tomcat.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>
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>
qe-yam - action #80244 (Closed): [qam] setup_libyui fails on aarch64 on 15SP1https://progress.opensuse.org/issues/802442020-11-24T07:33:04Ztjyrinki_susetjyrinki+redmine@suse.de
<p>Commit b391b84490214cfd27387353a5bd18fba1d8e2fe (Adjust qemu backend scheduled for RAID0/1/5/6/10 scenarios) added setup_libyui which fails on 15SP1 on aarch64:</p>
<p><a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=47.3&groupid=249" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=47.3&groupid=249</a></p>
<p><a href="https://openqa.suse.de/tests/5060842" class="external">https://openqa.suse.de/tests/5060842</a></p>
<p>The test is part of the QU5 validation being done today.</p>
<p>Note: There is no more QUs to 15SP1 after QU5, possibly finalized today, so this ticket is more for information. Trying to run with customs schedule now.</p>
openQA Tests - action #57584 (Resolved): [qam] test fails in evolution_setup_servers - dovecot n...https://progress.opensuse.org/issues/575842019-10-01T11:52:32Ztjyrinki_susetjyrinki+redmine@suse.de
<p>After <a href="https://progress.opensuse.org/issues/56273" class="external">https://progress.opensuse.org/issues/56273</a> got fixed, the evolution_setup_servers is now failing, a rerun done first at <a href="https://openqa.suse.de/tests/3397700" class="external">https://openqa.suse.de/tests/3397700</a> and a newer one at <a href="https://openqa.suse.de/tests/3424806" class="external">https://openqa.suse.de/tests/3424806</a></p>
<p>"No provider of 'dovecot' found." at <a href="https://openqa.suse.de/tests/3397700#step/evolution_prepare_servers/18" class="external">https://openqa.suse.de/tests/3397700#step/evolution_prepare_servers/18</a></p>
<p>qam-regression-message is currently disabled, <a href="https://progress.opensuse.org/issues/57260" class="external">https://progress.opensuse.org/issues/57260</a> is about re-enabling it once the issues are all fixed.</p>
openQA Tests - action #50867 (Resolved): [qam] nfsidmap part of the autofs tests fail on SLE12https://progress.opensuse.org/issues/508672019-04-30T07:30:08Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<pre><code class="bash syntaxhl" data-language="bash">nfsidmap <span class="nt">-c</span>
<span class="s1">'id_resolver'</span> keyring was not found
</code></pre>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<ul>
<li>Build <a href="https://openqa.suse.de/tests/2844872#step/autofs_client/39" class="external">20190430</a>
In scenario sle-12-SP3-Server-DVD-Updates-x86_64-1-mau-autofs-server@64bit</li>
</ul>
<a name="Expected-results"></a>
<h2 >Expected results<a href="#Expected-results" class="wiki-anchor">¶</a></h2>
<p>I cannot find any expected result in OSD, so I consider this a new test.</p>
<a name="Further-information"></a>
<h2 >Further information<a href="#Further-information" class="wiki-anchor">¶</a></h2>
<p>Latest job in this scenario: <a href="https://openqa.suse.de/tests/latest?test=mau-autofs-server&flavor=Server-DVD-Updates&arch=x86_64&distri=sle&version=12-SP3&machine=64bit" class="external">https://openqa.suse.de/tests/latest?test=mau-autofs-server&flavor=Server-DVD-Updates&arch=x86_64&distri=sle&version=12-SP3&machine=64bit</a></p>