openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-07-27T12:58:27ZopenSUSE Project Management Tool
Redmine qe-yam - action #114730 (Rejected): [Timebox: 16h] Investigate which job results block approval f...https://progress.opensuse.org/issues/1147302022-07-27T12:58:27Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>When a job from our <a href="https://openqa.suse.de/group_overview/421" class="external">aggregate maintenance updates</a> fails, it blocks all the related maintenance updates from approval by the members of the <code>qam-openqa</code> group (maintenance openqa reviewers).<br>
The questions arises, what job states, other than <code>failed</code>, result in maintenance updates being blocked?<br>
Does for instance an <a href="https://openqa.suse.de/tests/9222738" class="external">incomplete</a> job or a <a href="https://openqa.suse.de/tests/9222743#" class="external">cancelled</a> job also block their related updates? <br>
Knowing this will help us better organize the required actions in the context of our Maintenance Update Review process. </p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong> Figure out what job results block update approval for qam-openqa</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<p>The maintenance openqa reviewer use this dashboard <a href="http://dashboard.qam.suse.de/blocked" class="external">http://dashboard.qam.suse.de/blocked</a> to have visibility on the blocked updates.<br>
The maintainer of this dashboard (maybe someone from qe-tools?) should be able to help.<br>
Also we could check what happen when some arch doesn't run any job.</p>
qe-yam - action #103320 (Rejected): Create new test module for DASD disk filteringhttps://progress.opensuse.org/issues/1033202021-11-30T14:13:15Zgeorggkioulis@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>In DASD Disk Management page (can be seen <a href="https://openqa.suse.de/tests/7125537#step/disk_activation/2" class="external">here</a>) there is the capability of filtering DASD disks by inputting a channel range in the minimum and maximum channel ID fields.</p>
<p>We can test this by using the functionality (<code>enter_maximum_channel</code>, <code>enter_minimum_channel</code>, <code>press_filter_button</code>) provided by <code>DASDDiskManagementPage.pm</code>.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create a test module that filters the shown DASD devices by a selected channel range and validate the output.</li>
<li>It is sufficient to include this test module in a single job's schedule that includes the <code>configure_dasd</code> test module, not all of them.</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>An easy implementation can be to have the same channel value for minimum and maximum channel. This will make validating the output easier, since the device table item list will contain only one item to be asserted.</li>
</ul>
qe-yam - action #99603 (Rejected): svirt-xen-hvm jobs entering emergency mode in first boothttps://progress.opensuse.org/issues/996032021-10-01T09:59:42Zgeorggkioulis@suse.com
<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-xfs@svirt-xen-hvm fails in<br>
<a href="https://openqa.suse.de/tests/7262467/modules/first_boot/steps/9" class="external">first_boot</a></p>
<p>also fails on <a href="https://openqa.suse.de/tests/7276616#step/first_boot/9" class="external">textmode</a> and <a href="https://openqa.suse.de/tests/7262464#step/first_boot/9" class="external">minimal+base_yast</a></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>. 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/7262467" class="external">43.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/7218822" class="external">39.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=Online&machine=svirt-xen-hvm&test=xfs&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #99180 (Resolved): test fails in scc_registration in QR 15-SP3https://progress.opensuse.org/issues/991802021-09-24T10:49:22Zgeorggkioulis@suse.com
<p>After a recent change where the multipath activation pop up appears right after disk activation has been completed, the multipath module needs to precede the registration module in the zfcp jobs.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Online-QR-s390x-zfcp@s390x-zfcp fails in<br>
<a href="https://openqa.suse.de/tests/7215665/modules/scc_registration/steps/5" 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>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>. Maintainer: QE Yast, mgriessmeier</p>
<p>Installation-only test configuring an s390x ZFCP storage.</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/7141435" class="external">188.16</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/6872082" class="external">188.15</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=s390x&distri=sle&flavor=Online-QR&machine=s390x-zfcp&test=zfcp&version=15-SP3" class="external">latest</a></p>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<p>Alter the order the schedule so that multipath module precedes the registration.</p>
openQA Tests - action #96680 (Resolved): [qe-core] s390qa102.qa.suse.de zfcp issuehttps://progress.opensuse.org/issues/966802021-08-09T14:28:28Zgeorggkioulis@suse.com
<p>The disc_activation module <a href="https://openqa.suse.de/tests/6655178" class="external">fails</a> when the job is assigned to the second worker instance (s390qa102.qa.suse.de)</p>
<p>Bringing the FCP device online with <code>chccwdev -e 0.0.fa00</code> on s390qa102 does not attach the SCSI devices:</p>
<pre><code># lszfcp -PHD
0.0.fa00 host0
Error: No fcp devices found.
# cat /proc/scsi/scsi (shows no SCSI attached devices)
Attached devices:
# dmesg
[ 57.022293] NET: Registered protocol family 32
[ 387.264999] qdio: 0.0.fa00 ZFCP on SC 5 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A
[ 388.325650] scsi host0: zfcp
</code></pre>
<p>This probably happens due to a mapping issue of the zfcp devices on the s390qa102 virtual machine.<br>
A recommendation on how to proceed here is to file an infra ticket in order for the issue to be further investigated.</p>
openQA Tests - action #91899 (Resolved): [qe-core] 15SP2 QU - An error occured during the install...https://progress.opensuse.org/issues/918992021-04-28T10:11:12Zgeorggkioulis@suse.com
<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-RAID6@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/5891733/modules/setup_libyui/steps/3" class="external">setup_libyui</a></p>
<p>Installation of RAID6 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/5884567" class="external">390.3</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/5836424#step/setup_libyui/1" class="external">setup_libyui</a></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&test=RAID6&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #89335 (Resolved): [qe-core][systemd] qa_test_systemd fails in check-unit t...https://progress.opensuse.org/issues/893352021-03-02T12:03:14Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-Server-DVD-Updates-x86_64-mau-qa_userspace_systemd@64bit fails in <code>check-unit</code> testcase<br>
<a href="http://angmar.suse.de/tests/3069/modules/1_systemd/steps/63" class="external">1_systemd</a></p>
<a name="More-info"></a>
<h2 >More info<a href="#More-info" class="wiki-anchor">¶</a></h2>
<p><code>check-unit</code> testcase fails both is sle-15 and sle-15-sp1 because <code>qaperf.service</code> of <code>qa_testset_automation</code> package fails to start for SLE-15 and SLE-15SP1.</p>
openQA Tests - action #88648 (Resolved): [qe-core][qem][systemd] qa_test_systemd fails in check-l...https://progress.opensuse.org/issues/886482021-02-16T13:51:51Zgeorggkioulis@suse.com
<p>The systemd testsuite (<code>qa_test_systemd</code>) fails in</p>
<ul>
<li><code>check-named</code> for sle 15, sle 15sp1 and sle 15sp2. The service <code>named.service</code> does not exist in those products.</li>
<li><code>check-lvm2-lvmetad</code> for sle 15sp2. The service <code>lvm2-lvmetad.service</code> does not exist in this product.</li>
</ul>
<p>The problem is a bit different than one might first think, because the default behavior of the testsuite should be to SKIP those missing service tests rather than fail.<br>
But how do we know what the default behavior should be?</p>
<p>To answer this, let's check sle 12sp5:<br>
In this product, the <code>named.service</code> does not exist, similar to sle 15 and above. However the <code>check-named</code> testcase is SKIPPED here.<br>
The <code>/usr/share/qa/tools/test_systemd_run</code> script (that runs the testsuite) in short runs <code>/usr/share/qa/qa_test_systemd/check-service.sh</code> against all to-be-tested services as listed in <code>/usr/share/qa/qa_test_systemd/tcf/qa_systemd.tcf</code>.<br>
<code>/usr/share/qa/qa_test_systemd/check-service.sh</code> contains a function <code>function get_loaded()</code> that gets the <code>Loaded:</code> status of the service that is being tested. Later in the code, if this status is <code>"not-found"</code>, then the script exits with <code>exit 22</code>. This results in the current service test being skipped.<br>
So for 12sp5 if we would be testing a service called <code>imaginary-service</code>, <code>get_loaded()</code> would run</p>
<pre><code> # systemctl status imaginary-service
imaginary-service.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
</code></pre>
<p>So after <code>grepping</code> the <code>Loaded</code> status (which is <code>"not-found"</code>), it would skip the test for <code>imaginary-service.service</code></p>
<p>However for sle 15 and above the output of systemctl has changed:<br>
Here we get</p>
<pre><code>systemctl status imaginary-service
Unit imaginary-service.service could not be found.
</code></pre>
<p>Which means that <code>get_loaded</code> cannot grep the <code>Loaded</code> status and exits with <code>exit 1</code>, resulting in a failing testcase.</p>
<p>Given the above, there are two potential actions to address the aforementioned fails:</p>
<ul>
<li>The testsuite behavior should be fixed for the sle 15 products, namely how the <code>get_loaded</code> function gets the loaded status.</li>
<li>I also believe (but I am not sure if it is the correct route) that apart from the above change, the tests for the services that are no longer found (<code>check-lvm2-lvmetad</code> and <code>check-named</code>) should be removed from the <code>qa_systemd.tcf</code> of the qa_test_systemd versions that correspond to those products</li>
</ul>
openQA Tests - action #88597 (Resolved): [qe-core][qem][systemd] qa_test_systemd fails in rc-loca...https://progress.opensuse.org/issues/885972021-02-15T09:31:10Zgeorggkioulis@suse.com
<p>An executable <code>boot.local</code> does not exist by default in sle15, sle15sp1 and sle15sp2.<br>
This results in <code>qa_test_systemd</code> not passing the <code>rc-local</code> service test.</p>
<p>A failure can be seen <a href="https://openqa.suse.de/tests/4191578#step/1_systemd/35" class="external">here</a></p>
openQA Tests - action #81044 (Resolved): [qe-core][qem] Add check for unreleased container imageshttps://progress.opensuse.org/issues/810442020-12-14T14:58:03Zgeorggkioulis@suse.com
<p>There is need to automate the release of 15-SP3 container images from <a href="https://build.suse.de/project/show/SUSE:SLE-15-SP3:Update:CR" class="external">https://build.suse.de/project/show/SUSE:SLE-15-SP3:Update:CR</a> to <a href="https://build.suse.de/project/show/SUSE:SLE-15-SP3:Update:CR:ToTest" class="external">https://build.suse.de/project/show/SUSE:SLE-15-SP3:Update:CR:ToTest</a>. <br>
Since 15-SP3 is not public, openQA container tests should not be scheduled and the container image should not be able to get released to the public registry.</p>
<p>This will be part of <a href="https://gitlab.suse.de/geor/container_bot" class="external">https://gitlab.suse.de/geor/container_bot</a>.<br>
Once this is implemented, the container_bot running in <code>qam.suse.de</code> should have it's version updated.</p>
openQA Tests - action #80360 (Resolved): [qe-core] Reboot gnome through mouse clicks on all productshttps://progress.opensuse.org/issues/803602020-11-25T11:41:55Zgeorggkioulis@suse.com
<p>GNOME 3.38 changes the openQA graphical reboot process.<br>
In order to avoid branching the reboot behavior based on gnome version, a common graphical reboot sequence should be adopted for throughout all products in <code>sub reboot_x11</code>, for GNOME.</p>
openQA Tests - action #78296 (Resolved): [qe-core][qem] test fails in install_updatehttps://progress.opensuse.org/issues/782962020-11-19T13:41:03Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP3-Server-DVD-Incidents-Minimal-x86_64-qam-minimal-full@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4920287/modules/install_update/steps/48" class="external">install_update</a></p>
<p>The error message is <code>nothing provides libzypp >= 16.21.2 needed by zypper-1.13.57-21.32.1.x86_64</code></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>minimal = base pattern, minimal (enhanced base) pattern are additional convenience paclkages</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/4919728" class="external">:16986:zypper</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/4915695" class="external">:16967:ca-certificates-mozilla</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-Incidents-Minimal&machine=64bit&test=qam-minimal-full&version=12-SP3" class="external">latest</a></p>
openQA Tests - action #72037 (Workable): [yast][security][qem][shim] Enable shim testing on barem...https://progress.opensuse.org/issues/720372020-09-28T16:37:18Zgeorggkioulis@suse.com
<p>Although we do have openQA runs with secure boot, there is need for <code>shim</code> testing on baremetal machine with secure boot.</p>
<p>probably the following would need to be scheduled:</p>
<ul>
<li>security/mokutil_sign.pm</li>
<li>console/verify_efi_mok.pm</li>
</ul>
openQA Tests - action #71974 (Resolved): [qam][ant] test fails in anthttps://progress.opensuse.org/issues/719742020-09-28T10:56:15Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP5-Server-DVD-Updates-aarch64-mau-extratests@aarch64-virtio fails in<br>
<a href="https://openqa.suse.de/tests/4706226/modules/ant/steps/23" class="external">ant</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Run console tests against aggregated test repo</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/4682322" class="external">20200914-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=aarch64&distri=sle&flavor=Server-DVD-Updates&machine=aarch64-virtio&test=mau-extratests&version=12-SP5" class="external">latest</a></p>
openQA Tests - action #44306 (Closed): [qam] test fails in ant due to com.sun.tools.javac.Main no...https://progress.opensuse.org/issues/443062018-11-23T16:23:39Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP3-Server-DVD-Updates-x86_64-mau-extratests@64bit fails in<br>
<a href="https://openqa.suse.de/tests/2277443/modules/ant/steps/20" class="external">ant</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/2277443" class="external">20181123-2</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/2275386" class="external">20181123-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&version=12-SP3&distri=sle&test=mau-extratests&flavor=Server-DVD-Updates&machine=64bit" class="external">latest</a></p>