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>
openQA Tests - action #151738 (Feedback): [qe-core] Enable systemd-testsuite in 15-SP6https://progress.opensuse.org/issues/1517382023-11-30T09:41:09Zjlausuchjalausuch@suse.com
<a name="Background"></a>
<h2 >Background<a href="#Background" class="wiki-anchor">¶</a></h2>
<p>There is an important update for systemd in 15-SP6 to v254: <a href="https://jira.suse.com/browse/PED-4846" class="external">https://jira.suse.com/browse/PED-4846</a><br>
Some important partners are a bit worried about this update and have asked us to please make sure this doesn't break any application (e.g. SAP applications).<br>
We can't ensure 3rd party applications will be ok with this update, but what we can do is to provide good coverage for systemd testing (of course, SAP part will be covered by SAP squad). </p>
<p><code>systemd-testsuite</code> has been integrated in openQA and enabled in TW by Martin Loviska when he was on rotation. e.g. <a href="https://openqa.opensuse.org/tests/3760221" class="external">https://openqa.opensuse.org/tests/3760221</a><br>
It was also enabled in 15-SP4 and SP5 after GA, but the package is already in 15-SP6 channel <a href="http://download.suse.de/download/ibs/SUSE:/SLE-15-SP6:/GA/standard/x86_64/systemd-testsuite-254.5-150600.1.2.x86_64.rpm" class="external">http://download.suse.de/download/ibs/SUSE:/SLE-15-SP6:/GA/standard/x86_64/systemd-testsuite-254.5-150600.1.2.x86_64.rpm</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><code>systemd-testsuite</code> is scheduled in 15-SP6 functional group.</li>
</ul>
<p>Related slack thead: <a href="https://suse.slack.com/archives/C02CSAZLAR4/p1701087663691749" class="external">https://suse.slack.com/archives/C02CSAZLAR4/p1701087663691749</a></p>
openQA Project - action #113219 (Closed): Create a master label at job group level to label all t...https://progress.opensuse.org/issues/1132192022-07-04T18:53:37Zjlausuchjalausuch@suse.com
<p>As a openQA user, I would like to have a feature to label all the jobs of the same build at the same time with certain <code>bsc</code> or <code>poo</code>, instead of labeling one by one.</p>
<p>A possible use case is in container image tests (BCI) where a new container image build is tested on multiple host versions and architectures to be validated. Sometimes, the image is faulty and we need to label all the jobs (~40) which makes thing very time consuming for the reviewer.<br>
For example, <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=7.12_pcp-image&groupid=445" class="external">this build</a> or <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP4&build=7.9_pcp-image&groupid=445" class="external">this</a> are mostly failed tests.</p>
<p>It would be nice to use the <code>tag</code> feature + the <code>build</code> number doing something like this:<br>
<img src="https://progress.opensuse.org/attachments/download/13487/Screenshot%202022-07-04%20at%2020.52.21.png" alt="" loading="lazy" /><br>
and automatically label all the jobs.</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 #110566 (Resolved): [tools] Problem with ISOS Post command from OBS synchttps://progress.opensuse.org/issues/1105662022-05-03T09:57:28Zjlausuchjalausuch@suse.com
<p>The latest OSD 15-SP4 JeOS (Minimal-VM) jobs have only been triggered for Raspbery-Pi flavor:<br>
This is the OBS sync log: <a href="https://openqa.suse.de/admin/obs_rsync/SUSE:SLE-15-SP4:GA:TEST%7Cjeos/runs/.run_last/download/openqa.cmd.log" class="external">https://openqa.suse.de/admin/obs_rsync/SUSE:SLE-15-SP4:GA:TEST%7Cjeos/runs/.run_last/download/openqa.cmd.log</a></p>
<p>Looking at the product scheduled:<br>
<a href="https://openqa.suse.de/admin/productlog?id=910513" class="external">https://openqa.suse.de/admin/productlog?id=910513</a></p>
<pre><code>Results
{
"failed_job_info": [],
"successful_job_ids": [
8676719,
8676726,
8676732,
8676735,
8676742,
8676748,
8676753,
8676758
]
}
</code></pre>
<p>this is what I would expect from other isos post, but for instance:<br>
<a href="https://openqa.suse.de/admin/productlog?id=910516" class="external">https://openqa.suse.de/admin/productlog?id=910516</a> or <br>
<a href="https://openqa.suse.de/admin/productlog?id=910515" class="external">https://openqa.suse.de/admin/productlog?id=910515</a><br>
have empty results:</p>
<pre><code>Results
No results available.
</code></pre>
<p>and the jobs were not scheduled at all. </p>
openQA Tests - action #109046 (Resolved): [tools] auto_review:"Unable to find image SLES15-SP3-Je...https://progress.opensuse.org/issues/1090462022-03-28T06:23:08Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP4-Migration-from-SLE12-SPx-s390x-offline_sles12sp3_ltss_pscc_asmm-lgm_all_full@s390x-kvm-sle15 fails in<br>
<a href="https://openqa.suse.de/tests/8415599/modules/bootloader_zkvm/steps/18" class="external">bootloader_zkvm</a><br>
But the qcow exists:</p>
<pre><code>$ /var/lib/openqa/share/factory/hdd/fixed> ll SLES-12-SP3-s390x-GM-gnome-allpatterns.qcow2
-rw-r--r-- 1 geekotest nogroup 14485946368 Jan 14 08:45 SLES-12-SP3-s390x-GM-gnome-allpatterns.qcow2
</code></pre>
<p>And the asset is actually there:<br>
<img src="https://progress.opensuse.org/attachments/download/13001/hdd.png" alt="" loading="lazy" /></p>
<p>It happens in all jobs with <code>svirt</code> backend that have their HDD in fixed directory. So, all s390x jobs and some others that use that backend too:<br>
Examples:<br>
<a href="https://openqa.suse.de/tests/8414273" class="external">https://openqa.suse.de/tests/8414273</a><br>
<a href="https://openqa.suse.de/tests/8414268" class="external">https://openqa.suse.de/tests/8414268</a><br>
<a href="https://openqa.suse.de/tests/8414272" class="external">https://openqa.suse.de/tests/8414272</a><br>
<a href="https://openqa.suse.de/tests/8414267" class="external">https://openqa.suse.de/tests/8414267</a><br>
<a href="https://openqa.suse.de/tests/8414271" class="external">https://openqa.suse.de/tests/8414271</a><br>
<a href="https://openqa.suse.de/tests/8414266" class="external">https://openqa.suse.de/tests/8414266</a><br>
<a href="https://openqa.suse.de/tests/8414270" class="external">https://openqa.suse.de/tests/8414270</a><br>
<a href="https://openqa.suse.de/tests/8414265" class="external">https://openqa.suse.de/tests/8414265</a><br>
<a href="https://openqa.suse.de/tests/8414269" class="external">https://openqa.suse.de/tests/8414269</a><br>
<a href="https://openqa.suse.de/tests/8414264" class="external">https://openqa.suse.de/tests/8414264</a></p>
<p><a href="https://openqa.suse.de/tests/8414323" class="external">https://openqa.suse.de/tests/8414323</a><br>
<a href="https://openqa.suse.de/tests/8414322" class="external">https://openqa.suse.de/tests/8414322</a><br>
<a href="https://openqa.suse.de/tests/8414321" class="external">https://openqa.suse.de/tests/8414321</a><br>
<a href="https://openqa.suse.de/tests/8414320" class="external">https://openqa.suse.de/tests/8414320</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/8345312" class="external">113.1</a></p>
<p>Find jobs referencing this ticket with the help of<br>
<a href="https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label" class="external">https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label</a> ,<br>
call <code>openqa-query-for-job-label poo#109046</code></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/8292036" class="external">108.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=Migration-from-SLE12-SPx&machine=s390x-kvm-sle15&test=offline_sles12sp3_ltss_pscc_asmm-lgm_all_full&version=15-SP4" class="external">latest</a></p>
openQA Tests - action #108953 (Resolved): [tools] Performance issues in some s390 workershttps://progress.opensuse.org/issues/1089532022-03-25T07:13:32Zjlausuchjalausuch@suse.com
<p>This ticket is to collect examples of jobs that are failing due to some performance degradation, specially s390x workers.</p>
<p>Installation jobs:<br>
(some of these issues seem to be a slow key press so it doesn't reach the target needle on time):</p>
<ul>
<li><a href="https://openqa.suse.de/tests/8390044#step/select_patterns/5" class="external">https://openqa.suse.de/tests/8390044#step/select_patterns/5</a> - grenache-1:47</li>
<li><a href="https://openqa.suse.de/tests/8387127#step/disable_grub_timeout/18" class="external">https://openqa.suse.de/tests/8387127#step/disable_grub_timeout/18</a> - grenache-1:32</li>
<li><a href="https://openqa.suse.de/tests/8380005#step/add_update_test_repo/38" class="external">https://openqa.suse.de/tests/8380005#step/add_update_test_repo/38</a> - grenache-1:49
<a href="https://openqa.suse.de/tests/8380706#step/add_update_test_repo/10" class="external">https://openqa.suse.de/tests/8380706#step/add_update_test_repo/10</a> - grenache-1:49 </li>
<li><a href="https://openqa.suse.de/tests/8380553#step/cleanup_before_shutdown/4" class="external">https://openqa.suse.de/tests/8380553#step/cleanup_before_shutdown/4</a> (command 'rm -f /etc/udev/rules.d/70-persistent-net.rules' timed out ) - grenache-1:37</li>
</ul>
<p>Other jobs:</p>
<ul>
<li><a href="https://openqa.suse.de/tests/8387144#step/install_updates/14" class="external">https://openqa.suse.de/tests/8387144#step/install_updates/14</a> (command 'rm /tmp/journal_before' timed out) - grenache-1:44</li>
<li><a href="https://openqa.suse.de/tests/8387142#step/image_checks/13" class="external">https://openqa.suse.de/tests/8387142#step/image_checks/13</a> (script timeout: cat /usr/share/combustion-welcome) - grenache-1:33 </li>
</ul>
<p>Boot failures:</p>
<ul>
<li><a href="https://openqa.suse.de/tests/8380156#step/bootloader_zkvm/23" class="external">https://openqa.suse.de/tests/8380156#step/bootloader_zkvm/23</a></li>
<li><a href="https://openqa.suse.de/tests/8380915#step/bootloader_zkvm/22" class="external">https://openqa.suse.de/tests/8380915#step/bootloader_zkvm/22</a></li>
</ul>
openQA Project - action #108824 (Resolved): Some of the daily aggregate tests are cancelled witho...https://progress.opensuse.org/issues/1088242022-03-24T07:02:27Zjlausuchjalausuch@suse.com
<p>Some of the tests that are triggered by the bot-ng are cancelled without any apparent reason and missing logs.</p>
<p>Examples:<br>
<a href="https://openqa.suse.de/tests/8379473" class="external">https://openqa.suse.de/tests/8379473</a><br>
<a href="https://openqa.suse.de/tests/8379476" class="external">https://openqa.suse.de/tests/8379476</a></p>
<p>I have observed this a few times in past days, but I thought it was a sporadic error.<br>
Let's use this ticket to collect these kind of failures.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: It is clear what the expected scheduling behavior is (e.g. is VERSION <em>supposed</em> to be 5.1 in the job despite VERSION 5.0 being specified when scheduling the product)</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Clarify with the author of the test - this test is very new
<ul>
<li>Initial hypothesis: Have these jobs <em>not</em> been scheduled by bot-ng?</li>
<li>Find a way to distinguish bot jobs better</li>
<li>Find out why affected jobs are scheduled with 5.0 but show VERSION 5.1 in the settings</li>
</ul></li>
<li><a href="https://gitlab.suse.de/qac/qac-openqa-yaml/-/blob/master/sle-micro/updates.yaml#L170" class="external">https://gitlab.suse.de/qac/qac-openqa-yaml/-/blob/master/sle-micro/updates.yaml#L170</a>
<ul>
<li>Examine bot-ng logs for scheduling the sle-micro, look for both 5.0 and 5.1 versions (the other one could obsolete the first one)</li>
<li>Product log for 5.0 scheduling: <a href="https://openqa.suse.de/admin/productlog?id=886973" class="external">https://openqa.suse.de/admin/productlog?id=886973</a></li>
<li>Product log for 5.1 scheduling: <a href="https://openqa.suse.de/admin/productlog?id=886978" class="external">https://openqa.suse.de/admin/productlog?id=886978</a></li>
</ul></li>
<li>If the bot cancells jobs as expected, comment "Cancelled because of job #foo" on relevant jobs</li>
</ul>
openQA Project - action #103791 (Resolved): After module failure, the console is broken size:Mhttps://progress.opensuse.org/issues/1037912021-12-09T21:37:15Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>I have observed some situations when a module fails and openQA runs the next one, the very first command fails or times out.<br>
Example:</p>
<p>In <a href="https://openqa.suse.de/tests/7806676#step/cifs/4" class="external">this job</a>, after docker_compose failure, the following modules fail in the beginning.</p>
<p>More occurrences:<br>
<a href="https://openqa.suse.de/tests/7806630#step/libvorbis/4" class="external">https://openqa.suse.de/tests/7806630#step/libvorbis/4</a><br>
<a href="https://openqa.suse.de/tests/7810193#step/verify_default_target/4" class="external">https://openqa.suse.de/tests/7810193#step/verify_default_target/4</a></p>
<p>Related Slack thread: <a href="https://suse.slack.com/archives/C02CANHLANP/p1639048127294800" class="external">https://suse.slack.com/archives/C02CANHLANP/p1639048127294800</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: Better information exists about the state of the system after loading snapshots or in case of failures</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Add a box to the test module that a snapshot was loaded and since the previous module failed it might affect the result e.g. due to I/O or the system clock being askew</li>
<li>After loading snapshots in os-autoinst use QEMU monitoring commands to find out whether the system is just busy/slow, see <a href="https://qemu-project.gitlab.io/qemu/system/monitor.html" class="external">https://qemu-project.gitlab.io/qemu/system/monitor.html</a> , e.g. "info status" and check if the system is just very busy or responsive. Other commands okurz recommends "info migrate" as we just load a snapshot before, maybe it's not completely finished? Maybe "info dirty_rate" shows if stuff needs to be handled before the system is properly responsive again?</li>
<li>The output of those commands could be used in simple debug log lines, so nothing more fancy required</li>
<li>Try to reproduce with a synthetic setup, could e.g. be part of the os-autoinst full-stack test</li>
</ul>
openQA Tests - action #64724 (Resolved): [kernel][xfstests] Parted fails to create a partitionhttps://progress.opensuse.org/issues/647242020-03-22T18:31:09Zjlausuchjalausuch@suse.com
<p><a href="https://openqa.suse.de/tests/4017525#step/partition/13" class="external">https://openqa.suse.de/tests/4017525#step/partition/13</a></p>
<pre><code>parted /dev/vdb --script -- mklabel gpt
Error: partition(s) on /dev/vdb are being used.
</code></pre> openQA Tests - action #64547 (Resolved): [kernel][public cloud] Terraform init crashes with SIGSE...https://progress.opensuse.org/issues/645472020-03-17T22:11:47Zjlausuchjalausuch@suse.com
<p>There is a new error in Terraform while running the command terraform init.<br>
Needs investigation: </p>
<p>Examples:<br>
<a href="https://openqa.suse.de/tests/3997753" class="external">https://openqa.suse.de/tests/3997753</a> (EC2)<br>
<a href="https://openqa.suse.de/tests/3997743" class="external">https://openqa.suse.de/tests/3997743</a> (GCE)<br>
and some more in Azure.</p>
<pre><code># terraform init -no-color; echo 2t4Hw-$?-
Initializing the backend...
Initializing provider plugins...
- Checking for available provider plugins...
- Downloading plugin for provider "random" (hashicorp/random) 2.2.1...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x55c999cd8dfc]
</code></pre> openQA Tests - action #62408 (Closed): [kernel][public cloud] Timeout when creating Azure-Standar...https://progress.opensuse.org/issues/624082020-01-21T07:59:24Zjlausuchjalausuch@suse.com
<p>All the Azure-Standard tests are failing with timeout in terraform apply. <br>
<a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP2&build=0.9.3-1.28&groupid=219&flavor=Azure-Standard" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP2&build=0.9.3-1.28&groupid=219&flavor=Azure-Standard</a></p>
<p>I did some tests increasing that timeout to 1 hour and I get this message:</p>
<pre><code>azurerm_virtual_machine.openqa-vm[0]: Still creating... [40m10s elapsed]
azurerm_virtual_machine.openqa-vm[0]: Still creating... [40m20s elapsed]
azurerm_virtual_machine.openqa-vm[0]: Still creating... [40m30s elapsed]
azurerm_virtual_machine.openqa-vm[0]: Still creating... [40m40s elapsed]
azurerm_virtual_machine.openqa-vm[0]: Still creating... [40m50s elapsed]
azurerm_virtual_machine.openqa-vm[0]: Still creating... [41m0s elapsed]
Error: Code="OSProvisioningTimedOut" Message="OS Provisioning for VM 'jlausuch-vm-b453e006c72d7fae' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\r\n * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/ \r\n * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/ "
on plan.tf line 129, in resource "azurerm_virtual_machine" "openqa-vm":
129: resource "azurerm_virtual_machine" "openqa-vm" {
</code></pre> openQA Tests - action #58664 (Resolved): [kernel][wicked] Needs to improve handling of situation ...https://progress.opensuse.org/issues/586642019-10-24T13:56:53Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>tcpdump commands fails</p>
<pre><code># ## START: t01_gre_tunnel_legacy
# tcpdump -s0 -U -w /tmp/tcpdumpt01_gre_tunnel_legacy.pcap >& /dev/null & export CHECK_TCPDUMP_PID=$!; echo ZUt9d-$?-
[1] 4252
ZUt9d-0-
[1]+ Exit 127 tcpdump -s0 -U -w /tmp/tcpdumpt01_gre_tunnel_legacy.pcap &> /dev/null
</code></pre>
<p><a href="https://openqa.suse.de/tests/3518286#step/t01_gre_tunnel_legacy/89" class="external">https://openqa.suse.de/tests/3518286#step/t01_gre_tunnel_legacy/89</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: <a href="mailto:asmorodskyi@suse.de">asmorodskyi@suse.de</a> <a href="mailto:jalausuch@suse.com">jalausuch@suse.com</a> <a href="mailto:cfamullaconrad@suse.de">cfamullaconrad@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.opensuse.org/tests/1063727" class="external">20191022</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: None in QAM jobs, but it works on QA jobs. <br>
Example of expected result: <a href="https://openqa.suse.de/tests/3507684" class="external">https://openqa.suse.de/tests/3507684</a></p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
openQA Tests - action #58268 (Resolved): [kernel][public cloud] Fix OpenQA view with different ve...https://progress.opensuse.org/issues/582682019-10-16T11:57:33Zjlausuchjalausuch@suse.com
<p>Currently, we are grouping Public Cloud tests depending on the Cloud Build and the Kiwi Build, which are most of the same different for different providers. This makes the grouping of the tests cases a bit tricky, always depending on those build numbers. This has some drawbacks (e.g. searching specific tests, JDP, ...) and makes the view very complex.</p>
<p>The idea is to come up with a solution to group the tests in a smarter way. From the ISOS POST, we could change the BUILD variable we pass to OpenQA.</p>
<p>2 ways:</p>
<p>1) Use same BUILD number as the corresponding SLES build to the PC images<br>
Advantage: everything is in the same place, we can even merge the group with SLE1X job groups</p>
<p>It would look something like this:</p>
<pre><code>Build0358 (a day ago)
Build0357 (4 days ago)
Build0350 (8 days ago)
Build0346 (8 days ago)
</code></pre>
<p>2) Group them by SLES build number and also by Provider name:<br>
Advantage: easy to find tests for specific provider<br>
Disadvantage: we can't merge it in the SLE1X groups, we would need to keep it in Public Cloud group.</p>
<p>IT would look something like this:</p>
<pre><code>Build0358-Azure (a day ago)
Build0358-EC2 (a day ago)
Build0358-GCE (a day ago)
Build0357-Azure (a day ago)
Build0357-EC2 (a day ago)
Build0357-GCE (a day ago)
...
</code></pre> openQA Tests - action #58220 (Resolved): [kernel] fadump LVM test failshttps://progress.opensuse.org/issues/582202019-10-15T20:25:44Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Failure when going into grub screen<br>
<a href="https://openqa.suse.de/tests/3479900#step/kdump_and_crash/64" class="external">grub screen</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: Petr Cervinka <a href="mailto:pcervinka@suse.com">pcervinka@suse.com</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/3479900" class="external">0358</a><br>
But it also failed in some <a href="https://openqa.suse.de/tests/3395111" class="external">older run</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>This is an example of <a href="https://openqa.suse.de/tests/3470330#step/kdump_and_crash/64" class="external">successful run</a> in the previous build.</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>