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 #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 #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 #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 #125252 (Rejected): test fails in openldap_configurationhttps://progress.opensuse.org/issues/1252522023-03-02T06:21:11Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The old module openldap_to389ds.pm was working for opensuse : <a href="https://openqa.opensuse.org/tests/3151861" class="external">https://openqa.opensuse.org/tests/3151861</a><br>
but failing for sle because we cannot install the openldap2 package in the systsem: <a href="https://openqa.suse.de/tests/10565310" class="external">https://openqa.suse.de/tests/10565310</a><br>
It was decided that we will split the openldap_to_389ds module in two, so that the configuration files will be saved before migration, and after migration, the openldap_to_ds command will be used to convert the existing openldap configuration to 389-ds. </p>
<p>PR: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16505" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16505</a></p>
<p>Now, O3 still passes, but we have a new error in SLE:<br>
<a href="http://falafel.suse.cz/tests/939/modules/setup_openldap/steps/53" class="external">openldap_configuration</a><br>
(Note: in the vr, the openldap_configuration was named setup_openldap)</p>
<p>Check if some of the required packages are not installed and change the openldap_configuration.pm module accordingly, so it can pass. In case there are new failures open a new progress ticket.</p>
qe-yam - action #124014 (Rejected): Watch for powerpc KVM yast2_nfs_v3/4_server/client if network...https://progress.opensuse.org/issues/1240142023-02-07T09:09:44Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Due to <a href="https://openqa.suse.de/tests/10441871#next_previous" class="external">sporadic failures</a> for ppc64le architecture, the multimachine test yast2_nfs_v3_server/client was moved to development YaST job group. <br>
We should check if the sporadic failures persist, if any action was taken to fix the ppc64le networking issues, and move the test back to YaST job group or remove it completely. </p>
<p>Relevant ticket: <a href="https://progress.opensuse.org/issues/121555" class="external">https://progress.opensuse.org/issues/121555</a> </p>
qe-yam - action #101370 (Rejected): test fails in yast2_firewall due to recent modification the i...https://progress.opensuse.org/issues/1013702021-10-22T10:34:39Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>According to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1191608" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1191608</a> , eth0 will be set to public by default from now on.<br>
Scope of this ticket is to add the public option, create new needle and check if this change doesn't break any previous version tests.</p>
<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-yast2_gui@64bit fails in<br>
<a href="https://openqa.suse.de/tests/7487123/modules/yast2_firewall/steps/47" class="external">yast2_firewall</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/7087278" class="external">31.2</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=yast2_gui&version=15-SP4" class="external">latest</a></p>
qe-yam - action #101163 (Rejected): test fails in yast2_lan_restart_vlanhttps://progress.opensuse.org/issues/1011632021-10-19T08:12:44Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>The module fails because after opening yast network settings and closing without making any actual changes, it spots in logs a wicked reload that was not supposed to happen. Check if the logs are corresponding to the action or they are older logs that should not be parsed at the specific point. Check with YaST team if there are any relevant changes.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-aarch64-yast2_gui@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/7461525/modules/yast2_lan_restart_vlan/steps/54" class="external">yast2_lan_restart_vlan</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/7137082" 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=aarch64&distri=sle&flavor=Online&machine=aarch64&test=yast2_gui&version=15-SP4" class="external">latest</a></p>
qe-yam - action #99354 (Rejected): test fails in root_simple_pwdhttps://progress.opensuse.org/issues/993542021-09-27T14:45:47Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Bug <a href="https://bugzilla.suse.com/show_bug.cgi?id=1190102" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1190102</a> was rejected so we need to fix the sporadic failure occurring due to timing. The module expects the root password page, but it may occur that the page for user simple password is still in display, after accepting the warning for simple password.</p>
<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-autoyast_y2_firstboot@64bit fails in<br>
<a href="https://openqa.suse.de/tests/7218639/modules/root_simple_pwd/steps/2" class="external">root_simple_pwd</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Smoke test for YaST2 Firstboot module, basically same as yast2_firstboot test suite. Test pre-defined autoyast profile, which enables YaST2 Firstboot during system deployment. SUT should boot to YaST2 Firstboot wizard after reboot. Test goes through all Firstboot tabs, configure root and user accounts. SUT should end up in GDM screen after exiting YaST2 Firstboot.</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/7218639" class="external">39.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/7203756" class="external">38.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=64bit&test=autoyast_y2_firstboot&version=15-SP4" class="external">latest</a></p>
qe-yam - action #99351 (Rejected): test fails in firstboot_finish_setuphttps://progress.opensuse.org/issues/993512021-09-27T12:23:30Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>It's not clear by the code in lib/YaST/Firstboot/ConfigurationCompletedController.pm what is exactly checked in order to determine if the page finish page is shown. The bellow failure is not justified as the finish page is displayed as expected. Investigate and make the page check more reliable and stable.</p>
<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-yast2_firstboot_custom_textmode@64bit fails in<br>
<a href="https://openqa.suse.de/tests/7219556/modules/firstboot_finish_setup/steps/2" class="external">firstboot_finish_setup</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Smoke test for YaST2 Firstboot module, boot an existing image, enable YaST2 Firstboot after successful login to the SUT and reboot again. SUT should boot to YaST2 Firstboot wizard, go through all Firstboot tabs, configure root and user accounts. SUT should end up in GDM screen after exiting YaST2 Firstboot.</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/7126658" 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=Online&machine=64bit&test=yast2_firstboot_custom_textmode&version=15-SP4" class="external">latest</a></p>
qe-yam - action #98556 (Rejected): test fails in consoletest_finish for minimalx Desktophttps://progress.opensuse.org/issues/985562021-09-13T13:09:29Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Function ensure_unlocked_desktop in lib/x11utils.pm does not properly work for minimalx desktop as in line 135 it uses assert screen for typed password, which doesn't make sense for minimalx (the typed password is not visible on screen). Instead of modifying the particular code, we could implement in ensure_unlocked_desktop, function handle_password_prompt from lib/susedistribution.pm which already works for minimalx and that way we can avoid having duplicate code.</p>
<p>The failure is from test runs for future test enabling, the module is not yet enabled for any test with minimalx Desktop.<br>
<a href="https://openqa.suse.de/tests/7043920/modules/consoletest_finish/steps/20" class="external">consoletest_finish</a></p>
qe-yam - action #97328 (Rejected): test fails in yast2_lan_restart_*https://progress.opensuse.org/issues/973282021-08-22T15:05:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After renaming a device, the network should be reloaded: <a href="https://progress.opensuse.org/issues/64761" class="external">https://progress.opensuse.org/issues/64761</a>. After opening settings and closing without making any changes, there should not be restart or reload. The modules seem to either have wrong expectations or perform the wrong actions. We see these failures for all archs that the modules run.</p>
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Online-ppc64le-yast2_gui@ppc64le-2g fails in<br>
<a href="https://openqa.suse.de/tests/6914088/modules/yast2_lan_restart_bridge/steps/56" class="external">yast2_lan_restart_bridge</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/6907845" class="external">26.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=Online&machine=ppc64le-2g&test=yast2_gui&version=15-SP4" class="external">latest</a></p>
qe-yam - action #91136 (Rejected): Textmode test suite fails for s390x-kvmhttps://progress.opensuse.org/issues/911362021-04-14T13:20:42Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After implementing libyui for the mentioned tests, there is a strange network failure. The url that libyui is trying to connect to seems correct but the app doesn't connect successfully. The failure is the same for all machines:<br>
<a href="https://openqa.suse.de/tests/5814857#step/bootloader_start/30" class="external">https://openqa.suse.de/tests/5814857#step/bootloader_start/30</a> </p>
<p>Similar issue is visible on powerVM: <a class="issue tracker-4 status-5 priority-5 priority-high3 closed" title="action: [timeboxed:16h] libyui REST API cannot be accessed on powerVM (Closed)" href="https://progress.opensuse.org/issues/90776">#90776</a>, so might be that it's same issue for the both backends</p>
qe-yam - action #89494 (Rejected): Validate editing partition for mount_by optionshttps://progress.opensuse.org/issues/894942021-03-04T12:45:10Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In ticket : <a href="https://progress.opensuse.org/issues/88533" class="external">https://progress.opensuse.org/issues/88533</a> a new test scenario "fstab_mount_by" was implemented , for mount_by option validation after installation. The scenario covers editing the fstab options for new partitions added in the partitioning. </p>
<p>The objective of this follow-up ticket is to extend coverage and perform installation on the image created by "fstab_mount_by" scenario and, while partitioning, edit the existing partitions, check if the existing mount_by option for each partition is recognized correctly by the expert partitioner and validate after installation if the new options take effect correctly.</p>
qe-yam - action #81248 (Rejected): test fails in snapshots_small_root on aarch64https://progress.opensuse.org/issues/812482020-12-21T13:42:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The warning for small root partition is successfully handled, but the cancellation of the partitioning is not taking effect, so the module is expecting for a second warning, related to losing changes, tries to press "yes" and receives the following error:</p>
<pre><code>Test died: Timed out:
Not Found
{ "error" : "Widget not found" }
http://localhost:39106/v1/widgets?action=press&id=yes at /var/lib/openqa/cache/openqa.suse.de/tests/sle/lib/YuiRestClient/Http/HttpClient.pm line 35.
</code></pre>
<p>Seems that the "cancel" button is not pressed.</p>
<p>openQA test in scenario sle-15-SP3-Online-aarch64-btrfs+warnings@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/5201644/modules/snapshots_small_root/steps/15" class="external">snapshots_small_root</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Test for feature with insufficient disk space on btrfs partition with snapshots.</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/5194534" class="external">109.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/5162094" class="external">102.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=btrfs%2Bwarnings&version=15-SP3" class="external">latest</a></p>