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 #132839 (New): Use Mojo race condition where applicable in future testshttps://progress.opensuse.org/issues/1328392023-07-17T07:51:48Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After PR: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17150" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17150</a><br>
for handling the java license popup during installation settings, it was noticed and commended here <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17150#discussion_r1251875831" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17150#discussion_r1251875831</a> <br>
that we can use race conditions. An available library for openqa workers, here: <a href="https://docs.mojolicious.org/Mojo/Promise" class="external">https://docs.mojolicious.org/Mojo/Promise</a><br>
We could start using this after we investigate the functionality and proper syntax. Ask for help, if needed, in slack channel #discuss-perl</p>
<p><strong>Acceptance criteria</strong></p>
<ul>
<li>Research how we can use it in our testing code, make an example by refactoring existing code.</li>
<li>Make a demo for sharing the knowledge.</li>
</ul>
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 #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 #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 #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>
openQA Infrastructure - action #90692 (Rejected): [sporadic] script_output getting wrong output o...https://progress.opensuse.org/issues/906922021-04-06T07:50:59Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Only for aarch64, the following command:<br>
script_output("cat /proc/sys/kernel/sysrq");<br>
should return the content of the sysrq file, but 10% of the times it returns the character [, which seemt to be taken mistakenly by the serial console.<br>
Failure:<br>
<a href="https://openqa.suse.de/tests/5754960#step/yast2_system_settings/51" class="external">https://openqa.suse.de/tests/5754960#step/yast2_system_settings/51</a></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>
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>
openQA Tests - action #71638 (Rejected): [y] test fails in validate_fs_tablehttps://progress.opensuse.org/issues/716382020-09-22T10:50:02Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>During msdos partitioning, the SWAP partition is selected to be created with UDF instead of swap filesystem. Even though, the screen matches at swap, there is an extra key sent and the result is that SWAP partition is missing and the filesystme validation fails:</p>
<p>[2020-09-22T04:58:41.696 CEST] [debug] <<< testapi::check_screen(mustmatch="partitioning_swap-format-selected", timeout=5)<br>
�[37m[2020-09-22T04:58:42.046 CEST] [debug] load of /var/lib/openqa/cache/openqa.suse.de/tests/sle/products/sle/needles/partitioning_swap-format-selected-20200217.png took 0.35 seconds<br>
�[0m�[32m[2020-09-22T04:58:44.670 CEST] [debug] >>> testapi::_handle_found_needle: found partitioning_swap-format-selected-20200121, similarity 1.00 @ 368/351<br>
�[0m[2020-09-22T04:58:44.670 CEST] [debug] tests/installation/partitioning/msdos_partition_table.pm:27 called Installation::Partitioner::LibstorageNG::v4::ExpertPartitionerController::add_partition_msdos -> lib/Installation/Partitioner/LibstorageNG/v4/ExpertPartitionerController.pm:168 called Installation::Partitioner::LibstorageNG::v4::ExpertPartitionerController::add_new_partition -> lib/Installation/Partitioner/LibstorageNG/v4/ExpertPartitionerController.pm:180 called Installation::Partitioner::AbstractExpertPartitionerController::_set_partition_options -> lib/Installation/Partitioner/AbstractExpertPartitionerController.pm:114 called Installation::Partitioner::FormattingOptionsPage::select_mount_device_radiobutton -> lib/Installation/Partitioner/FormattingOptionsPage.pm:96 called testapi::assert_screen<br>
[2020-09-22T04:58:44.670 CEST] [debug] <<< testapi::assert_screen(mustmatch="partition-format", timeout=30)<br>
�[32m[2020-09-22T04:58:44.791 CEST] [debug] >>> testapi::_handle_found_needle: found partitioning-format-20160504, similarity 1.00 @ 275/273<br>
�[0m[2020-09-22T04:58:44.792 CEST] [debug] tests/installation/partitioning/msdos_partition_table.pm:27 called Installation::Partitioner::LibstorageNG::v4::ExpertPartitionerController::add_partition_msdos -> lib/Installation/Partitioner/LibstorageNG/v4/ExpertPartitionerController.pm:168 called Installation::Partitioner::LibstorageNG::v4::ExpertPartitionerController::add_new_partition -> lib/Installation/Partitioner/LibstorageNG/v4/ExpertPartitionerController.pm:180 called Installation::Partitioner::AbstractExpertPartitionerController::_set_partition_options -> lib/Installation/Partitioner/AbstractExpertPartitionerController.pm:114 called Installation::Partitioner::FormattingOptionsPage::select_mount_device_radiobutton -> lib/Installation/Partitioner/FormattingOptionsPage.pm:97 called testapi::send_key<br>
[2020-09-22T04:58:44.792 CEST] [debug] <<< testapi::send_key(key="alt-o", do_wait=0, wait_screen_change=0)</p>
<p><a href="https://openqa.suse.de/tests/4711745#step/msdos_partition_table/86">https://openqa.suse.de/tests/4711745#step/msdos_partition_table/86</a></p>
<p><a href="https://openqa.suse.de/tests/4711745/modules/validate_fs_table/steps/35">https://openqa.suse.de/tests/4711745/modules/validate_fs_table/steps/35</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Installation with MSDOS partition table.</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/4686599" class="external">33.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/4636012" class="external">23.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=Online&machine=ppc64le&test=msdos&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #68764 (Rejected): [functional][y] yast2_gui@svirt-xen-hvm fails when retri...https://progress.opensuse.org/issues/687642020-07-08T12:25:12Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Test suite yast2_gui@svirt-xen-hvm is set to START_AFTER_TEST=create_hdd_gnome. When a new build is triggering all test suites, create_hdd_gnome@svirt-xen-hvm fails and yast2_gui@svirt-xen-hvm is skipped as expected. <br>
<a href="https://openqa.suse.de/tests/4342327#dependencies" class="external">https://openqa.suse.de/tests/4342327#dependencies</a></p>
<p>If we trigger yast2_gui@svirt-xen-hvm, it would be expected that create_hdd_gnome@svirt-xen-hvm should be triggered as well but this doesn't happen, resulting in failure as the dependent test can't find HDD_1.<br>
<a href="https://openqa.suse.de/tests/4424999" class="external">https://openqa.suse.de/tests/4424999</a></p>
<pre><code>[error] [pid:6204] Failed to download SLES-15-SP2-x86_64-Build209.2@svirt-xen-hvm-gnome.qcow2 to /var/lib/openqa/cache/openqa.suse.de/SLES-15-SP2-x86_64-Build209.2@svirt-xen-hvm-gnome.qcow2
</code></pre> openQA Tests - action #67672 (Rejected): [functional][y] Extend coverage of yast2_gui test moduleshttps://progress.opensuse.org/issues/676722020-06-03T12:02:54Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>There are some modules on the test that fail, due to needle mismatch. Currently the modules are removed from the schedule for the architectures that fail.</p>
<p>s390-> yast2_datetime, yast2_bootloader, yast2_lang <br>
xen-hvm -> yast2_network_settings<br>
ppc -> yast2_bootloader, yast2_lang<br>
aarch64 -> yast2_bootloader</p>
<p>Create the necessary needles and enable the modules on the yast2_gui schedule. For ppc and aarch64, possible the same needles created for s390 would work.</p>
openQA Tests - action #63922 (Rejected): [functional][y] Sporadic failure of mediacheck module in...https://progress.opensuse.org/issues/639222020-02-27T15:14:42Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>After build 131.1, it is observed that while module "mediacheck" runs on hyperV, "Check installation media" is selected, but instead of actually checking the media, test goes back to grub menu and selects "installation". Test fails when warning for Beta distribution appears, after timing out. </p>
<p><a href="https://openqa.suse.de/tests/3928000#step/mediacheck/11" class="external">https://openqa.suse.de/tests/3928000#step/mediacheck/11</a></p>
<p>The issue happens sporadically.</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/3915652" class="external">143.1</a> (or more recent)</p>