openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-02-27T17:27:27ZopenSUSE Project Management Tool
Redmine openQA Project - action #156169 (New): Automatically validate ay-openqa-worker.xml.erbhttps://progress.opensuse.org/issues/1561692024-02-27T17:27:27Zybonatakisioannis.bonatakis@suse.com
<p><a href="https://github.com/os-autoinst/openQA/blob/master/contrib/ay-openqa-worker.xml.erb" class="external">https://github.com/os-autoinst/openQA/blob/master/contrib/ay-openqa-worker.xml.erb</a> is used for openqa workers. <br>
This is passed as-is to the autoyast and seems to work.<br>
But when generate the xml manual</p>
<ul>
<li>Either TW or Leap</li>
<li>install autoyast2</li>
<li>Run <code>sudo yast2 autoyast check-profile filename=ay-openqa-worker.xml.erb output=result.xml run-scripts=true run-erb=true</code></li>
</ul>
<p>Then complains for:</p>
<ul>
<li>firewall configuration</li>
<li>failure to run the scripts</li>
</ul>
<p>I am not sure about the requirements about the later, but firewall should be easy to address.</p>
openQA Project - action #129172 (Resolved): PXEBOOT doesnt set bootindex on aarch64https://progress.opensuse.org/issues/1291722023-05-12T06:30:55Zybonatakisioannis.bonatakis@suse.com
<p>Digging into the qemu backend seems that the bits to boot a machine (aarch4) from network is missing.</p>
<ul>
<li>first <code>BOOTFROM</code> doesnt support n options
<a href="https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L663">https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L663</a></li>
<li><code>PXEBOOT</code> doesnt set the booting order at all
<a href="https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L713">https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L713</a>
<a href="https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L892">https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L892</a></li>
</ul>
<p>the os-autoinst output looks like that</p>
<pre><code>/usr/bin/qemu-system-aarch64 -device virtio-gpu-pci,edid=on,xres=1024,yres=768 -chardev ringbuf,id=serial0,logfile=serial0,logappend=on -serial chardev:serial0 -audiodev none,id=snd0 -device intel-hda -device hda-output,audiodev=snd0 -m 4096 -machine virt,usb=off,gic-version=3,its=off -cpu host -netdev tap,id=qanet0,ifname=tap2,script=no,downscript=no -device virtio-net,netdev=qanet0,mac=52:54:00:12:05:02 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -device nec-usb-xhci -device usb-tablet -device usb-kbd -smp 1 -enable-kvm -no-shutdown -vnc :93,share=force-shared -device virtio-serial -chardev pipe,id=virtio_console,path=virtio_console,logfile=virtio_console.log,logappend=on -device virtconsole,chardev=virtio_console,name=org.openqa.console.virtio_console -chardev pipe,id=virtio_console_user,path=virtio_console_user,logfile=virtio_console_user.log,logappend=on -device virtconsole,chardev=virtio_console_user,name=org.openqa.console.virtio_console_user -chardev socket,path=qmp_socket,server=on,wait=off,id=qmp_socket,logfile=qmp_socket.log,logappend=on -qmp chardev:qmp_socket -S -device virtio-scsi-pci,id=scsi0 -blockdev driver=file,node-name=hd0-file,filename=/var/lib/openqa/pool/3/raid/hd0,cache.no-flush=on -blockdev driver=qcow2,node-name=hd0,file=hd0-file,cache.no-flush=on,discard=unmap -device virtio-blk-device,id=hd0-device,drive=hd0,serial=hd0 -blockdev driver=file,node-name=cd0-overlay0-file,filename=/var/lib/openqa/pool/3/raid/cd0-overlay0,cache.no-flush=on -blockdev driver=qcow2,node-name=cd0-overlay0,file=cd0-overlay0-file,cache.no-flush=on,discard=unmap -device scsi-cd,id=cd0-device,drive=cd0-overlay0,serial=cd0 -drive id=pflash-code-overlay0,if=pflash,file=/var/lib/openqa/pool/3/raid/pflash-code-overlay0,unit=0,readonly=on -drive id=pflash-vars-overlay0,if=pflash,file=/var/lib/openqa/pool/3/raid/pflash-vars-overlay0,unit=1
</code></pre>
<p>where bootindex is missing</p>
openQA Project - action #126032 (Resolved): iso posts do not start all the children chainhttps://progress.opensuse.org/issues/1260322023-03-15T04:34:31Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Not all the child jobs are scheduled from the parent.</p>
<p>I noticed that in the last two build IIRC. For some reason that occurred in this specific test.<br>
The rest of the multijobs looks to start as expected.<br>
However a few examples i tried out reproduce the problem. </p>
<p><a href="#" onclick="$('#collapse-e21c61c1-show, #collapse-e21c61c1-hide').toggle(); $('#collapse-e21c61c1').fadeToggle(150);; return false;" id="collapse-e21c61c1-show" class="icon icon-collapsed collapsible">iso posts example with _SKIP_CHAINED_DEPS</a><a href="#" onclick="$('#collapse-e21c61c1-show, #collapse-e21c61c1-hide').toggle(); $('#collapse-e21c61c1').fadeToggle(150);; return false;" id="collapse-e21c61c1-hide" class="icon icon-expanded collapsible" style="display:none;">iso posts example with _SKIP_CHAINED_DEPS</a><div id="collapse-e21c61c1" class="collapsed-text" style="display:none;"><p>openqa-cli api --pretty --osd -X POST isos ISO=SLE-15-SP5-Online-aarch64-Build80.1-Media1.iso DISTRI=sle VERSION=15-SP5 FLAVOR=Online ARCH=aarch64 BUILD=80.1 TEST=hpc_BETA_mpich_mpi_supportserver _GRPOUP_ID=130<br>
{<br>
"count" : 2,<br>
"failed" : [],<br>
"ids" : [<br>
10698182,<br>
10698183<br>
],<br>
"scheduled_product_id" : 1768408<br>
}</p>
</div></p>
<p><a href="#" onclick="$('#collapse-551ff268-show, #collapse-551ff268-hide').toggle(); $('#collapse-551ff268').fadeToggle(150);; return false;" id="collapse-551ff268-show" class="icon icon-collapsed collapsible">iso posts example with _SKIP_CHAINED_DEPS</a><a href="#" onclick="$('#collapse-551ff268-show, #collapse-551ff268-hide').toggle(); $('#collapse-551ff268').fadeToggle(150);; return false;" id="collapse-551ff268-hide" class="icon icon-expanded collapsible" style="display:none;">iso posts example with _SKIP_CHAINED_DEPS</a><div id="collapse-551ff268" class="collapsed-text" style="display:none;"><p>openqa-cli api --pretty --osd -X POST isos ISO=SLE-15-SP5-Online-aarch64-Build80.1-Media1.iso DISTRI=sle VERSION=15-SP5 FLAVOR=Online ARCH=aarch64 BUILD=80.1 TEST=hpc_BETA_mvapich2_mpi_supportserver _GRPOUP_ID=130 _SKIP_CHAINED_DEPS=1<br>
{<br>
"count" : 1,<br>
"failed" : [],<br>
"ids" : [<br>
10698186<br>
],<br>
"scheduled_product_id" : 1768410</p>
</div></p>
<p>All children has <code>PARALLEL_WITH=hpc_BETA_mpich_mpi_supportserver</code> on Test Suites</p>
<p>openQA test in scenario sle-15-SP5-Online-x86_64-hpc_BETA_mpich_mpi_supportserver@64bit fails in<br>
<a href="https://openqa.suse.de/tests/10691528/modules/wait_children/steps/7" class="external">wait_children</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Basic tests of mpich with CPU count=2. Maintainer: schlad <a href="mailto:schlad@suse.de">schlad@suse.de</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/10691528" class="external">80.1</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p><a href="#" onclick="$('#collapse-f659d256-show, #collapse-f659d256-hide').toggle(); $('#collapse-f659d256').fadeToggle(150);; return false;" id="collapse-f659d256-show" class="icon icon-collapsed collapsible">should look like</a><a href="#" onclick="$('#collapse-f659d256-show, #collapse-f659d256-hide').toggle(); $('#collapse-f659d256').fadeToggle(150);; return false;" id="collapse-f659d256-hide" class="icon icon-expanded collapsible" style="display:none;">should look like</a><div id="collapse-f659d256" class="collapsed-text" style="display:none;"><p>openqa-cli api --pretty --osd -X POST isos ISO=SLE-15-SP5-Online-x86_64-Build80.1-Media1.iso DISTRI=sle VERSION=15-SP5 FLAVOR=Online ARCH=x86_64 BUILD=80.1 TEST=hpc_BETA_mpich_mpi_supportserver,hpc_BETA_mpich_mpi_slave01,hpc_BETA_mpich_mpi_slave00,hpc_BETA_mpich_mpi_master _GRPOUP_ID=130 _SKIP_CHAINED_DEPS=1<br>
{<br>
"count" : 4,<br>
"failed" : [],<br>
"ids" : [<br>
10698191,<br>
10698192,<br>
10698193,<br>
10698194<br>
],<br>
"scheduled_product_id" : 1768412<br>
}</p>
</div><br>
Last good: <a href="https://openqa.suse.de/tests/10687724" class="external">80.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=hpc_BETA_mpich_mpi_supportserver&version=15-SP5" class="external">latest</a></p>
openQA Project - action #109292 (Resolved): OSD is missing x86_64 jobs duplicate key value violat...https://progress.opensuse.org/issues/1092922022-03-31T07:57:01Zybonatakisioannis.bonatakis@suse.com
<p>With the last two (117.1,118.3) or three builds x86_64 jobs are missing.</p>
<p>The very first time there was a dependency circle issue with one of the job group yaml. That found to prevent the scheduling. However the jobs are keep missing even after the correction and the scheduling looks to work without problem after manual intervention.</p>
openQA Project - action #107878 (Resolved): number of failed job provides wrong value on the buil...https://progress.opensuse.org/issues/1078782022-03-04T11:13:23Zybonatakisioannis.bonatakis@suse.com
<p><a href="https://openqa.suse.de/group_overview/130" class="external">https://openqa.suse.de/group_overview/130</a> display 2 failed jobs for build101.1.</p>
<p>if you press on the failed area of the bar, the <code>Test result overview</code> shows only one failed job. Cleaning all the filters i see that the only other job which was not successful is one failed as <code>timeout_exceeded</code>. </p>
<p>So either the <u>failed area</u> should enabled the <code>Timeout exceeded</code>(or any other flag) or it bar should point out only the actual failed jobs.</p>
openQA Tests - action #107395 (Resolved): [HPC] zypper returns error code 107 in slurm_masterhttps://progress.opensuse.org/issues/1073952022-02-23T19:04:58Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<pre><code>(4/6) Installing: twopence-0.4.2-3.d_t.22.x86_64 [.
warning: /var/cache/zypp/packages/devel_tools/x86_64/twopence-0.4.2-3.d_t.22.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 498d5a23: NOKEY
.....
/usr/lib/tmpfiles.d/net-snmp.conf:1: Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly.
/usr/lib/tmpfiles.d/systemd.conf:19: Failed to resolve user 'systemd-network': No such process
/usr/lib/tmpfiles.d/systemd.conf:20: Failed to resolve user 'systemd-network': No such process
/usr/lib/tmpfiles.d/systemd.conf:21: Failed to resolve user 'systemd-network': No such process
/usr/lib/tmpfiles.d/systemd.conf:22: Failed to resolve user 'systemd-network': No such process
warning: %post(twopence-0.4.2-3.d_t.22.x86_64) scriptlet failed, exit status 65
done]
(5/6) Installing: libtwopence0-0.4.2-3.d_t.22.x86_64 [.
warning: /var/cache/zypp/packages/devel_tools/x86_64/libtwopence0-0.4.2-3.d_t.22.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 498d5a23: NOKEY
......done]
(6/6) Installing: twopence-shell-client-0.4.2-3.d_t.22.x86_64 [.
warning: /var/cache/zypp/packages/devel_tools/x86_64/twopence-shell-client-0.4.2-3.d_t.22.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 498d5a23: NOKEY
.......done]
n3BEE-107-
</code></pre>
<p>107 - ZYPPER_EXIT_INF_RPM_SCRIPT_FAILED means "Installation basically succeeded, but some of the packages %post install scripts returned an error"</p>
<p>openQA test in scenario sle-15-SP4-Online-x86_64-hpc_EPSILON_slurm_master@64bit fails in<br>
<a href="https://openqa.suse.de/tests/8218862/modules/slurm_master/steps/162" class="external">slurm_master</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>HPC cluster for experimental and fast-moving external tests. maintainer: <a href="mailto:schlad@suse.de">schlad@suse.de</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/8205633" class="external">99.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/8181333" class="external">98.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=hpc_EPSILON_slurm_master&version=15-SP4" class="external">latest</a></p>
openQA Project - action #98577 (Resolved): Unknown ARRAY( variables matching HDD_1 or ISO in job ...https://progress.opensuse.org/issues/985772021-09-14T07:08:55Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<ul>
<li>For instance <a href="https://openqa.suse.de/tests/7092033/file/vars.json" class="external">https://openqa.suse.de/tests/7092033/file/vars.json</a> has <code>"ARRAY(0x55bb116ac3a0)" : "SLE-15-SP3-Full-x86_64-GM-Media1.iso"</code> which is repeated and assigned correctly on <code>ISO</code>.</li>
<li>Another one on publiccloud <a href="https://openqa.suse.de/tests/7096497/file/vars.json" class="external">https://openqa.suse.de/tests/7096497/file/vars.json</a> has <code>"ARRAY(0x55b5694714b8)" : "publiccloud_15sp3_Azure_BYOS_Updates.qcow2"</code> which is what <code>HDD_1</code> represents.</li>
</ul>
<p>i havent noticed any destruction or impact on the test so far but i havent also found where this comes from.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: No variables based on stringified array types present in job settings</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Add unit test validating variable names (assuming this is a bug in openQA or os-autoinst)</li>
<li>Mark jobs with variable names containing <code>(</code> as incomplete (assuming this is a bug in another tool)</li>
</ul>
openQA Project - action #98388 (Resolved): Non-existing asset "uefi-vars" is still shown up on #d...https://progress.opensuse.org/issues/983882021-09-09T09:38:23Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>An example is <a href="https://openqa.suse.de/tests/6994628#downloads" class="external">https://openqa.suse.de/tests/6994628#downloads</a></p>
<p>When i clone the job it fails with</p>
<pre><code>downloading
http://openqa.suse.de/tests/6994628/asset/other/SLE-15-SP4-Online-x86_64-Build31.2-Media1.iso.sha256
to
/var/lib/openqa/factory/other/SLE-15-SP4-Online-x86_64-Build31.2-Media1.iso.sha256
downloading
http://openqa.suse.de/tests/6994628/asset/iso/SLE-15-SP4-Online-x86_64-Build31.2-Media1.iso
to
/var/lib/openqa/factory/iso/SLE-15-SP4-Online-x86_64-Build31.2-Media1.iso
downloading
http://openqa.suse.de/tests/6994628/asset/hdd/SLES-15-SP4-x86_64-Build31.2-containers.qcow2
to
/var/lib/openqa/factory/hdd/SLES-15-SP4-x86_64-Build31.2-containers.qcow2
downloading
http://openqa.suse.de/tests/6994628/asset/hdd/SLES-15-SP4-x86_64-Build31.2-containers-uefi-vars.qcow2
to
/var/lib/openqa/factory/hdd/SLES-15-SP4-x86_64-Build31.2-containers-uefi-vars.qcow2
6994628 failed: 404 Not Found
</code></pre>
<p><a href="https://openqa.suse.de/tests/6994628/asset/hdd/SLES-15-SP4-x86_64-Build31.2-containers-uefi-vars.qcow2" class="external">uefi-vars qcow2</a> seems that it is not available any more and if you try to get this file you get 404.</p>
<p>Expected:</p>
<ul>
<li>ui should not show non-available assets</li>
</ul>
<a name="Steps-to-reproduce"></a>
<h2 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<p>Clone the job in the description, it returns a 404 error for an asset still shown in the UI page</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Investigate why is it still shown in the UI page if the cleanup removes it</li>
<li>Investigate why this is removed (if it is from the cleanup script) but not the rest</li>
<li>Fix UI so that it doesn't show non-available assets</li>
<li>(optional) i wonder if the cleanup can be more clever and keep the relevant assets</li>
</ul>
openQA Project - action #91878 (Resolved): Improve git log entries in failed test investigationhttps://progress.opensuse.org/issues/918782021-04-28T06:41:56Zybonatakisioannis.bonatakis@suse.com
<p>As for now the investigation shows commits and the files that changed separately.<br>
I believe this would be more useful if files' changes were represented below each commit such us know what changed what.<br>
So for instance test_diff_stat and test_log could be one entity.</p>
<p><a href="#" onclick="$('#collapse-932adffc-show, #collapse-932adffc-hide').toggle(); $('#collapse-932adffc').fadeToggle(150);; return false;" id="collapse-932adffc-show" class="icon icon-collapsed collapsible">Proposed represantation...</a><a href="#" onclick="$('#collapse-932adffc-show, #collapse-932adffc-hide').toggle(); $('#collapse-932adffc').fadeToggle(150);; return false;" id="collapse-932adffc-hide" class="icon icon-expanded collapsible" style="display:none;">Proposed represantation...</a><div id="collapse-932adffc" class="collapsed-text" style="display:none;"><p>❯ git log --stat --oneline HEAD~3..HEAD</p>
<pre><code>7d0a7d2d5 (HEAD -> 91821_rootless_podman, upstream/master, master) Merge pull request #12401 from rwx788/pvm
1cd0b8439 Merge pull request #12420 from rfan1/mok_util
16d2d6653 Add extend key usage CodeSigning for mok
data/openssl/gencert_conf/mok_cert.conf | 1 +
1 file changed, 1 insertion(+)
bab858b35 Merge pull request #12395 from tinawang123/zypperlr
5f3aaf134 Use get_required_var when connecting to the libyui REST API
lib/YuiRestClient.pm | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
6cb028ee8 Remove unused code in the setup_libyui test module
tests/installation/setup_libyui.pm | 1 -
1 file changed, 1 deletion(-)
93107e863 Introduce is_ssh_installation method
lib/Utils/Backends.pm | 20 ++++++++++++++++++--
tests/installation/setup_libyui.pm | 4 ++--
2 files changed, 20 insertions(+), 4 deletions(-)
876c02b53 Set YUI REST API parameters for ssh installations
lib/YuiRestClient.pm | 9 +++++++--
lib/bootloader_pvm.pm | 8 +++++++-
tests/installation/bootloader_zkvm.pm | 6 +++++-
tests/installation/setup_libyui.pm | 8 +++++++-
4 files changed, 26 insertions(+), 5 deletions(-)
3d27891b2 Check the product and modules repos after migration via zypper lr output information
products/sle/main.pm | 4 ++--
schedule/migration/aarch64_regression_test_offline.yaml | 1 +
schedule/migration/aarch64_regression_test_online.yaml | 1 +
schedule/migration/offline_spvm_Upgrade.yaml | 1 +
schedule/migration/ppc64le_regression_test_offline.yaml | 1 +
schedule/migration/ppc64le_regression_test_online.yaml | 1 +
schedule/migration/s390x-zVM-Upgrade.yaml | 1 +
schedule/migration/s390x_regression_test_offline.yaml | 1 +
schedule/migration/s390x_regression_test_online.yaml | 1 +
schedule/migration/x86_regression_test_offline.yaml | 1 +
schedule/migration/x86_regression_test_online.yaml | 1 +
tests/console/check_system_info.pm | 23 +++++++++++++++++++++++
12 files changed, 35 insertions(+), 2 deletions(-)
</code></pre></div></p>
openQA Project - action #89077 (Resolved): os-autoinst Makefile is missing symlinks configurationhttps://progress.opensuse.org/issues/890772021-02-24T15:57:21Zybonatakisioannis.bonatakis@suse.com
<p>i tried to use a forked os-autoinst on my local OpenQA instance following the steps from the documentation[0].</p>
<p>From the root of the forked repository i run <code>make</code> which finished without a problem and i started a worker with<br>
<code>sudo /usr/bin/perl /usr/share/openqa/script/worker --isotovideo /home/iob/os-autoinst-distri-opensuse/os-autoinst/isotovideo --instance 1</code><br>
Although the job was complaining about <br>
<code>Please build the tinycv bindings first (see os-autoinst's README)</code>.[1]</p>
<p>With the help of <a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a> we found that running <code>make symlinks</code> fixes the issue.<br>
Looking around i believe that the link that was missing was </p>
<pre><code>lrwxrwxrwx 1 iob users 68 Feb 24 16:06 videoencoder -> /home/iob/os-autoinst-distri-opensuse/os-autoinst/build/videoencoder
</code></pre>
<p>Expected:<br>
jobs which use that instance should run without a problem</p>
<p>Actual:<br>
Jobs fails to run asking to build tinycv which it should have done so from the <code>make</code></p>
<p>[0] <a href="https://github.com/os-autoinst/os-autoinst#build-instructions" class="external">https://github.com/os-autoinst/os-autoinst#build-instructions</a><br>
[1] <a href="http://aquarius.suse.cz/tests/5013" class="external">http://aquarius.suse.cz/tests/5013</a></p>
openQA Tests - action #71896 (Rejected): [y] Expert partitioning framework refactoringhttps://progress.opensuse.org/issues/718962020-09-25T10:38:14Zybonatakisioannis.bonatakis@suse.com
<p>As we are expanding and adding new subroutines in the framework we need to consider some refactoring to avoid duplication and make it more usable. </p>
<p>Things to refactor:</p>
<ul>
<li>_set_partitioning subroutine</li>
<li>this does not work for all the partitioning options</li>
<li>_encrypt_with_lvm subroutine</li>
<li>The encryption should work for a higher level for all the Pages that implement encryption</li>
<li>select_item_in_system_view_table subroutine</li>
<li>replace if-else with state design or find another solution.</li>
<li>Consider expansion?</li>
<li>naming of the Pages</li>
<li>The pages use the name of the page that they access but it is hard to tell if which proposal(current or suggested) comes from </li>
</ul>
<p>Let start with small things because more can come up but design is something that need to be always a task in progress but we cant cover everything.</p>
openQA Tests - action #70726 (Resolved): [y] Generate dud file dynamically instead of relying on ...https://progress.opensuse.org/issues/707262020-08-31T10:51:46Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Test fails because the <a href="ftp://openqa.suse.de/SLE-15-Module-Development-Tools-POOL-x86_64-Media1-CURRENT" class="external">ftp://openqa.suse.de/SLE-15-Module-Development-Tools-POOL-x86_64-Media1-CURRENT</a> is not available. </p>
<p>Validation and setup are introduced in <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10770/files" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10770/files</a> but we need a better approach.</p>
<p>We have <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/dev_tools.dud" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/dev_tools.dud</a> which is basically tarball created with <code>mkdud</code>. Detailed steps are described here:<br>
<code>https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/Development_Guide.md#updating-driver-update-disk-dud-file</code></p>
<p>As per comment below, we have option to pre-install <code>mkdud</code> tool on all 64bit workers, which is a bit of an overkill, but solves the issue: <a href="https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/server.sls" class="external">https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/server.sls</a></p>
<p>As an alternative we can use chained jobs and boot into installed image and generate the dud. To make it more stable we could have used support server image here.</p>
<p>See <a href="http://open.qa/api/testapi/#_upload_asset" class="external">http://open.qa/api/testapi/#_upload_asset</a> for uploading asset. <code>REPO_SLE_MODULE_DEVELOPMENT_TOOLS</code> variable contains the name of the repo.</p>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-dud_development_tools@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4619201/modules/validate_dud_addon_repos/steps/17" class="external">validate_dud_addon_repos</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Same as dud_sdk, but due to bsc#1080292 we cannot use ISO. FTP url is used instead. Limitation is that we use x86_64 url, as cannot create DUD in the runtime, so test cannot be executed on other architectures.</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/4611536" class="external">18.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/4587953" class="external">18.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=dud_development_tools&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #70153 (Resolved): [y] system_state should upload collected datahttps://progress.opensuse.org/issues/701532020-08-18T05:05:50Zybonatakisioannis.bonatakis@suse.com
<p>The <code>system_state.pm</code>[0] is just collecting data from the process list and system loads. I think it would be meaningful to upload the collected data to the OpenQA logs and assets, wherever this is used. Doing such we can review those data afterwards as it is tricky to add automatic validation on the output.</p>
<p>[0] <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/console/system_state.pm" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/console/system_state.pm</a></p>
<p>So basically we can:</p>
<ul>
<li>Fix the text uploading the file.</li>
<li>Additionally, perform a bit of research about where the post fail is trigger with ps and from which class you need to inherit to have it.</li>
<li>Consider if we need this module.</li>
</ul>
openQA Project - action #68146 (Resolved): Implement colored and interactive logshttps://progress.opensuse.org/issues/681462020-06-16T13:26:51Zybonatakisioannis.bonatakis@suse.com
<p>As tester<br>
I would like to have colored and interactive logs<br>
To explore and find the context easier</p>
<p>As a part of this, it would be great to have ability to open logs at the time when screenshot is made in Job Overview.</p>
openQA Project - action #68143 (Resolved): [y] Implement navigation to the schedule from the jobhttps://progress.opensuse.org/issues/681432020-06-16T13:18:47Zybonatakisioannis.bonatakis@suse.com
<p>As tester<br>
I want to be able to navigate easily to the schedule file of the test</p>
<p>we can implement same handling as we have for test modules code.</p>
<p>We can have it handled in similar way as test module code or at least have some improved usability using.</p>