openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-01-27T07:20:44ZopenSUSE Project Management Tool
Redmine openQA Project - action #123724 (Resolved): auto_review not working despite ticket in openQA auto...https://progress.opensuse.org/issues/1237242023-01-27T07:20:44Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Ticket #122215 seems not functional still, the affected tests do not get the softfail forcing still automatically but need to be set manually daily.</p>
<p>The ticket has:<br>
<code>auto_review:"Test result is NOT same as baseline":force_result:softfailed</code><br>
... at the end of the subject, and the ticket was moved to openQA auto review project.</p>
<p>The tests can be found at the 15-SP4 runs at <a href="https://openqa.suse.de/group_overview/429" class="external">https://openqa.suse.de/group_overview/429</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: Result is changed to softfailed as specified in the title of the ticket</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Verify that the regex valid/working e.g. <code>auto_review:"Test result is NOT same as baseline":force_result:softfailed</code>, maybe by putting the title in a unit test and seeing if that fails</li>
<li>Check that the ticket is filed correctly, i.e. using the force result tracker - this <strong>seems</strong> to be correct</li>
<li>Check the code in <a href="https://github.com/os-autoinst/scripts" class="external">https://github.com/os-autoinst/scripts</a></li>
</ul>
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 #107338 (Resolved): [qe-core] test fails in vino_screensharing_availablehttps://progress.opensuse.org/issues/1073382022-02-23T12:51: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 vino.</p>
<hr>
<p>openQA test in scenario sle-15-SP4-Online-x86_64-extra_tests_gnome@64bit fails in<br>
<a href="https://openqa.suse.de/tests/8207927/modules/vino_screensharing_available/steps/47" class="external">vino_screensharing_available</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/7262605" class="external">43.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=64bit&test=extra_tests_gnome&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: Vino should not be used where it's deprecated</p>
openQA Tests - action #107320 (Rejected): [qe-core] test fails in prepare_test_data - sshd[2171]:...https://progress.opensuse.org/issues/1073202022-02-23T10:10:57Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>ssh connection is consistently dropping between the SUT and openQA at prepare_test_data, preventing further tests. </p>
<p>openQA test in scenario sle-15-SP4-Online-s390x-extra_tests_gnome@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/8207530/modules/prepare_test_data/steps/10" class="external">prepare_test_data</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="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC:0</strong> Switch the test to use root console to remove the initial failure/urgency</li>
<li><strong>AC:1</strong> Investigate: sshd[2171]: error: kex_exchange_identification: Connection closed by remote host</li>
<li><strong>AC:2</strong> Investigate if this test can be unscheduled. Tests may be able or already are downloading the necessary test data themselves. No need to download unneeded data.</li>
<li><strong>AC:3</strong> Make sure that the ssh console is necessary for s390, given that we have a working serial console</li>
<li><strong>AC:4</strong> Investigate if it is a backend/hardware problem with grenache/s390 machine</li>
<li><strong>AC:5</strong> Investigate if the problem is caused by the choice of <code>user-console</code></li>
</ul>
<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/7618963" class="external">61.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=s390x&distri=sle&flavor=Online&machine=s390x-kvm-sle12&test=extra_tests_gnome&version=15-SP4" class="external">latest</a></p>
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 #93895 (Resolved): [qe-core][qe-yast][qu] ext4_yast@s390x-zVM-vswitch-l3 fa...https://progress.opensuse.org/issues/938952021-06-11T11:32:23Ztjyrinki_susetjyrinki+redmine@suse.de
<p>See for example <a href="https://openqa.suse.de/tests/6209945" class="external">https://openqa.suse.de/tests/6209945</a></p>
<p>Even if it would pass bootloader, it would fail to setup_libyui. At least the latter should be fixed regardless of the bootloader problems.</p>
openQA Tests - action #93757 (Resolved): [qe-core][qe-yast][qu] test fails in setup_libyui on lvm...https://progress.opensuse.org/issues/937572021-06-10T06:16:12Ztjyrinki_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-aarch64-lvm_thin_provisioning@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/6209821/modules/setup_libyui/steps/4" class="external">setup_libyui</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Complete OS deployment with unencrypted LVM drive management. Test creates 2 LVM and BIOS boot partitions. Thin pool and thin lv resides on the second LVM partition, where /home (XFS) is being mounted. Maintainer: mloviska, poo#39023</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/6209821" class="external">391.12</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/6123981" class="external">391.8</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=aarch64&distri=sle&flavor=Full-QR&machine=aarch64&test=lvm_thin_provisioning&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #93754 (Resolved): [qe-core][qe-yast][qu] xfs@svirt-xen-pv test fails in se...https://progress.opensuse.org/issues/937542021-06-10T06:05:25Ztjyrinki_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-x86_64-xfs@svirt-xen-pv fails in<br>
<a href="https://openqa.suse.de/tests/6210241/modules/setup_libyui/steps/8" class="external">setup_libyui</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 Yast, QE Kernel</p>
<p>Installation test with explicit selection of "xfs" instead of default.</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/6210241" class="external">391.12</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/6130040" class="external">391.8</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-QR&machine=svirt-xen-pv&test=xfs&version=15-SP2" class="external">latest</a></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 #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 - 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 #91106 (Resolved): [qe-core][qe-yast][qu] test fails in select_guided_setuphttps://progress.opensuse.org/issues/911062021-04-14T08:27:24Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Started failing 18 days ago, likely needs to fork the yaml schedule.</p>
<p>openQA test in scenario sle-15-SP2-Full-QR-x86_64-ext4@svirt-xen-pv fails in<br>
<a href="https://openqa.suse.de/tests/5792646/modules/select_guided_setup/steps/2" class="external">select_guided_setup</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: okurz</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/5767616" class="external">385.10</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/5725263" class="external">385.7</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-QR&machine=svirt-xen-pv&test=ext4&version=15-SP2" class="external">latest</a></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>
openQA Infrastructure - action #90275 (Resolved): Replacement openQA OSD aarch64 hardware (was: D...https://progress.opensuse.org/issues/902752021-03-18T10:29:54Ztjyrinki_susetjyrinki+redmine@suse.de
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>We have had a machine from orthos, but we need to renew the lease every now and then or lose it. It would be easier to have a more permanent solution for eg snapshot validations.</p>
<p>openQA tests aarch64 on KVM, this ticket would be about improving the baremetal aarch64 testing. We were not able to test RC1 on baremetal (non-rpi) aarch64 due to lack of access to hardware (eg problems on thunderx10)</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: <strong>DONE</strong> Make new arm machines available</li>
<li><strong>AC2</strong>: openqaworker-arm-4 is salted and processing jobs</li>
<li><strong>AC3</strong>: openqaworker-arm-5 is salted and processing jobs</li>
</ul>