openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-02-27T17:27:27ZopenSUSE Project Management Tool
Redmine openQA Project - action #156169 (New): Automatically validate ay-openqa-worker.xml.erbhttps://progress.opensuse.org/issues/1561692024-02-27T17:27:27Zybonatakisioannis.bonatakis@suse.com
<p><a href="https://github.com/os-autoinst/openQA/blob/master/contrib/ay-openqa-worker.xml.erb" class="external">https://github.com/os-autoinst/openQA/blob/master/contrib/ay-openqa-worker.xml.erb</a> is used for openqa workers. <br>
This is passed as-is to the autoyast and seems to work.<br>
But when generate the xml manual</p>
<ul>
<li>Either TW or Leap</li>
<li>install autoyast2</li>
<li>Run <code>sudo yast2 autoyast check-profile filename=ay-openqa-worker.xml.erb output=result.xml run-scripts=true run-erb=true</code></li>
</ul>
<p>Then complains for:</p>
<ul>
<li>firewall configuration</li>
<li>failure to run the scripts</li>
</ul>
<p>I am not sure about the requirements about the later, but firewall should be easy to address.</p>
openQA Project - action #126032 (Resolved): iso posts do not start all the children chainhttps://progress.opensuse.org/issues/1260322023-03-15T04:34:31Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Not all the child jobs are scheduled from the parent.</p>
<p>I noticed that in the last two build IIRC. For some reason that occurred in this specific test.<br>
The rest of the multijobs looks to start as expected.<br>
However a few examples i tried out reproduce the problem. </p>
<p><a href="#" onclick="$('#collapse-a4e4aac5-show, #collapse-a4e4aac5-hide').toggle(); $('#collapse-a4e4aac5').fadeToggle(150);; return false;" id="collapse-a4e4aac5-show" class="icon icon-collapsed collapsible">iso posts example with _SKIP_CHAINED_DEPS</a><a href="#" onclick="$('#collapse-a4e4aac5-show, #collapse-a4e4aac5-hide').toggle(); $('#collapse-a4e4aac5').fadeToggle(150);; return false;" id="collapse-a4e4aac5-hide" class="icon icon-expanded collapsible" style="display:none;">iso posts example with _SKIP_CHAINED_DEPS</a><div id="collapse-a4e4aac5" class="collapsed-text" style="display:none;"><p>openqa-cli api --pretty --osd -X POST isos ISO=SLE-15-SP5-Online-aarch64-Build80.1-Media1.iso DISTRI=sle VERSION=15-SP5 FLAVOR=Online ARCH=aarch64 BUILD=80.1 TEST=hpc_BETA_mpich_mpi_supportserver _GRPOUP_ID=130<br>
{<br>
"count" : 2,<br>
"failed" : [],<br>
"ids" : [<br>
10698182,<br>
10698183<br>
],<br>
"scheduled_product_id" : 1768408<br>
}</p>
</div></p>
<p><a href="#" onclick="$('#collapse-e6a8467c-show, #collapse-e6a8467c-hide').toggle(); $('#collapse-e6a8467c').fadeToggle(150);; return false;" id="collapse-e6a8467c-show" class="icon icon-collapsed collapsible">iso posts example with _SKIP_CHAINED_DEPS</a><a href="#" onclick="$('#collapse-e6a8467c-show, #collapse-e6a8467c-hide').toggle(); $('#collapse-e6a8467c').fadeToggle(150);; return false;" id="collapse-e6a8467c-hide" class="icon icon-expanded collapsible" style="display:none;">iso posts example with _SKIP_CHAINED_DEPS</a><div id="collapse-e6a8467c" class="collapsed-text" style="display:none;"><p>openqa-cli api --pretty --osd -X POST isos ISO=SLE-15-SP5-Online-aarch64-Build80.1-Media1.iso DISTRI=sle VERSION=15-SP5 FLAVOR=Online ARCH=aarch64 BUILD=80.1 TEST=hpc_BETA_mvapich2_mpi_supportserver _GRPOUP_ID=130 _SKIP_CHAINED_DEPS=1<br>
{<br>
"count" : 1,<br>
"failed" : [],<br>
"ids" : [<br>
10698186<br>
],<br>
"scheduled_product_id" : 1768410</p>
</div></p>
<p>All children has <code>PARALLEL_WITH=hpc_BETA_mpich_mpi_supportserver</code> on Test Suites</p>
<p>openQA test in scenario sle-15-SP5-Online-x86_64-hpc_BETA_mpich_mpi_supportserver@64bit fails in<br>
<a href="https://openqa.suse.de/tests/10691528/modules/wait_children/steps/7" class="external">wait_children</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Basic tests of mpich with CPU count=2. Maintainer: schlad <a href="mailto:schlad@suse.de">schlad@suse.de</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/10691528" class="external">80.1</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p><a href="#" onclick="$('#collapse-f7b34679-show, #collapse-f7b34679-hide').toggle(); $('#collapse-f7b34679').fadeToggle(150);; return false;" id="collapse-f7b34679-show" class="icon icon-collapsed collapsible">should look like</a><a href="#" onclick="$('#collapse-f7b34679-show, #collapse-f7b34679-hide').toggle(); $('#collapse-f7b34679').fadeToggle(150);; return false;" id="collapse-f7b34679-hide" class="icon icon-expanded collapsible" style="display:none;">should look like</a><div id="collapse-f7b34679" class="collapsed-text" style="display:none;"><p>openqa-cli api --pretty --osd -X POST isos ISO=SLE-15-SP5-Online-x86_64-Build80.1-Media1.iso DISTRI=sle VERSION=15-SP5 FLAVOR=Online ARCH=x86_64 BUILD=80.1 TEST=hpc_BETA_mpich_mpi_supportserver,hpc_BETA_mpich_mpi_slave01,hpc_BETA_mpich_mpi_slave00,hpc_BETA_mpich_mpi_master _GRPOUP_ID=130 _SKIP_CHAINED_DEPS=1<br>
{<br>
"count" : 4,<br>
"failed" : [],<br>
"ids" : [<br>
10698191,<br>
10698192,<br>
10698193,<br>
10698194<br>
],<br>
"scheduled_product_id" : 1768412<br>
}</p>
</div><br>
Last good: <a href="https://openqa.suse.de/tests/10687724" class="external">80.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=hpc_BETA_mpich_mpi_supportserver&version=15-SP5" class="external">latest</a></p>
qe-yam - action #113725 (Rejected): Make autoyast tests exit when the autoyast profile encounter ...https://progress.opensuse.org/issues/1137252022-07-18T13:35:03Zybonatakisioannis.bonatakis@suse.com
<a name="observation"></a>
<h1 >observation<a href="#observation" class="wiki-anchor">¶</a></h1>
<p>What happens is that when the autoyast profile is wrong or not found, the tests keep trying to match needles and continue.</p>
<p>One such case is [0]. The problem appears something like 5 minutes after it starts but keeps running for 2h where the job time limits are reached.<br>
Because this cause a slow feedback loop of the tests, in combination of the resources which are occupied without any good reason i would like to propose a solution.</p>
<p>the easier would be to match a needle with the popup and abort. <br>
I dont know if there is already a module for it but we could run a check on the xml profile before installation module. I am not sure but i think there was something implemented for this specific reason. </p>
<p>To reproduce:<br>
you can use <a href="https://gist.github.com/b10n1k/bca22757c5e4eb11473ceda30820f6d2" class="external">https://gist.github.com/b10n1k/bca22757c5e4eb11473ceda30820f6d2</a> as <u>profile.xml</u></p>
<p>Actual results:<br>
<a href="http://aquarius.suse.cz/tests/11324#step/installation/2" class="external">http://aquarius.suse.cz/tests/11324#step/installation/2</a></p>
<p>Expected:<br>
i am not sure about that. should that be one of the following:</p>
<ul>
<li>Exit after some rational time when the error exists.</li>
<li>terminate needle checking after some expected time??
the while loop have specific expectations during installation. When those expectation do not ever match, the loop run for even.</li>
<li>Validate xml before installation and exit then if problem appears</li>
</ul>
<p>[0] <a href="http://aquarius.suse.cz/tests/11324" class="external">http://aquarius.suse.cz/tests/11324</a></p>
openQA Project - action #109292 (Resolved): OSD is missing x86_64 jobs duplicate key value violat...https://progress.opensuse.org/issues/1092922022-03-31T07:57:01Zybonatakisioannis.bonatakis@suse.com
<p>With the last two (117.1,118.3) or three builds x86_64 jobs are missing.</p>
<p>The very first time there was a dependency circle issue with one of the job group yaml. That found to prevent the scheduling. However the jobs are keep missing even after the correction and the scheduling looks to work without problem after manual intervention.</p>
openQA Project - action #107878 (Resolved): number of failed job provides wrong value on the buil...https://progress.opensuse.org/issues/1078782022-03-04T11:13:23Zybonatakisioannis.bonatakis@suse.com
<p><a href="https://openqa.suse.de/group_overview/130" class="external">https://openqa.suse.de/group_overview/130</a> display 2 failed jobs for build101.1.</p>
<p>if you press on the failed area of the bar, the <code>Test result overview</code> shows only one failed job. Cleaning all the filters i see that the only other job which was not successful is one failed as <code>timeout_exceeded</code>. </p>
<p>So either the <u>failed area</u> should enabled the <code>Timeout exceeded</code>(or any other flag) or it bar should point out only the actual failed jobs.</p>
openQA Tests - action #107395 (Resolved): [HPC] zypper returns error code 107 in slurm_masterhttps://progress.opensuse.org/issues/1073952022-02-23T19:04:58Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<pre><code>(4/6) Installing: twopence-0.4.2-3.d_t.22.x86_64 [.
warning: /var/cache/zypp/packages/devel_tools/x86_64/twopence-0.4.2-3.d_t.22.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 498d5a23: NOKEY
.....
/usr/lib/tmpfiles.d/net-snmp.conf:1: Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly.
/usr/lib/tmpfiles.d/systemd.conf:19: Failed to resolve user 'systemd-network': No such process
/usr/lib/tmpfiles.d/systemd.conf:20: Failed to resolve user 'systemd-network': No such process
/usr/lib/tmpfiles.d/systemd.conf:21: Failed to resolve user 'systemd-network': No such process
/usr/lib/tmpfiles.d/systemd.conf:22: Failed to resolve user 'systemd-network': No such process
warning: %post(twopence-0.4.2-3.d_t.22.x86_64) scriptlet failed, exit status 65
done]
(5/6) Installing: libtwopence0-0.4.2-3.d_t.22.x86_64 [.
warning: /var/cache/zypp/packages/devel_tools/x86_64/libtwopence0-0.4.2-3.d_t.22.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 498d5a23: NOKEY
......done]
(6/6) Installing: twopence-shell-client-0.4.2-3.d_t.22.x86_64 [.
warning: /var/cache/zypp/packages/devel_tools/x86_64/twopence-shell-client-0.4.2-3.d_t.22.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 498d5a23: NOKEY
.......done]
n3BEE-107-
</code></pre>
<p>107 - ZYPPER_EXIT_INF_RPM_SCRIPT_FAILED means "Installation basically succeeded, but some of the packages %post install scripts returned an error"</p>
<p>openQA test in scenario sle-15-SP4-Online-x86_64-hpc_EPSILON_slurm_master@64bit fails in<br>
<a href="https://openqa.suse.de/tests/8218862/modules/slurm_master/steps/162" class="external">slurm_master</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>HPC cluster for experimental and fast-moving external tests. maintainer: <a href="mailto:schlad@suse.de">schlad@suse.de</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/8205633" class="external">99.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/8181333" class="external">98.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=hpc_EPSILON_slurm_master&version=15-SP4" class="external">latest</a></p>
openQA Project - action #98577 (Resolved): Unknown ARRAY( variables matching HDD_1 or ISO in job ...https://progress.opensuse.org/issues/985772021-09-14T07:08:55Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<ul>
<li>For instance <a href="https://openqa.suse.de/tests/7092033/file/vars.json" class="external">https://openqa.suse.de/tests/7092033/file/vars.json</a> has <code>"ARRAY(0x55bb116ac3a0)" : "SLE-15-SP3-Full-x86_64-GM-Media1.iso"</code> which is repeated and assigned correctly on <code>ISO</code>.</li>
<li>Another one on publiccloud <a href="https://openqa.suse.de/tests/7096497/file/vars.json" class="external">https://openqa.suse.de/tests/7096497/file/vars.json</a> has <code>"ARRAY(0x55b5694714b8)" : "publiccloud_15sp3_Azure_BYOS_Updates.qcow2"</code> which is what <code>HDD_1</code> represents.</li>
</ul>
<p>i havent noticed any destruction or impact on the test so far but i havent also found where this comes from.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: No variables based on stringified array types present in job settings</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Add unit test validating variable names (assuming this is a bug in openQA or os-autoinst)</li>
<li>Mark jobs with variable names containing <code>(</code> as incomplete (assuming this is a bug in another tool)</li>
</ul>
openQA Project - action #98388 (Resolved): Non-existing asset "uefi-vars" is still shown up on #d...https://progress.opensuse.org/issues/983882021-09-09T09:38:23Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>An example is <a href="https://openqa.suse.de/tests/6994628#downloads" class="external">https://openqa.suse.de/tests/6994628#downloads</a></p>
<p>When i clone the job it fails with</p>
<pre><code>downloading
http://openqa.suse.de/tests/6994628/asset/other/SLE-15-SP4-Online-x86_64-Build31.2-Media1.iso.sha256
to
/var/lib/openqa/factory/other/SLE-15-SP4-Online-x86_64-Build31.2-Media1.iso.sha256
downloading
http://openqa.suse.de/tests/6994628/asset/iso/SLE-15-SP4-Online-x86_64-Build31.2-Media1.iso
to
/var/lib/openqa/factory/iso/SLE-15-SP4-Online-x86_64-Build31.2-Media1.iso
downloading
http://openqa.suse.de/tests/6994628/asset/hdd/SLES-15-SP4-x86_64-Build31.2-containers.qcow2
to
/var/lib/openqa/factory/hdd/SLES-15-SP4-x86_64-Build31.2-containers.qcow2
downloading
http://openqa.suse.de/tests/6994628/asset/hdd/SLES-15-SP4-x86_64-Build31.2-containers-uefi-vars.qcow2
to
/var/lib/openqa/factory/hdd/SLES-15-SP4-x86_64-Build31.2-containers-uefi-vars.qcow2
6994628 failed: 404 Not Found
</code></pre>
<p><a href="https://openqa.suse.de/tests/6994628/asset/hdd/SLES-15-SP4-x86_64-Build31.2-containers-uefi-vars.qcow2" class="external">uefi-vars qcow2</a> seems that it is not available any more and if you try to get this file you get 404.</p>
<p>Expected:</p>
<ul>
<li>ui should not show non-available assets</li>
</ul>
<a name="Steps-to-reproduce"></a>
<h2 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<p>Clone the job in the description, it returns a 404 error for an asset still shown in the UI page</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Investigate why is it still shown in the UI page if the cleanup removes it</li>
<li>Investigate why this is removed (if it is from the cleanup script) but not the rest</li>
<li>Fix UI so that it doesn't show non-available assets</li>
<li>(optional) i wonder if the cleanup can be more clever and keep the relevant assets</li>
</ul>
openQA Project - action #89077 (Resolved): os-autoinst Makefile is missing symlinks configurationhttps://progress.opensuse.org/issues/890772021-02-24T15:57:21Zybonatakisioannis.bonatakis@suse.com
<p>i tried to use a forked os-autoinst on my local OpenQA instance following the steps from the documentation[0].</p>
<p>From the root of the forked repository i run <code>make</code> which finished without a problem and i started a worker with<br>
<code>sudo /usr/bin/perl /usr/share/openqa/script/worker --isotovideo /home/iob/os-autoinst-distri-opensuse/os-autoinst/isotovideo --instance 1</code><br>
Although the job was complaining about <br>
<code>Please build the tinycv bindings first (see os-autoinst's README)</code>.[1]</p>
<p>With the help of <a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a> we found that running <code>make symlinks</code> fixes the issue.<br>
Looking around i believe that the link that was missing was </p>
<pre><code>lrwxrwxrwx 1 iob users 68 Feb 24 16:06 videoencoder -> /home/iob/os-autoinst-distri-opensuse/os-autoinst/build/videoencoder
</code></pre>
<p>Expected:<br>
jobs which use that instance should run without a problem</p>
<p>Actual:<br>
Jobs fails to run asking to build tinycv which it should have done so from the <code>make</code></p>
<p>[0] <a href="https://github.com/os-autoinst/os-autoinst#build-instructions" class="external">https://github.com/os-autoinst/os-autoinst#build-instructions</a><br>
[1] <a href="http://aquarius.suse.cz/tests/5013" class="external">http://aquarius.suse.cz/tests/5013</a></p>
qe-yam - action #71026 (Rejected): [y] Validate updated package version with self_updatehttps://progress.opensuse.org/issues/710262020-09-07T07:33:28Zybonatakisioannis.bonatakis@suse.com
<p>With the work on <a href="https://bugzilla.suse.com/show_bug.cgi?id=1175614" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1175614</a> done, we can check what version the self update download and use in the inst-sys. Rodion has already created validation module <code>tests/installation/validate_self_update.pm</code> checking that the feature attempts to download some packages from the update repo but it does not check/compare the package version between the default inst-sys and the update repo. The inst-sys stores the package version in <code>/.packages.root</code>. With yast2-installation-4.3.16 and above we should find <code>/.packages.self_update</code> file which we can use to compare</p>
openQA Tests - action #70726 (Resolved): [y] Generate dud file dynamically instead of relying on ...https://progress.opensuse.org/issues/707262020-08-31T10:51:46Zybonatakisioannis.bonatakis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Test fails because the <a href="ftp://openqa.suse.de/SLE-15-Module-Development-Tools-POOL-x86_64-Media1-CURRENT" class="external">ftp://openqa.suse.de/SLE-15-Module-Development-Tools-POOL-x86_64-Media1-CURRENT</a> is not available. </p>
<p>Validation and setup are introduced in <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10770/files" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10770/files</a> but we need a better approach.</p>
<p>We have <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/dev_tools.dud" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/dev_tools.dud</a> which is basically tarball created with <code>mkdud</code>. Detailed steps are described here:<br>
<code>https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/Development_Guide.md#updating-driver-update-disk-dud-file</code></p>
<p>As per comment below, we have option to pre-install <code>mkdud</code> tool on all 64bit workers, which is a bit of an overkill, but solves the issue: <a href="https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/server.sls" class="external">https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/server.sls</a></p>
<p>As an alternative we can use chained jobs and boot into installed image and generate the dud. To make it more stable we could have used support server image here.</p>
<p>See <a href="http://open.qa/api/testapi/#_upload_asset" class="external">http://open.qa/api/testapi/#_upload_asset</a> for uploading asset. <code>REPO_SLE_MODULE_DEVELOPMENT_TOOLS</code> variable contains the name of the repo.</p>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-dud_development_tools@64bit fails in<br>
<a href="https://openqa.suse.de/tests/4619201/modules/validate_dud_addon_repos/steps/17" class="external">validate_dud_addon_repos</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Same as dud_sdk, but due to bsc#1080292 we cannot use ISO. FTP url is used instead. Limitation is that we use x86_64 url, as cannot create DUD in the runtime, so test cannot be executed on other architectures.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/4611536" class="external">18.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/4587953" class="external">18.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=dud_development_tools&version=15-SP3" class="external">latest</a></p>
qe-yam - action #69259 (Rejected): [y] Test fully qualified domain name as an input for yast2-net...https://progress.opensuse.org/issues/692592020-07-23T06:10:53Zybonatakisioannis.bonatakis@suse.com
<p>Although it is recommended to not use a FQDN as the static hostname there is not a restriction in the kernel or hostnamectl to use it and thus, there should not be a restriction in YaST in case that the user has a use case in which it is needed. YaST has recent changes in yast2-network to address this.</p>
<p>This is not typical use case, so low priority.</p>
openQA Project - action #68146 (Resolved): Implement colored and interactive logshttps://progress.opensuse.org/issues/681462020-06-16T13:26:51Zybonatakisioannis.bonatakis@suse.com
<p>As tester<br>
I would like to have colored and interactive logs<br>
To explore and find the context easier</p>
<p>As a part of this, it would be great to have ability to open logs at the time when screenshot is made in Job Overview.</p>
openQA 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>