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 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-6366b3a4-show, #collapse-6366b3a4-hide').toggle(); $('#collapse-6366b3a4').fadeToggle(150);; return false;" id="collapse-6366b3a4-show" class="icon icon-collapsed collapsible">autoinst-log.txt...</a><a href="#" onclick="$('#collapse-6366b3a4-show, #collapse-6366b3a4-hide').toggle(); $('#collapse-6366b3a4').fadeToggle(150);; return false;" id="collapse-6366b3a4-hide" class="icon icon-expanded collapsible" style="display:none;">autoinst-log.txt...</a><div id="collapse-6366b3a4" 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 Tests - action #65891 (Resolved): [functional][y] fix first_boot on ipmihttps://progress.opensuse.org/issues/658912020-04-21T07:06:26Zybonatakisioannis.bonatakis@suse.com
<p>##Observation</p>
<p>We need to check if we should disable grub timeout. If so, we should press enter in grub menu[0].<br>
Test appear not to work for quite some time.</p>
<p>From the past experience we know that <code>enter</code> key doesn't reach the system sporadically, so disabling grub timeout should resolve this issue and system should be able to boot.</p>
<p>[0] <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit-ipmi&test=btrfs_libstorage-ng&version=15-SP2" class="external">https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit-ipmi&test=btrfs_libstorage-ng&version=15-SP2</a></p>
openQA Tests - action #65088 (Resolved): [functional][y] Verify writing conflict from YaST in 70...https://progress.opensuse.org/issues/650882020-03-31T12:34:25Zybonatakisioannis.bonatakis@suse.com
<p>We want to test that config writings from YaST produces certain conflicts.</p>
<p>The implementation as now, contains a couple of yast modules that uses the 70-yast.conf. Some of them that we can use for automation during the installation is</p>
<ul>
<li>net.ipv4.ip_forward</li>
<li>net.ipv4.tcp_syncookies</li>
</ul>
<p>These settings are available in the yast2 network module.</p>
<p>Scope is limited to 64bit on SLES only for the start.</p>
<p>Potential Scenario:</p>
<ol>
<li>Check that module writes settings properly in /etc/sysctl.d/70-yast.conf and not in /etc/sysctl.conf (using yast2 lan module with settings mentioned above)</li>
<li>Set conflicting settings in /etc/sysctl.conf, edit them in yast module verify that yast module reports it</li>
<li>Set conflicting setting in custom file, e.g. /etc/sysctl.d/90-custom.conf , edit them in yast module verify that yast module reports it</li>
</ol>
<p>See Also <a href="https://jira.suse.com/browse/SLE-9077" class="external">https://jira.suse.com/browse/SLE-9077</a> and <a href="https://jira.suse.com/browse/SLE-9088" class="external">https://jira.suse.com/browse/SLE-9088</a></p>
<p>Feature discussion: <a href="https://trello.com/c/uf4RFeC1/3671-sysctld-handling-display-current-settings-and-warn-about-conflicts" class="external">https://trello.com/c/uf4RFeC1/3671-sysctld-handling-display-current-settings-and-warn-about-conflicts</a></p>
<p>Also see <a href="https://progress.opensuse.org/issues/61073#note-13" class="external">https://progress.opensuse.org/issues/61073#note-13</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>in case of conflict all the settings are discarded</li>
</ol>
openQA Tests - action #64731 (Resolved): [functional][y] generate TW image with wicked and use it...https://progress.opensuse.org/issues/647312020-03-24T09:42:11Zybonatakisioannis.bonatakis@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>The yast2_cmdline performs some tests for the command line with the Test Anything Protocol [0].<br>
One of the tap test is for yast2_network module which its tests are relative to wicked and that's why they do not work with NetworkManager,<br>
and it doesnt make sense to run it if this is the case.</p>
<p>Therefore, yast2_cmdline should be executed with wicked setup only.</p>
<p>In openqa, Tumbleweed uses an image which uses NetworkManager. We need to make the test work 'switching' to wicked</p>
<p><a href="https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Tumbleweed&build=20200320&groupid=38" class="external">https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Tumbleweed&build=20200320&groupid=38</a></p>
<p>NOTE: textmode installation has wicked by default, but we use only gnome image</p>
<p>In the image we can switch using following commands:<br>
systemctl disable NetworkManager --now<br>
systemctl enable wicked --now</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ol>
<li>There is an image with wicked enabled in it</li>
<li>yast2_ui_devel uses image with wicked from step 1.</li>
<li>nis_(client|server) test suites use image with wicked from step 1.</li>
</ol>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<p>[0] <a href="https://yastgithubio.readthedocs.io/en/latest/how-to-write-tests/#how" class="external">https://yastgithubio.readthedocs.io/en/latest/how-to-write-tests/#how</a></p>
openQA Tests - action #61931 (Resolved): [functiona][y] autoinst.xml is missing registration bloc...https://progress.opensuse.org/issues/619312020-01-08T16:37:19Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The <a href="https://openqa.suse.de/assets/other/03758754-autoinst.xml" class="external">autoinst.xml</a> which is created by the chained job is missing the block for the registration that is required for the Online Installer.</p>
<p>Scope is SLE 15 SP2, for other versions</p>
<p>The missing block looks like this</p>
<pre><code><suse_register>
<do_registration config:type="boolean">true</do_registration>
<email/>
<reg_code>667ccc9ac65d705f</reg_code>
<install_updates config:type="boolean">true</install_updates>
<reg_server>http://all-120.1.proxy.scc.suse.de</reg_server>
</suse_register>
</code></pre>
<p>##Suggestions</p>
<ol>
<li>move the job to the Full medium</li>
<li>modify the xml before the execution</li>
</ol>
<p>openQA test in scenario sle-15-SP2-Online-aarch64-autoyast_reinstall@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/3762738/modules/installation/steps/43" 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>Parent job produces autoyast profile after successful completion. This test uses generated profile to do autoyast installation.</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/3758866" class="external">120.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=autoyast_reinstall&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #61100 (Resolved): [functional][y] test fails in scc_registrationhttps://progress.opensuse.org/issues/611002019-12-17T14:34:14Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The full media have new warning popup when you try to skip registration. That makes the latest build fails. <br>
On the skip_registration jobs for full media we need, likely, to adjust the flow after the the skipping, too. related ticket <a href="https://jira.suse.com/browse/SLE-7222" class="external">https://jira.suse.com/browse/SLE-7222</a> and <a href="https://trello.com/c/pyqFurT6/1441-3-updater-registration-handling" class="external">https://trello.com/c/pyqFurT6/1441-3-updater-registration-handling</a>.</p>
<p>openQA test in scenario sle-15-SP2-Full-x86_64-offline_install+skip_registration@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3715189/modules/scc_registration/steps/4" class="external">scc_registration</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: riafarov</p>
<p>Offline installation. Skipping registration for SLE 15, as requires network connection. This is default behavior for SLE 12.</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/3715189" class="external">108.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/3698943" class="external">105.4</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=Full&machine=64bit&test=offline_install%2Bskip_registration&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #60230 (Resolved): [functional][y] test fails in system_rolehttps://progress.opensuse.org/issues/602302019-11-25T11:19:53Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Seems that the UI has changed for the system role frame. We need to adjast the needles to the new design. In this particular test the needle tries to match the textmode option</p>
<p>openQA test in scenario sle-15-SP2-Online-x86_64-addon-module-ftp@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3628412/modules/system_role/steps/15" class="external">system_role</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Test verifies that adding addon using ftp works fine. We just perform installation here. Using HA here, related ticket: <a href="https://progress.opensuse.org/issues/25896" class="external">https://progress.opensuse.org/issues/25896</a> Maintainer: riafarov.</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/3625062" class="external">93.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/3614139" class="external">92.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=addon-module-ftp&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #59939 (Resolved): [functional][y] first entry in product selection list is...https://progress.opensuse.org/issues/599392019-11-18T08:48:49Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Seems like the spc keystroke is not click the checkbox as it is expected but instead it presses the next button. this is observed on s390 as there is no occurrence in other archs </p>
<p>It might be that we need to tab to the list.<br>
We also need to check if there are two mechanisms in place, like clicking on checkboxes instead of iterating over the list which is fallback, when needle is not visible.</p>
<p>We should attempt to unify flows of module selection for registered and unregistered installations.</p>
<p><a href="https://openqa.suse.de/tests/3598118#step/scc_registration/13" class="external">https://openqa.suse.de/tests/3598118#step/scc_registration/13</a> vs <a href="https://openqa.suse.de/tests/3597803#step/addon_products_sle/4" class="external">https://openqa.suse.de/tests/3597803#step/addon_products_sle/4</a></p>
<p>openQA test in scenario sle-15-SP2-Full-s390x-skip_registration@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/3603938/modules/addon_products_sle/steps/37" class="external">addon_products_sle</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: okurz, riafarov</p>
<p>Like a standard scenario with explicit skipping of SCC registration in case where we register by default, e.g. for SLE >= 15<br>
See <a href="https://progress.opensuse.org/issues/25264" class="external">https://progress.opensuse.org/issues/25264</a> for details.</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/3529293" class="external">72.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=s390x&distri=sle&flavor=Full&machine=s390x-kvm-sle12&test=skip_registration&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #59318 (Resolved): [functional][u] packages are not gettting installed https://progress.opensuse.org/issues/593182019-11-11T16:04:24Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Online-x86_64-lvm+resize_root@64bit fails in<br>
<a href="https://openqa.suse.de/tests/3571728/modules/eog/steps/4" class="external">eog</a></p>
<p>Due to some misconfiguration(??) in the repos the system is incapable to find and install some packages.</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/3529472" class="external">72.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=lvm%2Bresize_root&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #59012 (Resolved): [functional][y] test fails in yast_sysconfighttps://progress.opensuse.org/issues/590122019-11-04T10:09:22Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Test variable is not propagated to the sysconfig list.</p>
<p>openQA test in scenario sle-15-SP2-Installer-DVD-s390x-yast2_cmd@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/3552677/modules/yast_sysconfig/steps/7" class="external">yast_sysconfig</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>QAM team has developed some tests using YaST cmd line, which is less costly to execute and maintain. This test suite is using those test modules for QA SLE functional.</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/3547257" class="external">77.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/3536545" class="external">72.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=Installer-DVD&machine=s390x-kvm-sle12&test=yast2_cmd&version=15-SP2" 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>