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 #157138 (Workable): [security] SLE Micro 6.0 s390x tests do not start (cont...https://progress.opensuse.org/issues/1571382024-03-13T08:21:13Ztjyrinki_susetjyrinki+redmine@suse.de
<p>openQA test in scenario sle-micro-6.0-Base-qcow-s390x-container_selinux@s390x-kvm fails in<br>
<a href="https://openqa.suse.de/tests/13756851/modules/disk_boot/steps/8" class="external">disk_boot</a></p>
<p>This has not been tried to be executed before. It is likely trying to boot with wrong modules and possibly wrong settings, comparison can be done to <a href="https://openqa.suse.de/tests/13756869" class="external">https://openqa.suse.de/tests/13756869</a> which boots the same image successfully.</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>
openQA Tests - action #107956 (New): [qe-core][sporadic][qem] test sometimes fails in ntp_client ...https://progress.opensuse.org/issues/1079562022-03-08T07:22:17Ztjyrinki_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-Server-DVD-Updates-x86_64-mau-extratests-security-fips@64bit fails in<br>
<a href="https://openqa.suse.de/tests/8286663/modules/ntp_client/steps/22" class="external">ntp_client</a></p>
<p>This is part of the FIPS test suite but ntp sounds generid enough for QE Core.</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>.</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/8286663" class="external">20220308-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/8280627" class="external">20220307-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=Server-DVD-Updates&machine=64bit&test=mau-extratests-security-fips&version=15-SP3" class="external">latest</a></p>
openQA Tests - coordination #107770 (New): [qe-core][epic] Create additional Java testinghttps://progress.opensuse.org/issues/1077702022-03-02T07:02:20Ztjyrinki_susetjyrinki+redmine@suse.de
<p>(draft)</p>
<p>Ideas:</p>
<ul>
<li>maven (in addition to current ant)</li>
<li>Compiling a stable but complicated application - this is to detect if an update would modify compilation experience</li>
<li>Other big java software besides tomcat that could be run</li>
</ul>
openQA Tests - coordination #107065 (New): [qe-core][epic] Zypper test planhttps://progress.opensuse.org/issues/1070652022-02-18T08:40:47Ztjyrinki_susetjyrinki+redmine@suse.de
<p>(draft)</p>
<p>Zypper is core to the updating and migrating SLE so it's important to cover in automated testing the variety of how it is used. Repositories are closely intertwiner with zypper, and especially rmt (repository mirroring tool) is of importance. PackageKit is a frontend that uses zypper via libzypp.</p>
<p>On a high level, zypper is used most of all to:</p>
<ul>
<li>Install the packages to the installed system</li>
<li>Install new packages</li>
<li>Upgrade packages</li>
<li>Upgrade (migrate) the whole system</li>
</ul>
<p>Currently QE Core runs the following:</p>
<ul>
<li>Modules zypper_clear_repos zypper_ar zypper_ref zypper_lr zypper_in zypper_log zypper_up zypper_lifecycle zypper_extend orphaned_packages_check (in extra_tests_textmode and mau-extratests-zypper)</li>
<li>Test suite toolchain_zypper installs a build environment but otherwise is mostly about building, not about zypper any more than many other modules</li>
<li>Especially zypper_extend is quite extensive regression tests suite, I think main functions are quite well covered by it and the other modules</li>
<li>Upgrading between Leap major versions in O3</li>
<li>rmt_feature module via qam_rmt</li>
<li>updates_packagekit_gpk</li>
</ul>
<p>Areas uncovered that QE Core could cover in automated tests:</p>
<ul>
<li>Catch new zypper warning messages that might be important - <a href="https://progress.opensuse.org/issues/106916">https://progress.opensuse.org/issues/106916</a></li>
<li>Execute rmt_feature also in Development version</li>
<li>For cleanup purposes, investigate "console/rmt.pm" and either enable using of it for all releases or get rid of it if it's obsoleted by the console/rmt/* - if removing, also remove RMT_TEST and its use (is_rmt) from main_common (nothing seems to specify RMT_TEST but double-check).</li>
<li>Executing the tests but with using the new environment variables that enable different zypper features. At least ZYPP_SINGLE_RPMTRANS=1, possibly also ZYPP_MEDIANETWORK=1 which is another new feature.</li>
<li>Checking Ctrl-C aborting of zypper midway and resuming</li>
<li>gnome-software - but this is low priority because of SUSE having next to no desktop business compared to Red Hat or Ubuntu</li>
</ul>
<p>Other squads cover:</p>
<ul>
<li>QE Yast tests zypper_in/zypper_lr/zypper_lifecycle/zypper_ref/zypper_log/zypper_clear_repos during install time and has a module yast2_rmt</li>
<li>QE SAP tests zypper in online migration / zypper patch</li>
<li>QE Migration tests migrations between SLE major versions (currently does not cover Leap, so it's left to Core for time being), and executes the same zypper tests as Yast and SAP together, and for rmt modules rmt_feature, rmt_export, rmt_chinese, rmt_host_migration, rmt_import</li>
<li>JeOS tests the same zypper tests as others, including zypper_extend</li>
<li>In openSUSE there's also updates_packagekit_kde</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 #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 #94090 (New): [qe-core][qac][study] End-to-end combination test scenarioshttps://progress.opensuse.org/issues/940902021-06-16T08:36:44Ztjyrinki_susetjyrinki+redmine@suse.de
<p>Researching end-to-end scenarios combining multiple SUSE technologies and popular real life uses across functional areas into test cases.</p>
<p>The focus is on testing the combination, not any specific component.</p>
<p>Focus should be in splitting items into smaller subtickets that could be in the backlog eventually. Feel free to create new tickets, adjust current ones, the plans are not set in stone.</p>
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 #88687 (New): [qe-tools] Use the TEST_SUITE_SUFFICIENT value to mark packag...https://progress.opensuse.org/issues/886872021-02-17T10:11:04Ztjyrinki_susetjyrinki+redmine@suse.de
<p>Reviewing and actually using the collected TEST_SUITE_SUFFICIENT data together with making template generator aware of it to have templates automatically acknowledge when build time regression test suite is enough.</p>
<p>The current machine readable data for automation is at <a href="https://pes.suse.de/QA_Maintenance/Automation_Progress_Tracking_in_QAM/" class="external">https://pes.suse.de/QA_Maintenance/Automation_Progress_Tracking_in_QAM/</a> and so that should be appended - probably with new sections for indirect and build time ones - as needed with packages that would be now marked as automatically tested.</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 - coordination #64126 (New): [qe-core][epic] Identify packages that have automated i...https://progress.opensuse.org/issues/641262020-03-03T13:23:14Ztjyrinki_susetjyrinki+redmine@suse.de
<p>There's both 1) potentially indirect testing of packages that could be marked as tested automatically, and 2) database of TEST_SUITE_SUFFICIENT information from Updates Squad that could be used likewise.</p>
<p>Let's use this ticket to define guidelines for us.</p>
<a name="How"></a>
<h1 >How<a href="#How" class="wiki-anchor">¶</a></h1>
<ul>
<li>How to own our testing better (Where our needs for tooling end, and where the tooling should be provided by external teams)</li>
<li>How to decide whether it should be a package test, an openQA test, or a separate test ran within openQA</li>
<li>How to match this with our test plan</li>
</ul>