openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-01-17T08:59:42ZopenSUSE Project Management Tool
Redmine ALP - action #153760 (Resolved): [qe-core]Adapt svirt backend to be able to boot systems with roo...https://progress.opensuse.org/issues/1537602024-01-17T08:59:42Zjlausuchjalausuch@suse.com
<p>ALP images (following Factory approach) do not allow root ssh by default, the best practices are to use a key-pair to ssh to the system.</p>
<p>There is a way to enable it, which consists of installing the package <code>openssh-server-config-rootlogin</code>, which is simply doing <code>echo 'PermitRootLogin yes' >> /etc/sshd/sshd_config.d/root_login_config.</code>.</p>
<p>Our svirt backend rely on doing a root ssh to the machine after it's booted, therefore it fails to do so.</p>
<p>There are several ideas to workaround this:<br>
1) Add <code>echo 'PermitRootLogin yes' >> /etc/sshd/sshd_config.d/root_login_config >$pty</code> to the svirt backend commands. <br>
2) Create a keypair for each run and inject it to the VM using svirt backend commands. <br>
3) Create new combustion script for s390x including the command `echo 'PermitRootLogin yes' >> /etc/sshd/sshd_config.d/root_login_config</p>
<a name="Acceptance-criteria"></a>
<h3 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h3>
<ul>
<li>ALP s390x images boot with svirt backend</li>
</ul>
ALP - action #126716 (Resolved): test fails in run_container_in_k3s - /usr/bin/k3s-install: No su...https://progress.opensuse.org/issues/1267162023-03-27T13:48:34Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario alp-micro-0.1-Default-x86_64-k3s@64bit fails in<br>
<a href="https://openqa.opensuse.org/tests/3194054/modules/run_container_in_k3s/steps/17" class="external">run_container_in_k3s</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>The base test suite is used for job templates defined in YAML documents. It has no settings of its own.</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.opensuse.org/tests/3183089" class="external">5.2</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.opensuse.org/tests/latest?arch=x86_64&distri=alp&flavor=Default&machine=64bit&test=k3s&version=micro-0.1" class="external">latest</a></p>
ALP - action #125855 (Resolved): Create OBS-sync scripts for ALP Micro and Bedrockhttps://progress.opensuse.org/issues/1258552023-03-13T07:52:34Zjlausuchjalausuch@suse.com
<p>Create new sync scripts in <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">openqa-trigger-from-obs</a></p>
<p>Currently we have 2 sync scripts that we used for the ALP December prototype:<br>
<a href="https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE:ALP:ToTest.xml" class="external">https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE:ALP:ToTest.xml</a><br>
<a href="https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE:ALP:Staging.xml" class="external">https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE:ALP:Staging.xml</a></p>
<p>But this project in IBS is obsolete and we should now sync the new images from the 2 new IBS projects:<br>
<a href="https://build.opensuse.org/project/show/SUSE:ALP:Products:Micro:0.1" class="external">https://build.opensuse.org/project/show/SUSE:ALP:Products:Micro:0.1</a><br>
<a href="https://build.opensuse.org/project/show/SUSE:ALP:Products:Bedrock:0.1" class="external">https://build.opensuse.org/project/show/SUSE:ALP:Products:Bedrock:0.1</a></p>
<p><a href="https://download.opensuse.org/repositories/SUSE:/ALP:/Products:/" class="external">https://download.opensuse.org/repositories/SUSE:/ALP:/Products:/</a></p>
<a name="Acceptance-Criteria"></a>
<h2 >Acceptance Criteria<a href="#Acceptance-Criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create new sync script for ALP Micro in <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">openqa-trigger-from-obs</a></li>
<li>Create new sync script for ALP Bedrock in <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">openqa-trigger-from-obs</a></li>
</ul>
ALP - action #125852 (Resolved): Create 2 new job groups in openqa.opensuse.org to hold the 2 new...https://progress.opensuse.org/issues/1258522023-03-13T07:44:11Zjlausuchjalausuch@suse.com
<p>So far, we have been using a <a href="https://openqa.opensuse.org/group_overview/100" class="external">job group</a> for ALP images, but that product in IBS is obsolete.</p>
<p>Instead, we now have 2 flavors corresponding to the 2 new products (see epic).</p>
<p>For now, we can keep the set of test suites the same as we had for ALP December, and we can do modifications as needed.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create 2 new jobs in O3: <code>ALP-Micro</code> and <code>ALP-Bedrock</code></li>
<li>Create corresponding mediums</li>
<li>Create the content of the groups in <a href="https://github.com/os-autoinst/opensuse-jobgroups" class="external">opensuse-jobgroups</a></li>
</ul>
ALP - coordination #125846 (Resolved): [epic] March Prototype testinghttps://progress.opensuse.org/issues/1258462023-03-13T07:20:30Zjlausuchjalausuch@suse.com
<p>For March prototype we have a 2 main deliverables:</p>
<ul>
<li><a href="https://confluence.suse.com/display/LEONG/01+SUSE+ALP+Bedrock" class="external">ALP Bedrock</a></li>
<li><a href="https://confluence.suse.com/display/LEONG/03+SUSE+ALP+Micro" class="external">ALP Micro</a></li>
</ul>
<p>Bedrock is like generic server-flavor OS and Micro is similar to SLE Micro or MicroOS flavor with limited set of packages.</p>
<p>QE Department has to provide test coverage for all the <a href="https://jira.suse.com/issues/?jql=project%20%3D%20PED%20AND%20fixVersion%20%3D%20%22ALP%20March%20Prototype%22" class="external">features</a> and all the images in the 2 flavors.</p>
<p>This epic aims to collect all the needed tickets related to March prototype testing.</p>
openQA Tests - action #116257 (New): [virtualization][svirt] Some workers in openqaworker2 time o...https://progress.opensuse.org/issues/1162572022-09-06T06:57:39Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP5-JeOS-for-kvm-and-xen-Updates-x86_64-jeos-extratest@svirt-xen-hvm fails in<br>
<a href="https://openqa.suse.de/tests/9459035/modules/bootloader_svirt/steps/25" class="external">bootloader_svirt</a></p>
<p>It hits the <code>MAX_JOB_TIMEOUT</code> while trying to copy the image. </p>
<p>The affected workers are:<br>
<a href="https://openqa.suse.de/admin/workers/366" class="external">openqaworker2:9</a><br>
<a href="https://openqa.suse.de/admin/workers/980" class="external">openqaworker2:10</a><br>
<a href="https://openqa.suse.de/admin/workers/1252" class="external">openqaworker2:16</a></p>
<p>Most jobs using these workers time out during this step. Other examples:<br>
<a href="https://openqa.suse.de/tests/9459036" class="external">https://openqa.suse.de/tests/9459036</a><br>
<a href="https://openqa.suse.de/tests/9459031" class="external">https://openqa.suse.de/tests/9459031</a><br>
<a href="https://openqa.suse.de/tests/9459037" class="external">https://openqa.suse.de/tests/9459037</a><br>
<a href="https://openqa.suse.de/tests/9459064" class="external">https://openqa.suse.de/tests/9459064</a><br>
<a href="https://openqa.suse.de/tests/9459069" class="external">https://openqa.suse.de/tests/9459069</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/9459035" class="external">20220905-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/9450196" class="external">20220903-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=JeOS-for-kvm-and-xen-Updates&machine=svirt-xen-hvm&test=jeos-extratest&version=12-SP5" class="external">latest</a></p>
ALP - action #114935 (Resolved): Add standard container host tests for ALP prototype in O3https://progress.opensuse.org/issues/1149352022-08-03T07:39:42Zjlausuchjalausuch@suse.com
<p>There are currently no container tests for ALP prototype.</p>
<p>The idea is to enable the same set of tests that are run for MicroOS/Leap-Micro, e.g. <a href="https://openqa.opensuse.org/tests/2433988" class="external">https://openqa.opensuse.org/tests/2433988</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria:<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<p>Create a new jobs <code>alp_containers</code> for the flavors <code>kvm-and-xen</code> and <code>kvm-and-xen_NonTransactional</code> which schedules the following modules:</p>
<pre><code>- toolbox
- podman
- image_podman
- podman_3rd_party_images
- podman_pods
- rootless_podman
</code></pre> ALP - action #112826 (Resolved): Fix ALP SelfInstall jobshttps://progress.opensuse.org/issues/1128262022-06-21T21:27:06Zjlausuchjalausuch@suse.com
<p>These jobs fail booting the image:<br>
<a href="https://openqa.opensuse.org/tests/2427880#step/bootloader_uefi/2" class="external">https://openqa.opensuse.org/tests/2427880#step/bootloader_uefi/2</a></p>
<p>Expected result (Leap Micro):<br>
<a href="https://openqa.opensuse.org/tests/2426647#step/bootloader_uefi/3" class="external">https://openqa.opensuse.org/tests/2426647#step/bootloader_uefi/3</a></p>
ALP - action #112427 (Resolved): 5. Adapt transactional server related test cases for ALPhttps://progress.opensuse.org/issues/1124272022-06-14T16:09:51Zjlausuchjalausuch@suse.com
<p>The idea for the first PoC for ALP testing in openQA is to copy what we already have for Leap Micro/MicroOS.<br>
So, taking this job as an example: <a href="https://openqa.opensuse.org/tests/2351803" class="external">https://openqa.opensuse.org/tests/2351803</a><br>
we should basically get the same results but executing them on ALP images.</p>
<p>The used schedule in this case is <a href="https://openqa.opensuse.org/tests/2351803/settings/schedule/sle-micro/raw_image.yaml" class="external">https://openqa.opensuse.org/tests/2351803/settings/schedule/sle-micro/raw_image.yaml</a><br>
But a different approach could be used (e.g <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/products/microos/main.pm" class="external">main.pm</a>).</p>
ALP - action #112424 (Resolved): 4. Enable OBS sync for ALP images for openQAhttps://progress.opensuse.org/issues/1124242022-06-14T16:06:33Zjlausuchjalausuch@suse.com
<p>To be able to trigger new openQA test for every build of ALP images, we need to enable this configuration into <a href="https://github.com/os-autoinst/openqa-trigger-from-obs" class="external">https://github.com/os-autoinst/openqa-trigger-from-obs</a>.</p>
<p>The OBS project to sync is: <code>devel:LEO/ALP</code>: <a href="https://build.opensuse.org/package/show/devel:LEO/ALP" class="external">https://build.opensuse.org/package/show/devel:LEO/ALP</a><br>
The images are available for download here: <a href="https://download.opensuse.org/repositories/devel:/LEO/images/" class="external">https://download.opensuse.org/repositories/devel:/LEO/images/</a><br>
We need to sync the following flavors (for now):</p>
<ul>
<li>kvm-and-xen</li>
<li>kvm-and-xen_NonTransactional</li>
<li>SelfInstall</li>
<li>SelfInstall_NonTransactional</li>
</ul>
<p>and also sync the repository so that we can use the <code>SCC_URL</code> variable pointing to local assets.</p>
ALP - action #112421 (Resolved): 3. Create a new product in os-autoinst-distri-opensusehttps://progress.opensuse.org/issues/1124212022-06-14T16:03:47Zjlausuchjalausuch@suse.com
<p>Since we are going to use <code>DISTRI=alp</code> for new ALP tests in openQA, we need to add the product to<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/products" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/products</a><br>
And also in O3 machine (ariel).</p>
<pre><code>/var/lib/openqa/share/tests> ll
total 4
lrwxrwxrwx 1 geekotest nogroup 8 Apr 5 10:34 d-installer -> opensuse
lrwxrwxrwx 1 root root 8 Sep 4 2017 kubic -> opensuse
lrwxrwxrwx 1 geekotest nogroup 8 Mar 30 15:36 leap-micro -> opensuse
lrwxrwxrwx 1 geekotest nogroup 8 Apr 16 2019 microos -> opensuse
drwxr-xr-x 5 geekotest nogroup 121 Feb 11 2020 obs
lrwxrwxrwx 1 root root 6 Jan 16 2019 openQA -> openqa
drwxr-xr-x 6 geekotest nogroup 166 Oct 11 2021 openqa
drwxr-xr-x 15 geekotest nogroup 4096 Jun 13 12:08 opensuse
drwxr-xr-x 4 geekotest nogroup 65 Apr 16 2020 repositories
lrwxrwxrwx 1 root root 8 Jul 22 2016 windows -> opensuse
</code></pre>
<p>we would need another symlinc to <code>alp -> opensuse</code>.</p>
openQA Project - action #111314 (Workable): _SECRET_ variables are exposed in vars.json when the ...https://progress.opensuse.org/issues/1113142022-05-19T11:03:37Zjlausuchjalausuch@suse.com
<p>Some workers contain sensitive information using <code>_SECRET</code> variables. Those variables are hidden in the settings tab and in vars.json, as expected.<br>
However, if you restart or clone a job and cancel it while it's running, those variables are exposed in vars.json</p>
<p><img src="https://progress.opensuse.org/attachments/download/13268/vars.png" alt="" loading="lazy" /></p>
<p>NOTE: I don't want to provide links as I might give too many hints for a public place.</p>
openQA Project - action #111135 (New): Enhance email notification message content for about faile...https://progress.opensuse.org/issues/1111352022-05-16T07:57:05Zjlausuchjalausuch@suse.com
<p>The new feature introduced by <a href="https://progress.opensuse.org/issues/91605" class="external">https://progress.opensuse.org/issues/91605</a> is very useful to notify people in different ways (direct email or to Slack, which will turn into Slack message). However, those messages could be improved adding some extra information about the test name, the group name, etc.</p>
<p>This is an example of how a message in Slack looks like:<br>
<img src="https://progress.opensuse.org/attachments/download/13239/slack_message.png" alt="" loading="lazy" /></p>
<p>So, a proposal from my side could be:</p>
<pre><code>Unknown issue to be reviewed.
OpenQA test https://openqa.suse.de/tests/8762619 fails with
"Test died: script timeout: docker info at /usr/lib/os-autoinst/distribution.pm line 296."
</code></pre>
<p>I guess it's difficult to include the reason given by the failure, so something like this could be also helpful:</p>
<pre><code>Unknown issue to be reviewed.
OpenQA test https://openqa.suse.de/tests/8762619 fails in docker.
Job Group: 427 - Maintenance: Test Repo / Public Cloud Maintenance Updates
Build: 20220515-1
Flavor: AZURE-CHOST-BYOS-Updates
</code></pre>
<p>similar to when you report a poo ticket directly from the UI. </p>
openQA Tests - action #111093 (New): [containers][sporadic][s389x] test fails in boot_to_desktop ...https://progress.opensuse.org/issues/1110932022-05-13T13:22:29Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-BCI-Updates-s390x-bci_on_SLES_15-SP2_host_docker@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/8753928/modules/boot_to_desktop/steps/28" class="external">boot_to_desktop</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>The base test suite is used for job templates defined in YAML documents. It has no settings of its own.</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/8753928" class="external">_15-SP4_10.47_minimal-image</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/8744352" class="external">_15-SP4_3.9_python-3.10-image</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=BCI-Updates&machine=s390x-kvm-sle12&test=bci_on_SLES_15-SP2_host_docker&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #95697 (New): [kernel][jeos][opensuse] Have a common way to add LTP reposit...https://progress.opensuse.org/issues/956972021-07-20T08:34:37Zjlausuchjalausuch@suse.com
<p>Currently, LTP tests in SLE use QA_HEAD_REPO variable<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/kernel/install_ltp.pm" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/kernel/install_ltp.pm</a></p>
<pre><code> if (is_sle) {
add_qa_head_repo;
return;
}
</code></pre>
<p>Then, for openSUSE, the openSUSE tests, the condition is a bit complex:</p>
<pre><code> my $arch = '';
$arch = "_PowerPC" if is_ppc64le();
$arch = "_zSystems" if is_s390x();
$arch = ((is_x86_64 || is_aarch64) ? "Tumbleweed" : "Factory") . $arch;
$repo = "https://download.opensuse.org/repositories/benchmark:/ltp:/devel/openSUSE_$arch/";
</code></pre>
<p>and even more complex after <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12902" class="external">this PR</a>.</p>
<p>The idea behind this ticket is to use the same function (e.g. <code>add_qa_head_repo</code>) for ALL distri/versions using a single variable (e.g. <code>QA_HEAD_REPO</code>) pointing to the repository to be used, instead of hardcoding the repository with several conditions in the code. This would affect all the kernel jobs (also for JeOS-kernel jobs) for TW and Leap in O3.</p>