openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-08-09T05:43:01ZopenSUSE Project Management Tool
Redmine 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>
openQA Tests - action #107350 (Feedback): [qe-core] test fails in scc_registration in create_hdd_...https://progress.opensuse.org/issues/1073502022-02-23T13:04:22Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Somehows this seems persistent in this test suite even though scc_registration not reachable would sound like a flakiness.</p>
<hr>
<p>openQA test in scenario sle-15-SP4-Online-x86_64-create-hdd-allmodules-allpatterns-gnome@64bit fails in<br>
<a href="https://openqa.suse.de/tests/8211349/modules/scc_registration/steps/6" 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: zluo<br>
create hdd from allmodules+allpatterns gnome</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/8089591" class="external">91.2</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/8037528" class="external">88.4</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=create-hdd-allmodules-allpatterns-gnome&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #107347 (Resolved): [qe-core] test fails in system_rolehttps://progress.opensuse.org/issues/1073472022-02-23T13:02:01Ztjyrinki_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-x86_64-textmode+role_xen@64bit fails in<br>
<a href="https://openqa.suse.de/tests/8216702/modules/system_role/steps/5" class="external">system_role</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>Selects Xen role in System Role window (12SP2+). Select bigger HDD size to resemble more realistic scenario: More place for virtual machines. This is also necessary to enable snapshots based on the installer logic. Related progress issues: <a href="https://progress.opensuse.org/issues/30853" class="external">https://progress.opensuse.org/issues/30853</a></p>
<p>Renamed from textmode+xen_server_role</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/8089629" class="external">91.2</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/8030295" class="external">88.4</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=textmode%2Brole_xen&version=15-SP4" class="external">latest</a></p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<p>AC1: Make the Xen selection work again, a wrong needle was created?</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 #106888 (Resolved): [qe-core] test fails in consoletest_finish in Build 97.1https://progress.opensuse.org/issues/1068882022-02-16T09:14:18Ztjyrinki_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-Full-x86_64-gnome+proxy_SCC+allmodules@64bit fails in<br>
<a href="https://openqa.suse.de/tests/8149494/modules/consoletest_finish/steps/14" class="external">consoletest_finish</a> - in Build 97.1 Functional</p>
<p>This was originally reported from:</p>
<p><a href="https://openqa.suse.de/tests/8173543#step/consoletest_finish/12" class="external">https://openqa.suse.de/tests/8173543#step/consoletest_finish/12</a> and its retries<br>
, and it is "currently blocking our Staging acceptance".</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>. Maintainers: QE Core, jrauch<br>
Install all module which are available through ProxySCC<br>
Install as patterns during installation.</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/8149494" class="external">97.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/8124852" class="external">95.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=x86_64&distri=sle&flavor=Full&machine=64bit&test=gnome%2Bproxy_SCC%2Ballmodules&version=15-SP4" class="external">latest</a></p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<p>AC1: Test finishing both in Functional and Staging.</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 #94829 (New): [qe-core] Web/app serving end-to-end scenariohttps://progress.opensuse.org/issues/948292021-06-29T06:15:22Ztjyrinki_susetjyrinki+redmine@suse.de
<p>A test case for a theoretical app server running inside a Kubernetes cluster, serving clients.</p>
<p>Ideas/examples about possible implementation details:</p>
<ul>
<li>Rancher K3S for the server <a href="https://rancher.com/docs/rancher/v2.5/en/installation/resources/k8s-tutorials/ha-with-external-db/" class="external">https://rancher.com/docs/rancher/v2.5/en/installation/resources/k8s-tutorials/ha-with-external-db/</a></li>
<li>NodeJS 14 LTS serving either http directly or from behind nginx proxy
<ul>
<li>From SLE repositories where available, or <a href="https://nodejs.org/en/download/package-manager/#opensuse-and-sle" class="external">https://nodejs.org/en/download/package-manager/#opensuse-and-sle</a></li>
</ul></li>
<li>For client, one could use something like minimal containers running multiple (tens of?) httperf in a local network. If SUSE containers not minimal enough, maybe for example docker alpine:3.13.5. One can balance between the number of containers and number of threads within.</li>
</ul>
<p>Try not to overlap eg with what QE Performance is testing, see eg "database/http traffic" tests and others.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>Runs a simple https server (self-signed certificate) inside a single node Kubernetes</li>
<li>Each client connecting to it uses https (ignoring self-signed certificate)</li>
<li>The clients altogether doing at least hundreds of requests per second.</li>
<li>Runs for minimum 1 hour</li>
<li>Runs on at minimum 15-SP2, 15-SP3, Tumbleweed, Leap 15.3 and SLE12 if possible without extra effort</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 #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>