openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-10-17T16:13:22ZopenSUSE Project Management Tool
Redmine qe-yam - action #118966 (Rejected): Testuiste mru-iscsi_{client,server}_normal_auth_backstore_{lv...https://progress.opensuse.org/issues/1189662022-10-17T16:13:22Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Related to <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Add AutoYaST test suites for chained dependencies in YaST Maintenance Updates (rest of products) (Resolved)" href="https://progress.opensuse.org/issues/111743">#111743</a><br>
Testsuites <code>create_hdd_yast_maintenance_desktop</code> and <code>create_hdd_yast_maintenance_minimal</code> are performing an autoyast installation which is used by subsequent testsuites (eg <code>mau-extratests-yast2ui</code>, <code>mau_extratests_yast2_ncurses</code>, <code>mau_extratests_yast_cmd</code>).</p>
<p>However the <code>mru-iscsi</code> multimachine testsuites that have <code>create_hdd_yast_maintenance_desktop</code> as a dependency seem to bump into an issue where the Network of the resulting image is not configured, ending up with <a href="https://openqa.suse.de/tests/9742604#step/addon_products_via_SCC_yast2/25" class="external">this type of failure</a>.</p>
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p><a href="https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=mru-iscsi_client_normal_auth_backstore_lvm_dev&test=mru-iscsi_server_normal_auth_backstore_lvm_dev&test=mru-iscsi_client_normal_auth_backstore_fileio_dev&test=mru-iscsi_server_normal_auth_backstore_fileio_dev&test=mru-iscsi_client_normal_auth_backstore_hdd_dev&test=mru-iscsi_server_normal_auth_backstore_hdd_dev&modules=&module_re=&distri=sle&build=20221016-1&groupid=446#" class="external">mru-iscsi_{client,server}_normal_auth_backstore_{lvm,fileio,hdd}</a> for MU YaST 12-SP4 to 15-SP2 Job groups.<br>
arch: x86_64</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: The mru-iscsi_{client,server}<u>normal_auth_backstore</u>{lvm,fileio,hdd} testsuites succeed on the Registration step.<br>
<strong>AC2</strong>: The mru-iscsi_{client,server}<u>normal_auth_backstore</u>{lvm,fileio,hdd} are removed from the development group, and their equivalent testsuites in the YaST MU Job Groups now have a dependency on the <code>create_hdd_yast_maintenance_desktop</code> testsuite.</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<ul>
<li>This is most probably an AutoYaST profile related issue. The <code>mru-iscsi_{client,server}_normal_auth_backstore_{lvm,fileio,hdd}</code> seem to run fine for <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP3&build=20221016-1&groupid=421" class="external">15-SP3</a> and <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=20221016-1&groupid=421" class="external">15-SP4</a>, maybe it is worth observing how network configuration is done on these autoyast installation <code>create_hdd_yast_maintenance_desktop</code> jobs.</li>
</ul>
qe-yam - action #116128 (Rejected): Rectify unsupported configuration in bootloader settings when...https://progress.opensuse.org/issues/1161282022-09-01T14:20:22Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>When migrating form 15sp4 hpc to 15sp5, the test encounters an unsupported bootloader configuration (unkown udev device), as seen <a href="https://openqa.suse.de/tests/9426332#step/start_install/2" class="external">here</a>. The issue is likely caused by an earlier configuration which would need to be mitigated.</p>
<a name="Scope"></a>
<h4 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h4>
<p>Migration: HPC <a href="https://openqa.suse.de/tests/9426332#step/start_install/2" class="external">https://openqa.suse.de/tests/9426332#step/start_install/2</a> </p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Adjust the test so that bootloader configuration is written to an existing disk.</p>
qe-yam - action #105972 (Rejected): New version of nvme package causes nvme_checks module to failhttps://progress.opensuse.org/issues/1059722022-02-04T16:28:46Zgeorggkioulis@suse.com
<p>Since build 91.2 the nvme package has been bumped to version 2.0 (from 1.13).</p>
<p>This causes (among other things) some changes in the output of <code>nvme list</code> and <code>nvme list-ns /dev/nvme0</code>.</p>
<p>The <code>nvme_checks.pm</code> module fails when running <code>nvme list-ns /dev/$nvm_test_data->{nvm_char_device} | awk -F ':' '{print $2}'"</code>, because, in the new version, <code>nvme list-ns /dev/nvme0</code> outputs nothing, instead of <code>[ 0]:0x1</code>.</p>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=uefi&test=nvme&version=15-SP4" class="external">latest</a></p>
<p><strong>Suggestion:</strong> change the <code>nvme list-ns</code> command to verify the 0x1 namespace array</p>
qe-yam - action #101903 (Rejected): Investigate test failure in integration_serviceshttps://progress.opensuse.org/issues/1019032021-11-03T15:18:29Zgeorggkioulis@suse.com
<p>The <code>integration_services.pm</code> module fails at the <code>select_console 'root-console'</code> call.<br>
This fails because the System Under Test finds itself in the display manager screen.<br>
When fixed the test behavior should be similar to <a href="https://openqa.suse.de/tests/5785744#step/integration_services/2" class="external">the old runs</a>.</p>
<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-select_modules_and_patterns+registration@svirt-hyperv-uefi fails in<br>
<a href="https://openqa.suse.de/tests/7591216/modules/integration_services/steps/5" class="external">integration_services</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Full Medium installation that covers the following cases:<br>
1. Additional modules enabled using SCC (Legacy, Development Tools,<br>
Web and Scripting, Containers, Desktop Applications);<br>
2. Yast patterns installed;<br>
3. System registration is skipped during installation;<br>
4. Installation is validated by successful boot and that YaST does not<br>
report any issues;<br>
5. Registration is performed on the installed system.</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/7200373" class="external">38.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=Full&machine=svirt-hyperv-uefi&test=select_modules_and_patterns%2Bregistration&version=15-SP4" class="external">latest</a></p>
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>
qe-yam - action #99600 (Rejected): Investigate System Role page not loadinghttps://progress.opensuse.org/issues/996002021-10-01T09:43:51Zgeorggkioulis@suse.com
<p>Until now, at the end of <code>addon_products_sle</code> module, once the next button is pressed using keyboard, the System Role page appears, as can be seen in the last screen of the <code>addon_products_sle</code> module <a href="https://openqa.suse.de/tests/7200374#step/addon_products_sle/60" class="external">on previous runs</a>.</p>
<p>In the new build however, the transition to the System Role page never happens resulting in a failing needle in the <code>system_role</code> module.</p>
<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-select_modules_and_patterns+registration@svirt-hyperv2016 fails in<br>
<a href="https://openqa.suse.de/tests/7279621/modules/system_role/steps/2" 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>Full Medium installation that covers the following cases:<br>
1. Additional modules enabled using SCC (Legacy, Development Tools,<br>
Web and Scripting, Containers, Desktop Applications);<br>
2. Yast patterns installed;<br>
3. System registration is skipped during installation;<br>
4. Installation is validated by successful boot and that YaST does not<br>
report any issues;<br>
5. Registration is performed on the installed system.</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/7124547" class="external">36.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=Full&machine=svirt-hyperv2016&test=select_modules_and_patterns%2Bregistration&version=15-SP4" class="external">latest</a></p>
qe-yam - action #99573 (Rejected): Investigate failure of LVM activationhttps://progress.opensuse.org/issues/995732021-09-30T15:36:18Zgeorggkioulis@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-aarch64-activate_encrypted_volume+import_users@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/7274219/modules/skip_install_addons/steps/1" class="external">skip_install_addons</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/7269640" 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: <a href="https://openqa.suse.de/tests/7217928" 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=aarch64&distri=sle&flavor=Online&machine=aarch64&test=activate_encrypted_volume%2Bimport_users&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #96986 (Workable): [qe-core][sporadic][samba_adcli] net ads join / leave failshttps://progress.opensuse.org/issues/969862021-08-16T13:36:01Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><code>net ads join</code> occasionally fails in <a href="https://openqa.suse.de/tests/6838830#step/samba_adcli/55" class="external">samba_adcli</a></p>
<p>The command <code>net ads join --domain geeko.com -U Administrator --no-dns-updates -i</code> occasionally fails with:</p>
<pre><code>ads_print_error: AD LDAP ERROR: 53 (Server is unwilling to perform): 0000001F: SvcErr: DSID-031A1236, problem 5003 (WILL_NOT_PERFORM), data 0
</code></pre>
<p>similar issue for the command <code>net ads leave --domain geeko.com -U Administrator -i'</code></p>
<p>For now it has been softfailed.</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/6839956#step/samba_adcli/60" class="external">ge0r/os-autoinst-distri-opensuse#retry-adcli-join</a> (or more recent)</p>
openQA Tests - action #96983 (Workable): [qe-core][sporadic][samba_adcli] adcli joining domain failshttps://progress.opensuse.org/issues/969832021-08-16T13:24:46Zgeorggkioulis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>adcli join fails in <a href="https://openqa.suse.de/tests/6840326/modules/samba_adcli/steps/220" class="external">samba_adcli</a></p>
<p>The command <code>adcli join -v -W --domain geeko.com -U Administrator -C</code> sporadically results in :</p>
<pre><code>Couldn't perform discovery search: Can't contact LDAP server
* Received NetLogon info from: WIN-NHOU56DRDK4.geeko.com
! Cannot set computer password: Authentication error
adcli: joining domain geeko.com failed: Cannot set computer password: Authentication error
</code></pre>
<p>Increasing the number of retries just reduces the frequency of the failure. For now it has been softfailed.</p>
<p>The expected output of the aforementioned <code>adcli join</code> command can be seen <a href="https://openqa.suse.de/tests/6839956#step/samba_adcli/226" class="external">here</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/6840326" class="external">ge0r/os-autoinst-distri-opensuse#retry-adcli-join</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/6839956" class="external">ge0r/os-autoinst-distri-opensuse#retry-adcli-join</a> (or more recent)</p>
openQA Tests - coordination #96980 (Workable): [qe-core][samba_adcli][epic] Tracker for samba_adc...https://progress.opensuse.org/issues/969802021-08-16T13:23:29Zgeorggkioulis@suse.comopenQA Tests - action #96513 (Workable): [qe-core][sporadic][samba_adcli] wbinfo failshttps://progress.opensuse.org/issues/965132021-08-03T12:18:07Zgeorggkioulis@suse.com
<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-aarch64-mau-extratests2@aarch64-virtio fails in<br>
<a href="https://openqa.suse.de/tests/6630974/modules/samba_adcli/steps/78" class="external">samba_adcli</a></p>
<p>Test samba_adcli sporadicly fails due to wbinfo failures<br>
eg <code>wbinfo -u</code> fails with <code>Error looking up domain users</code></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/6630974" class="external">20210802-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/6628144" class="external">20210801-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=aarch64&distri=sle&flavor=Server-DVD-Updates&machine=aarch64-virtio&test=mau-extratests2&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #95611 (Workable): [qe-core][samba_adcli] test fails in samba_adcli in s390...https://progress.opensuse.org/issues/956112021-07-19T08:30:46Zgeorggkioulis@suse.com
<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-s390x-Build20210719-1-mau-extratests2@s390x-kvm-sle12 fails in <a href="https://openqa.suse.de/tests/6483346#step/samba_adcli/60" class="external">samba_adcli</a></p>
<p>From what I understand, the samba_adcli module has never been run for s390. </p>
<p>The <code>adcli join -v -W --domain geeko.com -U Administrator -C</code> does not work, even with multiple retries, possibly is a network access problem on one of the lpars</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ol>
<li>Run a manual installation or use an image on an s390 kvm machine and/or lpar (zkvm), and try to run the steps manually</li>
<li>If step above works, trigger a job in openQA and use developer mode (Trigger the job with PAUSE_AT=samba_adcli and use <a href="https://confluence.suse.com/pages/viewpage.action?pageId=742719853" class="external">this page</a> to figure out how to connect to the running machine, possibly for s390 zkvm the procedure might be different, ping szarate) and debug the network (starting with trying to ssh Administrator@$AD_ip/windows machine).</li>
<li>Update test module/and/or modify host, create follow up tickets as needed</li>
</ol>
QA - action #94600 (New): [tools][mtui] Communicate reduced visibility of openQA incident related...https://progress.opensuse.org/issues/946002021-06-23T13:49:30Zgeorggkioulis@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>The <code>Results from openQA incidents jobs:</code> section in a maintenance update's test log shows, as one would expect, the incident jobs related to the incident that is to be tested.<br>
It can happen that engineers testing the incident fall under the impression that the openQA coverage shown in the log is the complete openQA test coverage for that incident.<br>
It should thus be communicated that the <code>openQA incident jobs</code> section does not show the complete test coverage of the incident in openQA, but only a subset of it (the other being in aggregate runs that test the incident).</p>
<p>This should clarify to the engineers that the absence of failed incident jobs in the log does not mean necessarily that there are no other failed jobs related to the incident.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Communicate that the jobs listed in the log of an update are not the complete set of jobs that test that update</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>One suggestion could be to remove that section from the log and instead link the incident comments (eg <a href="https://maintenance.suse.de/incident/19067/#comments" class="external">https://maintenance.suse.de/incident/19067/#comments</a>) where all jobs related to that incident are listed.</li>
</ul>
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 #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>