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 Tests - action #135218 (In Progress): test regression in ww4_await_pxe_installhttps://progress.opensuse.org/issues/1352182023-09-06T06:44:43Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Tries to boot before the server gets ready and process fails.</p>
<p>openQA test in scenario sle-15-SP6-Online-x86_64-hpc_ww4_compute0@64bit fails in<br>
<a href="https://openqa.suse.de/tests/12014546/modules/ww4_await_pxe_install/steps/7" class="external">ww4_await_pxe_install</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>first compute node for warewulf booting from network (PXE) after the controller is ready for connection.</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/11979509" class="external">16.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=hpc_ww4_compute0&version=15-SP6" class="external">latest</a></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 Tests - action #128594 (New): test fails in spack_masterhttps://progress.opensuse.org/issues/1285942023-05-03T12:50:53Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>This is related to LD_LIBRARY_PATH again similar to bsc#1208751 [1].</p>
<p>To solve the problem back then, we replace the source file which we compile and run with a simple one which it doesnt have dependency on boost library.<br>
As such we had only to load mpich. SLE15SP5 seems with this. However the SLE15SP3 doesnt accept this change. <br>
The spack versions are quite the same<br>
SLE15SP3 -> 0.19.1-150300.5.16.1<br>
SLE15SP5 -> 0.19.1-150400.12.5.1</p>
<p>The thing is that despite the source file nothing else has change. the test fails in the same version which is used by previous jobs.</p>
<p>[1] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1208751" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1208751</a></p>
<p>openQA test in scenario sle-15-SP3-Server-DVD-HPC-Incidents-x86_64-hpc_BETA_mpich_spack_master@64bit-4gbram fails in<br>
<a href="https://openqa.suse.de/tests/11015548/modules/spack_master/steps/118" class="external">spack_master</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. </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/10938144" class="external">:28369:hdf5</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/10882077" class="external">:28369:hdf5</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=Server-DVD-HPC-Incidents&machine=64bit-4gbram&test=hpc_BETA_mpich_spack_master&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #120900 (New): Required patterns values are not removed on select_patterns https://progress.opensuse.org/issues/1209002022-11-23T17:38:39Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>I am not sure if the title is accurate. What actually happens can be seen on the attached screen <a href="https://openqa.suse.de/tests/9825401/modules/select_patterns/steps/124" class="external">select_patterns</a><br>
The specific job set <code>PATTERNS": "base,minimal,apparmor"</code> but at the end only minimal and apparmor are selected. The problem is that another pattern is deselected after the base is checked.<br>
Due to the logic of the <code>select_specific_patterns_by_iteration</code> function, which iterates from top to bottom, it can happen a previous pattern to alter as a dependency of another selection/deselection on a later checkbox.</p>
<p>Also i found the code a bit complicated. For starters there is two different approaches to uncheck patterns</p>
<ol>
<li><code>$self->deselect_pattern() if get_var('EXCLUDE_PATTERNS');</code></li>
<li>inside <code>select_specific_patterns_by_iteration</code> using minus notation on PATTERNS.</li>
</ol>
<p>I think this is unnecessarily complexity<br>
Also i believe that the <code>process_patterns</code> should take care and acts of <em>defaults</em> PATTERNS. As now the logic is inside <code>select_specific_patterns_by_iteration</code></p>
<p>This ticket to improve and improve in all the above. I dont think this is high priority -nor even normal- as it doesnt have destructive impact on the most of the test cases but hides <strong>a seriously defect which produces an unexpected installation than the one was set it up for</strong>.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>To reproduce you can set <code>PATTERNS": "base,minimal,apparmor"</code> and choose a job which by default has <code>GNOME</code> checked. At the end of the <code>select_specific_patterns_by_iteration</code> review the <em>installation settings</em> window before the installation</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>PATTERNS values are ensured are selected at the end of the <code>process_patterns</code></p>
openQA Tests - action #118663 (New): [qe-core] wait_serial reports fail on serial_terminal when i...https://progress.opensuse.org/issues/1186632022-10-13T13:38:34Zybonatakisioannis.bonatakis@suse.com
<a name="Description"></a>
<h1 >Description<a href="#Description" class="wiki-anchor">¶</a></h1>
<p>The problem appears in a scenario where you run a container and launch its interactive console and the module itself uses serial_terminal</p>
<p><a href="#" onclick="$('#collapse-7197ffeb-show, #collapse-7197ffeb-hide').toggle(); $('#collapse-7197ffeb').fadeToggle(150);; return false;" id="collapse-7197ffeb-show" class="icon icon-collapsed collapsible">autoinst-log.txt...</a><a href="#" onclick="$('#collapse-7197ffeb-show, #collapse-7197ffeb-hide').toggle(); $('#collapse-7197ffeb').fadeToggle(150);; return false;" id="collapse-7197ffeb-hide" class="icon icon-expanded collapsible" style="display:none;">autoinst-log.txt...</a><div id="collapse-7197ffeb" class="collapsed-text" style="display:none;"><pre><code>[2022-10-13T15:17:01.951831+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:17:01.952227+02:00] [debug] <<< testapi::wait_serial(timeout=90, buffer_size=undef, no_regex=1, expect_not_found=0, regexp="# ", quiet=1, record_output=undef)
[2022-10-13T15:17:01.953435+02:00] [debug] <<< consoles::serial_screen::read_until(timeout=90, no_regex=1, record_output=undef, buffer_size=undef, pattern=[
"# "
], regexp="# ", expect_not_found=0, quiet=1, json_cmd_token="stLkEWrr", cmd="backend_wait_serial")
[2022-10-13T15:18:32.041417+02:00] [debug] >>> testapi::wait_serial: # : fail
[2022-10-13T15:18:32.041731+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:18:32.041945+02:00] [debug] <<< distribution::script_output("Content of /tmp/script_uow4.sh :\n \"cat > /tmp/script_uow4.sh << 'EOT__uow4'; echo _uow4-\$?-\" \n")
[2022-10-13T15:18:32.043257+02:00] [debug] <<< consoles::serial_screen::type_string(text="cat > /tmp/script_uow4.sh << 'EOT__uow4'; echo _uow4-\$?-\n", json_cmd_token="kCaIjsnI", cmd="backend_type_string")
[2022-10-13T15:18:32.044126+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:18:32.044536+02:00] [debug] <<< testapi::wait_serial(quiet=1, record_output=undef, timeout=90, buffer_size=undef, expect_not_found=0, regexp="cat > /tmp/script_uow4.sh << 'EOT__uow4'; echo _uow4-\$?-", no_regex=1)
[2022-10-13T15:18:32.045981+02:00] [debug] <<< consoles::serial_screen::read_until(record_output=undef, timeout=90, no_regex=1, quiet=1, json_cmd_token="KTIlmTxF", cmd="backend_wait_serial", pattern=[
"cat > /tmp/script_uow4.sh << 'EOT__uow4'; echo _uow4-\$?-"
], buffer_size=undef, regexp="cat > /tmp/script_uow4.sh << 'EOT__uow4'; echo _uow4-\$?-", expect_not_found=0)
[2022-10-13T15:18:32.046286+02:00] [info] ::: consoles::serial_screen::read_until: Matched output from SUT in 2 loops & 0.000667732208967209 seconds: cat > /tmp/script_uow4.sh << 'EOT__uow4'; echo _uow4-$?-
[2022-10-13T15:18:32.047033+02:00] [debug] >>> testapi::wait_serial: cat > /tmp/script_uow4.sh << 'EOT__uow4'; echo _uow4-$?-: ok
[2022-10-13T15:18:32.047315+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:18:32.047697+02:00] [debug] <<< testapi::wait_serial(record_output=undef, quiet=1, no_regex=1, expect_not_found=0, regexp="> ", buffer_size=undef, timeout=90)
[2022-10-13T15:18:32.049043+02:00] [debug] <<< consoles::serial_screen::read_until(no_regex=1, timeout=90, record_output=undef, expect_not_found=0, regexp="> ", buffer_size=undef, pattern=[
"> "
], cmd="backend_wait_serial", json_cmd_token="TLLLRDQk", quiet=1)
[2022-10-13T15:18:32.049266+02:00] [info] ::: consoles::serial_screen::read_until: Matched output from SUT in 1 loops & 0.000562381930649281 seconds: >
[2022-10-13T15:18:32.049970+02:00] [debug] >>> testapi::wait_serial: > : ok
[2022-10-13T15:18:32.050915+02:00] [debug] <<< consoles::serial_screen::type_string(text="cat /etc/os-release && echo testdone\nEOT__uow4\n", cmd="backend_type_string", json_cmd_token="KTMInCwi")
[2022-10-13T15:18:32.051701+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:18:32.052216+02:00] [debug] <<< testapi::wait_serial(regexp="> EOT__uow4", expect_not_found=0, no_regex=1, timeout=90, buffer_size=undef, record_output=undef, quiet=1)
[2022-10-13T15:18:32.053458+02:00] [debug] <<< consoles::serial_screen::read_until(json_cmd_token="azrXZuje", cmd="backend_wait_serial", quiet=1, expect_not_found=0, regexp="> EOT__uow4", pattern=[
"> EOT__uow4"
], buffer_size=undef, record_output=undef, no_regex=1, timeout=90)
[2022-10-13T15:18:32.053728+02:00] [info] ::: consoles::serial_screen::read_until: Matched output from SUT in 2 loops & 0.000609030947089195 seconds: > EOT__uow4
[2022-10-13T15:18:32.054428+02:00] [debug] >>> testapi::wait_serial: > EOT__uow4: ok
[2022-10-13T15:18:32.054704+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:18:32.055060+02:00] [debug] <<< testapi::wait_serial(record_output=undef, quiet=1, no_regex=0, regexp="_uow4-0-", expect_not_found=0, buffer_size=undef, timeout=90)
[2022-10-13T15:18:32.056388+02:00] [debug] <<< consoles::serial_screen::read_until(timeout=90, no_regex=0, record_output=undef, pattern="_uow4-0-", buffer_size=undef, regexp="_uow4-0-", expect_not_found=0, quiet=1, cmd="backend_wait_serial", json_cmd_token="aCMENdVw")
[2022-10-13T15:18:32.058856+02:00] [info] ::: consoles::serial_screen::read_until: Matched output from SUT in 2 loops & 0.00273504760116339 seconds: _uow4-0-
[2022-10-13T15:18:32.059562+02:00] [debug] >>> testapi::wait_serial: _uow4-0-: ok
[2022-10-13T15:18:32.059848+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:18:32.060210+02:00] [debug] <<< testapi::wait_serial(expect_not_found=0, regexp="# ", no_regex=1, buffer_size=undef, timeout=90, record_output=undef, quiet=1)
[2022-10-13T15:18:32.061421+02:00] [debug] <<< consoles::serial_screen::read_until(buffer_size=undef, pattern=[
"# "
], regexp="# ", expect_not_found=0, quiet=1, cmd="backend_wait_serial", json_cmd_token="HkXhwxdk", timeout=90, no_regex=1, record_output=undef)
[2022-10-13T15:20:02.113308+02:00] [debug] >>> testapi::wait_serial: # : fail
[2022-10-13T15:20:02.114530+02:00] [debug] <<< consoles::serial_screen::type_string(json_cmd_token="ZmelFHja", cmd="backend_type_string", text="echo _uow4; bash -oe pipefail /tmp/script_uow4.sh ; echo SCRIPT_FINISHED_uow4-\$?-\n")
[2022-10-13T15:20:02.115298+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:20:02.115764+02:00] [debug] <<< testapi::wait_serial(record_output=undef, quiet=1, no_regex=1, expect_not_found=0, regexp="echo _uow4; bash -oe pipefail /tmp/script_uow4.sh ; echo SCRIPT_FINISHED_uow4-\$?-", buffer_size=undef, timeout=90)
[2022-10-13T15:20:02.117013+02:00] [debug] <<< consoles::serial_screen::read_until(buffer_size=undef, pattern=[
"echo _uow4; bash -oe pipefail /tmp/script_uow4.sh ; echo SCRIPT_FINISHED_uow4-\$?-"
], expect_not_found=0, regexp="echo _uow4; bash -oe pipefail /tmp/script_uow4.sh ; echo SCRIPT_FINISHED_uow4-\$?-", quiet=1, cmd="backend_wait_serial", json_cmd_token="HGtqBdRI", timeout=90, no_regex=1, record_output=undef)
[2022-10-13T15:20:02.117351+02:00] [info] ::: consoles::serial_screen::read_until: Matched output from SUT in 2 loops & 0.00069341529160738 seconds: echo _uow4; bash -oe pipefail /tmp/script_uow4.sh ; echo SCRIPT_FINISHED_uow4-$?-
[2022-10-13T15:20:02.118108+02:00] [debug] >>> testapi::wait_serial: echo _uow4; bash -oe pipefail /tmp/script_uow4.sh ; echo SCRIPT_FINISHED_uow4-$?-: ok
[2022-10-13T15:20:02.118391+02:00] [debug] tests/containers/apptainer.pm:50 called testapi::validate_script_output
[2022-10-13T15:20:02.118743+02:00] [debug] <<< testapi::wait_serial(expect_not_found=0, regexp="SCRIPT_FINISHED_uow4-\\d+-", no_regex=0, buffer_size=undef, timeout=90, record_output=1, quiet=1)
[2022-10-13T15:20:02.120085+02:00] [debug] <<< consoles::serial_screen::read_until(no_regex=0, timeout=90, record_output=1, expect_not_found=0, regexp="SCRIPT_FINISHED_uow4-\\d+-", buffer_size=undef, pattern="SCRIPT_FINISHED_uow4-\\d+-", cmd="backend_wait_serial", json_cmd_token="uwWUVyYC", quiet=1)
[2022-10-13T15:20:02.125432+02:00] [info] ::: consoles::serial_screen::read_until: Matched output from SUT in 8 loops & 0.00561576243489981 seconds: SCRIPT_FINISHED_uow4-0-
[2022-10-13T15:20:02.126191+02:00] [debug] >>> testapi::wait_serial: SCRIPT_FINISHED_uow4-\d+-: ok
</code></pre></div></p>
<p>I tried to play with <code>set_serial_prompt</code> and <code>set_standard_prompt</code> functions without actual solve the problem.<br>
This isnt shown up when <code>select_console</code> is used</p>
<p>The failure comes from (script_output of distribution.pm)</p>
<pre><code>testapi::wait_serial($self->{serial_term_prompt}, no_regex => 1, quiet => $args{quiet});
</code></pre>
<p>Expected:<br>
wait_serial returns <em>ok</em> or ignore <code>testapi::wait_serial</code> if is an interactive terminal</p>
<p>Additional:<br>
I think that this is low priority because doesnt make test fail or anything, but it would be nice to fix it and improve the code as it causes some additional time of the test execution without any good reason</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 #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-0d8b9db2-show, #collapse-0d8b9db2-hide').toggle(); $('#collapse-0d8b9db2').fadeToggle(150);; return false;" id="collapse-0d8b9db2-show" class="icon icon-collapsed collapsible">Proposed represantation...</a><a href="#" onclick="$('#collapse-0d8b9db2-show, #collapse-0d8b9db2-hide').toggle(); $('#collapse-0d8b9db2').fadeToggle(150);; return false;" id="collapse-0d8b9db2-hide" class="icon icon-expanded collapsible" style="display:none;">Proposed represantation...</a><div id="collapse-0d8b9db2" 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 #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 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>