openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-05-12T06:30:55ZopenSUSE Project Management Tool
Redmine 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 auto review - openqa-force-result #112442 (Resolved): auto_review:"'systemctl --no-pager s...https://progress.opensuse.org/issues/1124422022-06-14T19:17:25Zybonatakisioannis.bonatakis@suse.com
<p>Enable auto-review for slurm jobs reporting on <a href="https://progress.opensuse.org/issues/112436" class="external">https://progress.opensuse.org/issues/112436</a> #112436</p>
openQA Tests - action #108581 (Resolved): False softfails in scc_registrationhttps://progress.opensuse.org/issues/1085812022-03-19T08:35:17Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>There are softfails in the installation and particular on ssc_registration module. However i havent reproduce the softfail in most of the cases. </p>
<p>From the bug[0] context, it is not clear whether this is an actual product issue. <br>
I havent tested it outside of the openqa env yet but many of the tests i run do not show the problem except some particular jobs(sles+sdk+proxy_SCC_via_YaST) which YaST team have some peculiarities, and i think this might be a test issue or env setup. </p>
<p>Anyhow the softfail should be ignored in the cases which it just work as it reports misleading results for the product in the whole. </p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Every build after <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14342" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14342</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Softfail raised after checking of the problem<br>
or restrict the softfail only for the jobs which seems to affect the most</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>[0] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1191112" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1191112</a></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 Tests - action #95455 (Rejected): [qac][kernel] Make record_soft_failure shows error as re...https://progress.opensuse.org/issues/954552021-07-13T15:29:46Zybonatakisioannis.bonatakis@suse.com
<p>The idea is that when there is a bug open we have <code>record_soft_failure</code> to workaround in the test level.<br>
But when the bug is resolved there are two approach AFAIK. remove the softfail or leave it intact to find regressions. <br>
however when the bug is gone and softfail still exists in the code, there is not an easy way to distinguish the regression.</p>
<p>I propose to enhance the <code>record_soft_failure</code> to show the regression. One idea is to introduce a flag(extra param?) which we can switch <br>
when the bug has been resolved. Then we can either make the test fail*[1] or show the soft_fail with another colour.</p>
<p>I am not sure if this is the best approach so please comment below if something better comes in your mind.</p>
<p>*[1] maybe we can introduce a parameter to define severity. Then if(critical)->(fail)->else(pass) </p>
openQA Tests - action #91941 (Resolved): [qac] test fails in docker_runchttps://progress.opensuse.org/issues/919412021-04-29T08:39:13Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Fabian Vogt <a class="user active user-mention" href="https://progress.opensuse.org/users/20030">@favogt</a><br>
10:28 AM<br>
Veronika Svecova jun wang Yes, the conflict is expected. <code>docker-runc</code> is no longer used<br>
10:34 AM<br>
Marcus Rückert <a class="user active user-mention" href="https://progress.opensuse.org/users/29146">@darix</a><br>
10:28 AM<br>
maybe we should provide/obsolete it then?<br>
Fabian Vogt <a class="user active user-mention" href="https://progress.opensuse.org/users/20030">@favogt</a><br>
10:28 AM<br>
The issue is that the openQA test tries to install it explicitly</p>
<p>openQA test in scenario sle-15-SP1-Server-DVD-Updates-s390x-mau-extratests-docker@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/5915293/modules/docker_runc/steps/68" class="external">docker_runc</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Run docker console tests against aggregated test repo</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/5915293" class="external">20210429-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/5908947" class="external">20210428-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=s390x&distri=sle&flavor=Server-DVD-Updates&machine=s390x-kvm-sle12&test=mau-extratests-docker&version=15-SP1" class="external">latest</a></p>
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-24bf6c9b-show, #collapse-24bf6c9b-hide').toggle(); $('#collapse-24bf6c9b').fadeToggle(150);; return false;" id="collapse-24bf6c9b-show" class="icon icon-collapsed collapsible">Proposed represantation...</a><a href="#" onclick="$('#collapse-24bf6c9b-show, #collapse-24bf6c9b-hide').toggle(); $('#collapse-24bf6c9b').fadeToggle(150);; return false;" id="collapse-24bf6c9b-hide" class="icon icon-expanded collapsible" style="display:none;">Proposed represantation...</a><div id="collapse-24bf6c9b" 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 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 Tests - action #69862 (Resolved): [y] supportserver_generator_from_hdd fails for x86_64https://progress.opensuse.org/issues/698622020-08-11T10:19:46Zybonatakisioannis.bonatakis@suse.com
<p><a href="https://openqa.suse.de/tests/4546589#step/configure/12" class="external">https://openqa.suse.de/tests/4546589#step/configure/12</a><br>
<a href="https://openqa.suse.de/tests/4546588#step/configure/12" class="external">https://openqa.suse.de/tests/4546588#step/configure/12</a></p>
qe-yam - action #69142 (Resolved): [y] Adjust bootloader for MM on aarch64https://progress.opensuse.org/issues/691422020-07-20T13:34:04Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>aarch64 uses uefi in the bootloader. <br>
The bootloader for the MM tests are not setup properly the parameters as you can see for instance on remote_ssh_target_ftp in <a href="https://openqa.suse.de/tests/4466996/modules/bootloader_start/steps/8" class="external">bootloader_start</a></p>
<p>the bootloader for the x86_64 loads parameters as you can find in <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/bootloader.pm#L59" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/bootloader.pm#L59</a>. basically <code>ssh</code> and <code>ssh.password</code>. Other parameters might are required based on the media. for example, Online installation, might need dns.</p>
<p>bootloader_start uses the correct bootloader as now.</p>
<p>We are missing at least following boot params:<br>
nameserver= ssh=1 sshpassword=nots3cr3t for ssh<br>
nameserver= vnc=1 vncpassword=nots3cr3t for vnc</p>
<p>So we need to make sure those are added to uefi bootloader.</p>
<p>Don't hesitate to contact Anton Smorodsky in case you need support with MM tests on arm.</p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>uefi bootloader passes the required parameters for networking(ssh, vnc, etc)</li>
</ul>
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>
openQA Tests - action #67285 (Resolved): [y] Adjust installation in autoyast_salt to the recent c...https://progress.opensuse.org/issues/672852020-05-26T14:24:50Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>now we support several formulas (suse manager and not suse manager), several pillars etc.<br>
in order to make everything consistent, we changed how the salt.tar.gz is organized, and the "formulas" directories has now two directories (states and metadata). <br>
the changes are <a href="https://github.com/yast/yast-configuration-management/pull/81" class="external">https://github.com/yast/yast-configuration-management/pull/81</a> and <a href="https://github.com/yast/yast-configuration-management/pull/80" class="external">https://github.com/yast/yast-configuration-management/pull/80</a>.</p>
<p>in theory we would need to update the tar file with the new structure. The rest should remain the same(xml, installation flow)</p>
<p>Contact to <a class="user active user-mention" href="https://progress.opensuse.org/users/15330">@IGonzalezSosa</a> for support</p>
<p>openQA test in scenario sle-15-SP2-Online-x86_64-autoyast_salt@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4283662/modules/installation/steps/46" 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>Test installation using AutoYaST plus salt formulas.</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/4281272" class="external">202.5</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/4277536" class="external">201.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_salt&version=15-SP2" class="external">latest</a></p>
openQA Project - action #66427 (Rejected): openqa-cli cant trigger single jobhttps://progress.opensuse.org/issues/664272020-05-05T11:05:58Zybonatakisioannis.bonatakis@suse.com
<p>I used </p>
<pre><code class="text syntaxhl" data-language="text">openqa-cli api --pretty --osd -X POST isos ISO=SLE-15-SP2-Online-x86_64-Build188.1-Media1.iso DISTRI=sle VERSION=15-SP2 FLAVOR=Online ARCH=x86_64 BUILD=188.1 TEST=autoyast_home_encrypted
</code></pre>
<p>to trigger a single job named <em>autoyast_home_encrypted</em> but it wound up running all the jobs for the Online medium. The corresponding command with openqa-client was </p>
<pre><code class="text syntaxhl" data-language="text">openqa-client isos post --host=http://openqa.suse.de ISO=SLE-15-SP2-Online-x86_64-Build188.1-Media1.iso DISTRI=sle VERSION=15-SP2 FLAVOR=Online ARCH=x86_64 BUILD=188.1 TEST=autoyast_home_encrypted
</code></pre>
<p>Expected:<br>
To run only the test job with name autoyast_home_encrypted from the TEST variable</p>
<p>Actual:<br>
Seems to ignore the TEST variable and match all the others with reasult to trigger many jobs</p>
openQA Tests - action #62096 (Resolved): [functional][y][opensuse][timeboxed:16h] remote intallat...https://progress.opensuse.org/issues/620962020-01-13T15:25:53Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Follow up for <a class="issue tracker-4 status-3 priority-4 priority-default closed child behind-schedule" title="action: [functional][y] Enable remote installation over VNC for openSUSE (Resolved)" href="https://progress.opensuse.org/issues/52310">#52310</a> as scenario is still not enabled.</p>
<p>In remote installation through ssh and vnc in opensuse the remote_target doesn't close the yast2 to get into the installed desktop. The support qcow is support_server_opensuse-15.0-x86_64-GM-gnome.qcow2. I believe that there is something wrong with the image. We may need to create and test with a new one. Otherwise we need to investigate the problem.</p>
<p>for now there is a workaround for opensuse to do so manually pressing the "ctl-alt-delete" but this is not the expected behavior.</p>
<p>openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-remote_vnc_target_nfs@64bit fails in<br>
<a href="http://aquarius.suse.cz/tests/1274/modules/remote_target/steps/4" class="external">remote_target</a></p>
<p>We need to investigate the issue and at least report the bug, which we can use as a soft-failure for the workaround.</p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>remote installation with vnc. setup for target</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="http://aquarius.suse.cz/tests/1274" class="external">20191214</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="http://aquarius.suse.cz/tests/1250" class="external">20191214</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="http://aquarius.suse.cz/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=remote_vnc_target_nfs&version=Tumbleweed" class="external">latest</a></p>
openQA Project - action #55151 (Resolved): [functional][y] provide message explaining the failure...https://progress.opensuse.org/issues/551512019-08-06T15:15:20Zybonatakisioannis.bonatakis@suse.com
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>I'm as a openQA test developer would like to put message in <code>script_run</code> calls to provide more details about executed command.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>Test developer can provide custom message for script_run</li>
<li>Unit tests are added for the new functionality</li>
</ol>