openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-10-27T06:00:25ZopenSUSE Project Management Tool
Redmine openQA Project - action #119467 (Resolved): "Internal server error" on opening any job group fron...https://progress.opensuse.org/issues/1194672022-10-27T06:00:25Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Build specific pages etc work, but job group front page like <a href="https://openqa.suse.de/group_overview/268" class="external">https://openqa.suse.de/group_overview/268</a> does not.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> No obvious related regression on OSD</li>
<li><strong>AC2:</strong> Test coverage for the branding button code exists for both the job comments as well as job group comments</li>
</ul>
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 #94441 (Resolved): [qe-core] Re-schedule pidgin testshttps://progress.opensuse.org/issues/944412021-06-22T05:37:00Ztjyrinki_susetjyrinki+redmine@suse.de
<p>These were disabled due to <a href="https://progress.opensuse.org/issues/94177" class="external">https://progress.opensuse.org/issues/94177</a> and blocking many updates.</p>
<p>However, it turns out pidgin is still part of even SLE 15 WE, so it's a good idea to consider fixing the test too.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<p>AC1: Schedule pidgin tests - this time via YAML - on functional + maintenance releases.<br>
AC2: Before enabling, fix any problems that may still remain - likely useful to switch to irc.libera.chat if not yet done.</p>
openQA Tests - action #93321 (Resolved): [qe-core] Add vsftpd test to Tumbleweedhttps://progress.opensuse.org/issues/933212021-06-01T07:52:21Ztjyrinki_susetjyrinki+redmine@suse.de
<p>Note: this ticket is with New status, and would need history explanation why vsftpd is in sle_tests only.</p>
<p>Add the following tests in Tumbleweed testing:</p>
<pre><code>tests/console/vsftpd.pm
</code></pre>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>AC1 The tests are scheduled under extra_tests_textmode test suite under <a href="https://openqa.opensuse.org/group_overview/1" class="external">https://openqa.opensuse.org/group_overview/1</a> job group</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 - action #92215 (Resolved): [qe-core] Change mysql tests to mariadb integration testshttps://progress.opensuse.org/issues/922152021-05-06T08:54:11Ztjyrinki_susetjyrinki+redmine@suse.de
<p>We mainly cover Mariadb in two places:</p>
<p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/console/mysql_odbc.pm" class="external">tests/console/mysql_odbc</a><br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/console/mysql_srv.pm" class="external">tests/console/mysql_srv</a></p>
<p><a href="https://openqa.suse.de/tests/overview?arch=&machine=&modules=mysql_srv&distri=sle&version=15-SP3&build=183.1&groupid=110" class="external">https://openqa.suse.de/tests/overview?arch=&machine=&modules=mysql_srv&distri=sle&version=15-SP3&build=183.1&groupid=110</a><br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/search?p=3&q=console%2F%2Amysql" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/search?p=3&q=console%2F%2Amysql</a></p>
<p>See parent task for more information.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<p>AC1: mysql test modules are renamed to "mariadb" and mariadb tests are scheduled in the products where mariadb is shipping<br>
AC2: mysql references are renamed to mariadb where applicable</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 #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 #91181 (Resolved): [qe-core] Add existing console QEM tests to Product QEhttps://progress.opensuse.org/issues/911812021-04-15T06:16:21Ztjyrinki_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 after release and could be used also before the release (QEM -> product QE)</p>
<p>tests/console/bind.pm<br>
tests/console/dracut_enhanced.pm<br>
tests/console/gd.pm<br>
tests/console/iotop.pm<br>
tests/console/journalctlLevels.pm<br>
tests/console/krb5.pm<br>
tests/console/libgcrypt.pm<br>
tests/console/libssh.pm<br>
tests/console/openssl_nodejs.pm<br>
tests/console/perf.pm<br>
tests/console/rsync_client.pm<br>
tests/console/rsync_server.pm<br>
tests/console/systemd_rpm_macros.pm<br>
tests/console/valgrind.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>
openQA Tests - action #90329 (Resolved): [qe-core] 15SP2 QU - test fails in raid_gpt on ppc64lehttps://progress.opensuse.org/issues/903292021-03-19T09:14:39Ztjyrinki_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-RAID0@ppc64le-no-tmpfs fails in<br>
<a href="https://openqa.suse.de/tests/5696096/modules/raid_gpt/steps/99" class="external">raid_gpt</a></p>
<p>This used to work earlier, now complains about "select at least two devices" so something has changed. Whether it's a test issue (this ticket) or product bug (to be filed if investigation shows that) is to be seen.</p>
<p>These steps look equal so I'm not sure why it fails:<br>
fail: <a href="https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Full-QR&machine=ppc64le-no-tmpfs&test=RAID0&version=15-SP2#step/raid_gpt/96" class="external">https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Full-QR&machine=ppc64le-no-tmpfs&test=RAID0&version=15-SP2#step/raid_gpt/96</a><br>
pass: <a href="https://openqa.suse.de/tests/5446298#step/raid_gpt/96" class="external">https://openqa.suse.de/tests/5446298#step/raid_gpt/96</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: slindomansilla, jrauch</p>
<p>Installation of RAID0 using expert partitioner</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/5653559" class="external">383.6</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/5446298" class="external">383.6</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=Full-QR&machine=ppc64le-no-tmpfs&test=RAID0&version=15-SP2" class="external">latest</a></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 #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>