openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-18T12:32:04ZopenSUSE Project Management Tool
Redmine qe-yam - action #157474 (Resolved): Remove package Hub from SLE 12 SP5 migrations and resolve ven...https://progress.opensuse.org/issues/1574742024-03-18T12:32:04Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>According to the response in a dependency issue bug report: <a href="https://bugzilla.suse.com/show_bug.cgi?id=1209498#c3" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1209498#c3</a> <br>
We should remove packagehub from migration scenarions as it is not L3 supported.<br>
In the PRD is explicitly mentioned about not supported for SLE 12 SP5, for SLE 15 SPN is on best effort.</p>
<p>Latest conflict issues for two migration tests that include phub prior migration: <a href="https://openqa.suse.de/tests/13793854#step/resolve_dependency_issues/28" class="external">https://openqa.suse.de/tests/13793854#step/resolve_dependency_issues/28</a> and <a href="https://openqa.suse.de/tests/13793867#step/resolve_dependency_issues/3" class="external">https://openqa.suse.de/tests/13793867#step/resolve_dependency_issues/3</a></p>
<p>Additionally we have a mechanism to resolve vendor changes for the SLE 15 SP5 failures related with phub.</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: phum module removed from SLE 12 SP5 migrations.<br>
<strong>AC2</strong>: Vendor changes for SLE 15 SP5 addressed via setting that activate that testing path in the UI.</p>
qe-yam - action #157156 (Resolved): Textmode auto-installation fails in spvm due to partitioning ...https://progress.opensuse.org/issues/1571562024-03-13T12:43:21Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Scope"></a>
<h2 >Scope<a href="#Scope" class="wiki-anchor">¶</a></h2>
<p>Recently the PPC grenache worker was restored and ppc tests run again. For <a href="https://openqa.suse.de/tests/13768555#step/bootloader_start/43" class="external">create_hdd_gnome</a> though, we see constant failures at the early step of bootloader_start module. The <a href="https://openqa.suse.de/tests/13711494" class="external">create_hdd_textmode</a> test is successful, following the same steps. Noticable difference so far at lsblk step, the sda disk seems not to be empty and unformatted: <a href="https://openqa.suse.de/tests/13768555#step/bootloader_start/39" class="external">https://openqa.suse.de/tests/13768555#step/bootloader_start/39</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>Find the root cause.</li>
<li>Implement a fix, if possible.</li>
</ul>
qe-yam - action #153964 (In Progress): [Research: 24h] Check how to not need to set YUI_REST_API=...https://progress.opensuse.org/issues/1539642024-01-19T13:03:24Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Currently, we are distinguishing the libuyi test from the non-libyui tests by using the variable YUI_REST_API.<br>
It would be more convenient to create a different way, based on the version of the os (=+sles15-sp3). <br>
The challenge would be to avoid using multiple conditions in the os-autoinst-opensuse-distro repo.<br>
This settings is tightly coupled with the yaml schedule, so it might require some research what are all the points in the code affected.</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Find strategy to avoid setting YUI_REST_API at all.</p>
qe-yam - action #152807 (Resolved): Prepare for SLE 15 SP4 enters LTSS on mid December 2023 for M...https://progress.opensuse.org/issues/1528072023-12-20T11:47:37Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Follow the <a href="https://progress.opensuse.org/issues/121639" class="external">poo 121639</a>, SLE 15 SP4 enters LTSS on mid December 2023. <br>
We need update 15 SP4 tests to add 'LTSS' and corresponding regcode for 'LTSS', this include Maintenance Update and MU development.</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Update SLES 15 SP4 test to add 'LTSS' and verify.</p>
qe-yam - action #135194 (Resolved): Edit validate_encrypt module or create new onehttps://progress.opensuse.org/issues/1351942023-09-05T13:43:57Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently, in the module that we use for validating encrypted disks after installation, there are many checks that don't really make sense to keep, as they do not have to do with the settings chosen during installation itself. For example, verifying the LUKS version or the key location, is out of our testing scope. </p>
<p>The particular module is used by other teams (security and qam), so before editing it we could contact them to check if they need the particular checks, or simply create a new one that will validate the disk encryption accordingly, avoiding checks that do not concern Yast team. </p>
<p><strong>Acceptance criteria</strong></p>
<ul>
<li>Investigate and select the proper encryption checks.</li>
<li>Make sure we will not remove checks significant to other teams.</li>
<li>Replace module and test data in current tests.</li>
</ul>
qe-yam - action #134990 (Resolved): Sporadic failure in zypper_migration due to invalid repo URL https://progress.opensuse.org/issues/1349902023-09-01T07:51:01Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Two migration tests fail due to invalid SP6 repositories:<br>
ppc64le test in migration misc. : <a href="https://openqa.suse.de/tests/11954086#step/scc_registration/4" class="external">https://openqa.suse.de/tests/11954086#step/scc_registration/4</a><br>
x86_64 test in migration daily : <a href="https://openqa.suse.de/tests/11961594/modules/zypper_migration/steps/9" class="external">https://openqa.suse.de/tests/11961594/modules/zypper_migration/steps/9</a></p>
<p>In zypper log :</p>
<p>2023-08-31 05:08:25 susetest(11062) [zypp-core] Exception.cc(log):186 repos.cc(build_cache):456 CAUGHT: [SUSE_Linux_Enterprise_Server_15_SP6_x86_64:SLE-Product-SLES15-SP6-Pool|<a href="https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15-SP6/x86_64/product?-GSt7JnzfNnwwVlBHE1U_FghhBtzPI_3FTYvrOITzaBHvIVp2JHNJHsUkAIpTFvr6Zt7gAZb-SnBLueKEIKhaITo8VGa9_fSJlJOVbrVdGLtKZbAQSrfPMGlByEZMPUxS7378F3AHPEhvwdZ5Maq3eQ5og" class="external">https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15-SP6/x86_64/product?-GSt7JnzfNnwwVlBHE1U_FghhBtzPI_3FTYvrOITzaBHvIVp2JHNJHsUkAIpTFvr6Zt7gAZb-SnBLueKEIKhaITo8VGa9_fSJlJOVbrVdGLtKZbAQSrfPMGlByEZMPUxS7378F3AHPEhvwdZ5Maq3eQ5og</a>] Valid metadata not found at specified URL</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP6-Migration-from-SLE15-SPx-x86_64-online_sles15sp3_ltss_pscc_basesys-srv-def_minimal_zypp@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11961594/modules/zypper_migration/steps/9" class="external">zypper_migration</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>The base test suite is used for job templates defined in YAML documents. It has no settings of its own.</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/11953980" class="external">16.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/11870058" class="external">13.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=Migration-from-SLE15-SPx&machine=64bit&test=online_sles15sp3_ltss_pscc_basesys-srv-def_minimal_zypp&version=15-SP6" class="external">latest</a></p>
qe-yam - action #130865 (Resolved): Create support image in textmode for SLE 15 SP5 which uses SC...https://progress.opensuse.org/issues/1308652023-06-14T10:44:52Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>Currently, generate_dud uses an outdated image to boot. The most recent failure had to do with the proxy scc being down, the outdated qcow had the proxy scc in /etc/SUSEConnect instead of the normal scc url, so the scc registration failed. <br>
We should add a textmode autoyast test in maintenance development job group for SP5 that will publish an updated image.</p>
<p>openQA test: sle-15-SP5-Server-DVD-Updates-x86_64-generate_dud@64bit<br>
<a href="https://openqa.suse.de/tests/11345026/modules/generate_dud/steps/25" class="external">generate_dud</a></p>
<p>We can omit the patching, it should be needed, but as the original scenario doesn't have it and it is stable we shouldn't complicate it more, but we could add patching in the future for sure, when we will have some migrations in maintenance update.</p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Create support image in textmode for SLE 15 SP5 which uses SCC instead of proxy.</p>
qe-yam - action #130288 (Resolved): test fails in select_only_visible_patterns_from_tophttps://progress.opensuse.org/issues/1302882023-06-02T12:22:10Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In Yast Maintenance Dev Job group for SLE 15 SP4, the select_only_visible_patterns_from_top module for yast-mru-install-minimal-with-addons_dev test, fails because there are a lot of new addons and the minimal-system cannot be found on the top of the list. We could try to replace select_only_visible_patterns_from_top with select_patterns</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Server-DVD-Updates-aarch64-yast-mru-install-minimal-with-addons_dev@aarch64-virtio fails in<br>
<a href="https://openqa.suse.de/tests/11234267/modules/select_only_visible_patterns_from_top/steps/10" class="external">select_only_visible_patterns_from_top</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>.</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/11220683" class="external">20230530-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/11214412" class="external">20230529-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=yast-mru-install-minimal-with-addons_dev&version=15-SP4" class="external">latest</a></p>
qe-yam - action #129859 (Resolved): Edit check_system_info for MILESTONE_VERSION checkhttps://progress.opensuse.org/issues/1298592023-05-25T08:23:59Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In check_system_info module, there is a check for MILESTONE_VERSION that seems unnecessary and can cause problems as we run Migration Milestone build after the image is published, so MILESTONE_VERSION is removed from the /etc/issue file. See relevant failure <a href="https://openqa.suse.de/tests/11189816#step/check_system_info#1/13" class="external">https://openqa.suse.de/tests/11189816#step/check_system_info#1/13</a><br>
We should either split the module and move the check to another one, that will be excluded from Migration Milestone Job group tests, or verify information in /etc/issue that remain after publishing the build file.</p>
qe-yam - action #128690 (Resolved): test fails in check_migration_features due to python310 missinghttps://progress.opensuse.org/issues/1286902023-05-04T12:48:02Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>python 3.10 is not shipped with SLE15 SP5 any more as it's been upgraded to python 3.11, according to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1207966" class="external">bug#1207966</a> . We should add the proper conditions in the check_migration_features.pm to avoid the bellow failure.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP5-Regression-on-Migration-from-SLE15-SPx-ppc64le-offline_sles15sp4_pscc_lp-basesys-srv-desk-dev-contm-lgm-tsm-wsm-py3-pcm_all_full@ppc64le-spvm fails in<br>
<a href="https://openqa.suse.de/tests/11022894/modules/check_migration_features/steps/28" class="external">check_migration_features</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>The base test suite is used for job templates defined in YAML documents. It has no settings of its own.</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/10658987" class="external">77.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=ppc64le&distri=sle&flavor=Regression-on-Migration-from-SLE15-SPx&machine=ppc64le-spvm&test=offline_sles15sp4_pscc_lp-basesys-srv-desk-dev-contm-lgm-tsm-wsm-py3-pcm_all_full&version=15-SP5" class="external">latest</a></p>
qe-yam - action #128198 (Resolved): Create autoyast installation testsuite to publish s390x image...https://progress.opensuse.org/issues/1281982023-04-24T07:46:46Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently the migration tests for sles12sp5 -> sles15sp5 use an outdated image, patch the system and then proceed to installation. As a result, the tests run for a long time and there are a lot of background processes running. Recently an issue occurred where force_scheduled_tasks module would sporadically collide with btrf_cleanup and it would <a href="https://openqa.suse.de/tests/10943063" class="external">fail</a> due to the load not being settled in time. Additionally, the migration test is very unstable and shows multiple different <a href="https://openqa.suse.de/tests/10743937#next_previous" class="external">failures</a> .</p>
<p><strong>Acceptance criteria</strong>:</p>
<ul>
<li>Create s390x autoyast installation test suite for sles12sp5 that will publish and updated image in Development job group.</li>
<li>Link the migration jobs with the new image and remove the patching part of the schedule.</li>
</ul>
qe-yam - action #127214 (Resolved): [sporadic] test fails in validate_installed_patternshttps://progress.opensuse.org/issues/1272142023-04-04T15:50:22Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The parser cannot locate the < in the beginning of the output, even though it's there.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP5-Online-aarch64-yast2_gui@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/10848056/modules/validate_installed_patterns/steps/5" class="external">validate_installed_patterns</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, riafarov</p>
<p>Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.</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/10825984" class="external">81.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/10748228" class="external">81.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=yast2_gui&version=15-SP5" class="external">latest</a></p>
qe-yam - action #125717 (Resolved): [sporadic] test fails in openldap_to_389dshttps://progress.opensuse.org/issues/1257172023-03-09T12:46:35Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Motivation"></a>
<h4 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h4>
<p>There is a sporadic failure for all regression tests that run openlad_to_389ds module, at the validation point that checks if the users belong to group1. It appears from the result , that the group data for the testusers are missing from the output . </p>
<p>openQA test in scenario sle-15-SP5-Regression-on-Migration-from-SLE12-SPx-x86_64-offline_sles12sp4_ltss_pscc_sdk-lp-we-asmm-contm-lgm-pcm-tcm-wsm_def_full@sofiasyria/os-autoinst-distri-opensuse#ldap@64bit fails in<br>
<a href="https://openqa.suse.de/tests/10640986/modules/openldap_to_389ds/steps/70" class="external">openldap_to_389ds</a></p>
<a name="Acceptance-criteria"></a>
<h4 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h4>
<p><strong>AC1</strong>: Ensure validation is correct</p>
<a name="Suggestions"></a>
<h4 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h4>
<p>We could try a retry on that point.</p>
openQA Tests - action #69754 (Resolved): [y][u] tests fail in bootloader_start for ppc64le - Powe...https://progress.opensuse.org/issues/697542020-08-10T08:09:03Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>For the time being, some machines are turned off, see: <a href="https://mailman.suse.de/mlarch/SuSE/maxtorhof/2020/maxtorhof.2020.08/msg00005.html" class="external">https://mailman.suse.de/mlarch/SuSE/maxtorhof/2020/maxtorhof.2020.08/msg00005.html</a></p>
<p>All openqa ppc64le-hmc-single-disk or ppc64le-hmc-4disk test suites fail in bootloader_start or bootloader with the following error message<br>
<a href="https://openqa.suse.de/tests/4543002/modules/bootloader_start/steps/6" class="external">bootloader_start</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since 9th of August (<a href="https://openqa.suse.de/tests/4541148" class="external">https://openqa.suse.de/tests/4541148</a>)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good 6th of August (<a href="https://openqa.suse.de/tests/4528757" class="external">https://openqa.suse.de/tests/4528757</a>)</p>
openQA Project - action #69313 (Resolved): When using refspec for ppc for a particular job, PRODU...https://progress.opensuse.org/issues/693132020-07-24T10:25:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>While attempting to run refspecs for test "autoyast_reinstall" job on various architectures, I faced an issue specifically on ppc64le. The PRODUCTDIR needs to be set manually like following: <br>
<code>openqa-clone-custom-git-refspec https://github.com/sofiasyria/os-autoinst-distri-opensuse/tree/ac68803 https://openqa.suse.de/tests/4427385 ASSET_1="04427383-autoinst.xml" YAML_TEST_DATA=test_data/yast/autoyast_reinstall/autoyast_reinstall_ppc64le-hmc.yaml PRODUCTDIR="os-autoinst-distri-opensuse/products/sle"</code></p>
<p>If the above command is used without the PRODUCTDIR specification, the variable gets the value "os-autoinst-distri-opensuseos-autoinst-distri-opensuse/products/sle" which leads to test failure as here:<br>
<a href="https://openqa.suse.de/tests/4482090" class="external">https://openqa.suse.de/tests/4482090</a></p>
<p>The particular test suite runs for ppc64le-2g, ppc64le-hmc-single-disk, 64bit, s390x and aarch64. For both the ppc machines, the PRODUCTDIR needs to be set manually. For rest of them, it's not necessary.</p>
<p>I have unsuccessfully tried to reproduce the issue with other jobs on ppc.</p>