openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-01-24T14:09:51ZopenSUSE Project Management Tool
Redmine qe-yam - action #154183 (Rejected): Yam support images not being replaced by latest runshttps://progress.opensuse.org/issues/1541832024-01-24T14:09:51Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>While working on <a href="https://progress.opensuse.org/issues/153043" class="external">poo#153043</a> , the realization that the published images on osd are not replaced by the latest runs of teh yam support images tests occurred. This can be a problem as it invalidates all the effort of minimizing patch time.</p>
<p><strong>Acceptance criteria</strong></p>
<ul>
<li>Make sure that a test publishing an image under the same name can replace an existing one.</li>
<li>Check if the above applies for all archs.</li>
</ul>
<p>Proposal: this can be done by creating a dev job group, publish some images gnome images under a certain name and replace them with textmode images but keeping the same PUBLISH_HDD name and then proceed to see if they where replaced by booting into them (either manually or by using some other openqa test). Any other way of verification would be acceptable as well.</p>
qe-yam - action #153967 (Rejected): Check and update bugs linked with soft failures in detect_yas...https://progress.opensuse.org/issues/1539672024-01-19T13:22:49Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently the <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=detect_yast2_failures_dev%40sofiasyria%2Fos-autoinst-distri-opensuse%23y2log_fail&version=15-SP6" class="external">detect_yast2_failures</a> test suite is soft failing for a number of reported bugs that have beed confirmed but are idle for a long time. We should comment on each bug report to check with the developers and see if the error messages are just noise to be ignored, or we should keep the soft failure. (See example <a href="https://bugzilla.suse.com/show_bug.cgi?id=1167248#c18" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1167248#c18</a> )<br>
In case we can safely ignore the failure, it should be linked with the trello page for y2log cleanup.</p>
<p>Related ticket : <a href="https://progress.opensuse.org/issues/153085" class="external">https://progress.opensuse.org/issues/153085</a></p>
qe-yam - action #153154 (New): Replace different arch yaml schedules with one for continuous migr...https://progress.opensuse.org/issues/1531542024-01-05T10:36:25Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Test offline_sle12sp5_sles15sp4_sles15sp_latest_*_ph0 from migration_miscellaneous job group has a dedicated yaml schedule for each arch. The schedules are quite similar and could be replaced by one, if properly written. The differences are mainly the bootloader (bootloader_start can replace all), isosize module for aarch64 and ppc64le and for s390x reconnect_mgmt_console module instead of grub_test module. Files:<br>
schedule/migration/migration_offline_scc_deregistration_x86_64.yaml <br>
schedule/migration/migration_offline_scc_deregistration_s390x.yaml<br>
schedule/migration/migration_offline_scc_deregistration_aarch64.yaml<br>
schedule/migration/migration_offline_scc_deregistration_ppc64le.yaml </p>
<p><strong>Acceptance criteria</strong></p>
<ul>
<li>Unify the above files to one</li>
<li>Research which archs should include isosize module (preferably all or none)</li>
<li>Edit the Job group yaml to point to the new schedule.</li>
</ul>
qe-yam - action #133616 (Rejected): agama full_disk_encryption and lvm tests fail due to changes...https://progress.opensuse.org/issues/1336162023-08-01T11:49:49Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The latest changes in Agama live image is that only dolomite is available for installation, no ALM micro or server. Therefore, we need to adjust our playwright test lvm and full_disk_encryption that currently fail. The Tumbleweed test will remain as is, because tumbleweed is still available.</p>
<p><a href="https://openqa.opensuse.org/tests/overview?distri=alp&version=agama-2.1-staging&build=2.17&groupid=96" class="external">https://openqa.opensuse.org/tests/overview?distri=alp&version=agama-2.1-staging&build=2.17&groupid=96</a></p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario alp-agama-2.1-staging-agama-live-default-Playwright-x86_64-agama_dolomite_full_disk_encryption@64bit-2G fails in<br>
<a href="https://openqa.opensuse.org/tests/3470423/modules/agama_full_disk_encryption/steps/6" class="external">agama_full_disk_encryption</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.opensuse.org/tests/3468486" class="external">2.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.opensuse.org/tests/3457233" class="external">2.5</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.opensuse.org/tests/latest?arch=x86_64&distri=alp&flavor=agama-live-default-Playwright&machine=64bit-2G&test=agama_dolomite_full_disk_encryption&version=agama-2.1-staging" class="external">latest</a></p>
qe-yam - action #133373 (Rejected): Tidy up migration yaml job groups with yamllinthttps://progress.opensuse.org/issues/1333732023-07-26T10:24:05Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The <a href="https://gitlab.suse.de/coolgw/wegao-test/-/tree/master/JobGroups" class="external">migration job group yamls</a>, if parsed with yamllint, show a lot of errors. It's better to tidy them up and re-order the test suites for each product and architecture according to name alphabetical order, for better readability.</p>
<p>Note: yamllint is available in opensuse repo as python311-yamllint package. Documentation <a href="https://yamllint.readthedocs.io/en/stable/" class="external">here</a></p>
qe-yam - action #130360 (Rejected): addon_products_via_SCC_yast2 in SLE12SP4/5 attempts to re-reg...https://progress.opensuse.org/issues/1303602023-06-05T07:38:46Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In Yast Maintenance Dev job group The module addon_products_via_SCC_yast2 tries to register an already registered system. We should check first the registration status and proceed if needed. </p>
<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-x86_64-mru-iscsi_server_normal_auth_backstore_hdd_dev@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11253708/modules/addon_products_via_SCC_yast2/steps/17" class="external">addon_products_via_SCC_yast2</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>. iSCSI multimachine test suite with manually configure the static network between SUTs. Authentication: 2way normal authentication, discovery authentication is not configured Backstore: plain drive Test data are included in enclosed yaml file. </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/10991058" class="external">20230426-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=Server-DVD-Updates&machine=64bit&test=mru-iscsi_server_normal_auth_backstore_hdd_dev&version=12-SP5" class="external">latest</a></p>
qe-yam - action #130357 (Rejected): test fails in addon_products_via_SCC_yast2 SLE15SP2https://progress.opensuse.org/issues/1303572023-06-05T07:30:52Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In Yast Maintenance Dev job group SLE15SP2 some iscsi tests fail as it seems that the HDD_1 image does not have properly configured network, so when the module addon_products_via_SCC_yast2 attempts unsuccessfully to reach the scc server. The successful iscsi tests, do not have this module in their schedule. We should check if the server is available and fix the configuration in the parent test <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=create_hdd_yast_maintenance_desktop&version=15-SP2" class="external">create_hdd_yast_maintenance_desktop</a> accordingly. We also need to make sure that the rest of the dependent tests don't fail after the new configuration.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Server-DVD-Updates-x86_64-mru-iscsi_server_normal_auth_backstore_fileio_dev@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11253956/modules/addon_products_via_SCC_yast2/steps/28" class="external">addon_products_via_SCC_yast2</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>. iSCSI multimachine test suite with manually configure the static network between SUTs. Authentication: 2way normal authentication, discovery authentication is not configured Backstore: fileIO Test data are included in enclosed yaml file. </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/10990206" class="external">20230426-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=Server-DVD-Updates&machine=64bit&test=mru-iscsi_server_normal_auth_backstore_fileio_dev&version=15-SP2" class="external">latest</a></p>
qe-yam - action #130345 (Rejected): test fails during upgrade from SLE15SP3 due to LTSS being act...https://progress.opensuse.org/issues/1303452023-06-05T05:47:33Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In Yast Maintenance Dev job group SLE 15 SP3, this test attempts to migrate from 15SP3 to 15SP5 without deactivating first the LTSS, which is not available for the target version. We need to deactivate it before proceeding to upgrade.</p>
<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-autoupgrade_sle15sp3+1_scc_we_sdk_basesys_wsm_srv_desk_lgm_contm_pcm_def_full@64bit fails in<br>
<a href="https://openqa.suse.de/tests/11253765/modules/installation/steps/5" class="external">installation</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>.<br>
Autoyast migration between one hdd with unreleased maintenance updates installed to newer SLE version. </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/10990421" class="external">20230426-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=Server-DVD-Updates&machine=64bit&test=autoupgrade_sle15sp3%2B1_scc_we_sdk_basesys_wsm_srv_desk_lgm_contm_pcm_def_full&version=15-SP3" class="external">latest</a></p>
qe-yam - action #128768 (Rejected): test fails in system_prepare because sle-module-python2 is no...https://progress.opensuse.org/issues/1287682023-05-05T08:08:19Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The sle-module-python2 is registered for the sp3 system prior the upgrade, but after upgrade it's not there. We need to investigate if our expectations make sense after the recent python upgrades for SLE 15 SP5 and fix the test accordingly.</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_sles15sp3_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full@ppc64le-spvm fails in<br>
<a href="https://openqa.suse.de/tests/11039784/modules/system_prepare/steps/17" class="external">system_prepare</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/10658986" 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_sles15sp3_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full&version=15-SP5" class="external">latest</a></p>
qe-yam - action #128606 (Rejected): [sporadic] test fails in install_servicehttps://progress.opensuse.org/issues/1286062023-05-03T13:35:08Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After install_service module is attempting to install,enable and start vsftpd, it runs the /etc/bash/bash.local and we expect it to return no error ( $? = 0 ). Even though the script doesn't seem to fail, openqa is reporting <a href="https://openqa.suse.de/tests/11022849#step/install_service/197" class="external">failure</a> . Find the root cause and provide solution , in case there are false failures reported by openqa.</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-SLE12-SPx-ppc64le-offline_sles12sp5_pscc_sdk-lp-asmm-contm-lgm-tcm-wsm-pcm_all_full@ppc64le-2g fails in<br>
<a href="https://openqa.suse.de/tests/10918493/modules/install_service/steps/199" class="external">install_service</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/10905871" class="external">90.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/10849460" class="external">88.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=ppc64le&distri=sle&flavor=Regression-on-Migration-from-SLE12-SPx&machine=ppc64le-2g&test=offline_sles12sp5_pscc_sdk-lp-asmm-contm-lgm-tcm-wsm-pcm_all_full&version=15-SP5" class="external">latest</a></p>
openQA Project - action #127739 (New): ASSET_1 gets outdated value when using openqa-clone-custom...https://progress.opensuse.org/issues/1277392023-04-17T07:59:50Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>When using openqa-clone-custom-git-refspec in order to clone a job, the value of ASSET_1 or any other ASSET get's the value from settings. But usually, the ASSET uploaded after the original job is run, gets another file name. For example, if ASSET_1=dev_tools.dud in settings, the original job will have uploaded ASSET_1=10931294-dev_tools.dud and the cloned job will fail because it cannot find dev_tools.dud with error:<br>
[info] [<a class="issue tracker-4 status-5 priority-4 priority-default closed" title="action: Breadcrumbs (Closed)" href="https://progress.opensuse.org/issues/555">#555</a>] Downloading "dev_tools.dud" from "<a href="http://openqa.suse.de/tests/10932003/asset/other/dev_tools.dud" class="external">http://openqa.suse.de/tests/10932003/asset/other/dev_tools.dud</a>"<br>
[info] [<a class="issue tracker-4 status-5 priority-4 priority-default closed" title="action: Breadcrumbs (Closed)" href="https://progress.opensuse.org/issues/555">#555</a>] Download of "/var/lib/openqa/cache/openqa.suse.de/dev_tools.dud" failed: 404 Not Found</p>
<p>In order to have a successful cloning, ASSET_1 has to be manually set to ASSET_1=10931294-dev_tools.dud while typing the refspec command.<br>
#openqa-clone-custom-git-refspec <a href="https://github.com/sofiasyria/os-autoinst-distri-opensuse/tree/master" class="external">https://github.com/sofiasyria/os-autoinst-distri-opensuse/tree/master</a> <a href="https://openqa.suse.de/tests/10931666" class="external">https://openqa.suse.de/tests/10931666</a> ASSET_1='10931294-dev_tools.dud'</p>
<p>It would be useful to automate the above process. </p>
qe-yam - action #90350 (Rejected): Add yast2_system_settings for ncurseshttps://progress.opensuse.org/issues/903502021-03-19T11:08:21Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Module yast2_system_settings is designed to run on gui, using libyui. The coverage can be extended for ncurses too. We can write a second module. The basic libyui code will be the same, but the x11 handling won't be needed. </p>
openQA Project - action #87725 (New): MULTIPATH backend variable doesn't set HDDMODEL for aarch64https://progress.opensuse.org/issues/877252021-01-13T16:48:15Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>According to the definition of the variable, if MULTIPATH=1:<br>
"Add HDD drives as multipath devices. Override HDDMODEL to virtio-scsi-pci"</p>
<p>That indeed happens when used on 64bit or ppc64le, but for aarch64, HDDMODEL remains to default value "virtio-blk-device". Test fails with error: "Device 'virtio-blk-device' can't go on SCSI bus". In order for the test to work, HDDMODEL needs to be set to "scsi-hd".</p>
openQA Tests - action #72184 (New): [virtualization][y] Select_console fails sporadically for svi...https://progress.opensuse.org/issues/721842020-10-01T15:10:12Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>There is a sporadic failure of approximately 17%, for prepare_data module for yast2_gui test suite. The SUT seems to be freezing with black screen, when select_console is called.</p>
<p>It is notable that by simplifying the module to:</p>
<pre><code>sub run {
select_console 'root-console';
}
1;
</code></pre>
<p>it still displays the same percentage of failure.</p>
<p>The issue is not present in case of using xterm and chvt 6.</p>
<pre><code>sub run {
x11_start_program('xterm');
wait_still_screen(5);
become_root;
assert_script_run "chvt 6";
assert_screen "tty6-selected";
}
1;
</code></pre>
<p>Unfortunately, the logs are not helpful. When successfully switching to tty6, the autoinst logs contain:<br>
[2020-09-30T17:28:05.896 CEST] [debug] <<< testapi::select_console(testapi_console="root-console")<br>
....<br>
[ 82.601276] <strong>systemd[1]: Started Getty on tty6.</strong></p>
<p>Looking at the logs from failed runs, the above phrase is missing.</p>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-yast2_gui@svirt-xen-hvm fails in<br>
<a href="https://openqa.suse.de/tests/4718229/modules/prepare_test_data/steps/3" class="external">prepare_test_data</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p><a href="https://openqa.suse.de/tests/4752856" class="external">48.1</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=x86_64&distri=sle&flavor=Online&machine=svirt-xen-hvm&test=yast2_gui&version=15-SP3" class="external">latest</a></p>
qe-yam - action #67669 (Rejected): [y] Enable yast2_lan_restart_bond module for s390xhttps://progress.opensuse.org/issues/676692020-06-03T11:48:56Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Module yast2_lan_restart_bond is part of yast2_gui test suite.<br>
For s390x, it fails due to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1172444" class="external">bug#1172444</a>.</p>
<p>Check of the bug is fixed and modify the test suite schedule, accordingly. </p>