openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-21T09:51:42ZopenSUSE Project Management Tool
Redmine openQA Tests - action #157657 (Feedback): PackageHub module activation while using SCC-proxyhttps://progress.opensuse.org/issues/1576572024-03-21T09:51:42Zjlausuchjalausuch@suse.com
<a name="Problem-statement"></a>
<h2 >Problem statement:<a href="#Problem-statement" class="wiki-anchor">¶</a></h2>
<p>When registering the system using ProxySCC, activating the PackageHub module returns repos in OSD that don't exist.<br>
This is expected, because the proxySCC replaces the repo URLs given by the real SCC by local openQA asset URL.</p>
<p>Normally, we use the proxySCC in the openQA jobs with <code>SCC_URL</code> variable, this will be used by the code to make the <code>SUSEConnect</code> call like this:</p>
<p><code>SUSEConnect -r $REGCODE --url http://all-67.1.proxy.scc.suse.de</code></p>
<p>This will make that all the repos returned look like this:<br>
<code>http://openqa.suse.de/assets/repo/...</code></p>
<p>And enabling any module, will have the same effect, for example PackageHub:</p>
<pre><code>
susetest:~ # suseconnect -p PackageHub/15.6/x86_64
Registering system to registration proxy http://all-67.1.proxy.scc.suse.de
Updating system details on http://all-67.1.proxy.scc.suse.de ...
Activating PackageHub 15.6 x86_64 ...
-> Adding service to system ...
-> Installing release package ...
Successfully registered system
</code></pre>
<p>And the repo will point to the wrong place:</p>
<pre><code>18 | SUSE_Package_Hub_15_SP6_x86_64:SLE-Module-Packagehub-Subpackages15-SP6-Pool | SLE-Module-Packagehub-Subpackages15-SP6-Pool | Yes | (r ) Yes | No | http://openqa.suse.de/assets/repo/SLE-15-SP6-Module-Packagehub-Subpackages-POOL-x86_64-Build67.1-Media1/
</code></pre>
<a name="Solution"></a>
<h2 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h2>
<p>To cope with this, we would need to sync the PackageHub module for EVERY build we have for 15-SP6. Another solution would be to tweak ProxySCC code to return the real URL instead of local assets.</p>
<p>BUT there is an easier way:<br>
1) Register the system using the usual proxySCC</p>
<pre><code>susetest:~ # SUSEConnect -r $REGCODE --url http://all-67.1.proxy.scc.suse.de
Registering system to registration proxy http://all-67.1.proxy.scc.suse.de
Announcing system to http://all-67.1.proxy.scc.suse.de ...
Activating SLES 15.6 x86_64 ...
-> Adding service to system ...
Activating sle-module-basesystem 15.6 x86_64 ...
-> Adding service to system ...
-> Installing release package ...
Activating sle-module-server-applications 15.6 x86_64 ...
-> Adding service to system ...
-> Installing release package ...
Activating sle-module-python3 15.6 x86_64 ...
-> Adding service to system ...
-> Installing release package ...
Successfully registered system
</code></pre>
<p>2) Activate the desired module using <code>--url</code> pointing to real SCC:</p>
<pre><code>susetest:~ # SUSEConnect -p PackageHub/15.6/x86_64 --url https://scc.suse.com
Registering system to SUSE Customer Center
Updating system details on https://scc.suse.com ...
Activating PackageHub 15.6 x86_64 ...
-> Adding service to system ...
-> Installing release package ...
Successfully registered system
</code></pre>
<p>3) And voilá, you will get the repos from REAL SCC:</p>
<pre><code>susetest:~ # zypper lr -u |grep -i PackageHub-15-SP6-Pool
22 | SUSE_Package_Hub_15_SP6_x86_64:SUSE-PackageHub-15-SP6-Pool | SUSE-PackageHub-15-SP6-Pool | Yes | (r ) Yes | No | https://updates.suse.com/SUSE/Backports/SLE-15-SP6_x86_64/product?RMMzfgZAuv8Hy903n30FsW6hbWs5KExVGGIwF1w5nRMdkliFvRBscHmgomWpHwFbG8l2C7cmrcZead-ejTo_f0NKbts7ZNwGBw0WtMwuWeKXxK2mgknqmbcYZ22y3RB3rThU1AMZTw
</code></pre> 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>
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 - 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 #112895 (Closed): [stale] SelfInstall ALP Images fail in image_checkshttps://progress.opensuse.org/issues/1128952022-06-22T18:07:31Zjlausuchjalausuch@suse.com
<p><a href="https://openqa.opensuse.org/tests/2430307#step/image_checks/8" class="external">https://openqa.opensuse.org/tests/2430307#step/image_checks/8</a><br>
<a href="https://openqa.opensuse.org/tests/2430327#step/image_checks/9" class="external">https://openqa.opensuse.org/tests/2430327#step/image_checks/9</a></p>
<p>It fails in the step: <br>
<code>validate_script_output("sfdisk --list-free /dev/$disk", qr/Unpartitioned space .* 0 sectors/);</code><br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/microos/image_checks.pm#L26" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/microos/image_checks.pm#L26</a></p>
<pre><code>Unpartitioned space /dev/vda: 27.85 GiB, 29906419200 bytes, 58410975 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Start End Sectors Size
</code></pre>
<p>Expected output:<br>
<a href="https://openqa.opensuse.org/tests/2426647#step/image_checks/6" class="external">https://openqa.opensuse.org/tests/2426647#step/image_checks/6</a></p>
<pre><code>Unpartitioned space /dev/vda: 0 B, 0 bytes, 0 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
</code></pre> ALP - action #112829 (Closed): [stale] ALP uefi jobs fail in disk_boot https://progress.opensuse.org/issues/1128292022-06-21T21:32:51Zjlausuchjalausuch@suse.com
<p>UEFI jobs are not booting properly:<br>
<a href="https://openqa.opensuse.org/tests/2426185" class="external">https://openqa.opensuse.org/tests/2426185</a></p>
<p>Expected result (Leap Micro):<br>
<a href="https://openqa.opensuse.org/tests/2426642#step/disk_boot/1" class="external">https://openqa.opensuse.org/tests/2426642#step/disk_boot/1</a></p>
ALP - coordination #112409 (Resolved): [epic] PoC for openSUSE ALP testing in openQA https://progress.opensuse.org/issues/1124092022-06-14T15:51:37Zjlausuchjalausuch@suse.com
<p>This epic is a coordination effort for a first Proof of Concept enabling ALP testing in openqa.opensuse.org.</p>
<p>The goal is to re-use the existing tests we are running for MicroOS plus some adaptations and execute them against images.</p>
<p>The images that this PoC shall cover are:</p>
<ul>
<li>kvm-and-xen</li>
<li>kvm-and-xen_NonTransactional</li>
<li>SelfInstall</li>
<li>SelfInstall_NonTransactional</li>
</ul>
<p>Current available architecture is x86_64, but aarch64 might be available for the PoC as well.</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>
qe-yam - action #107959 (Closed): 12-SP5-Server-DVD-Updates-s390x installation job fails too oftenhttps://progress.opensuse.org/issues/1079592022-03-08T08:16:49Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP5-Server-DVD-Updates-s390x-mru-install-minimal-with-addons@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/8286121/modules/await_install/steps/2" class="external">await_install</a></p>
<p>This job is a parent job which many child jobs depend on and are blocked if this fails,<br>
which delays the maintenance review some hours.</p>
<p>It fails 40-50% of the times with <strong>timeout_exceeded</strong> or <strong>incomplete</strong>.</p>
<p>Examples:<br>
<a href="https://openqa.suse.de/tests/8280085" class="external">https://openqa.suse.de/tests/8280085</a><br>
<a href="https://openqa.suse.de/tests/8277975" class="external">https://openqa.suse.de/tests/8277975</a><br>
<a href="https://openqa.suse.de/tests/8277320" class="external">https://openqa.suse.de/tests/8277320</a><br>
<a href="https://openqa.suse.de/tests/8261669" class="external">https://openqa.suse.de/tests/8261669</a><br>
<a href="https://openqa.suse.de/tests/8247241" class="external">https://openqa.suse.de/tests/8247241</a><br>
<a href="https://openqa.suse.de/tests/8239743" class="external">https://openqa.suse.de/tests/8239743</a><br>
<a href="https://openqa.suse.de/tests/8227540" class="external">https://openqa.suse.de/tests/8227540</a><br>
<a href="https://openqa.suse.de/tests/8226549" class="external">https://openqa.suse.de/tests/8226549</a><br>
<a href="https://openqa.suse.de/tests/8194333" class="external">https://openqa.suse.de/tests/8194333</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Testsuite maintained at <a href="https://gitlab.suse.de/qa-maintenance/qam-openqa-yml" class="external">https://gitlab.suse.de/qa-maintenance/qam-openqa-yml</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/8286121" class="external">20220308-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/8281074" class="external">20220307-1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Server-DVD-Updates&machine=s390x-kvm-sle12&test=mru-install-minimal-with-addons&version=12-SP5" 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>
openQA Tests - action #64710 (Resolved): [qac][public cloud] Failed to get credentials form Vault...https://progress.opensuse.org/issues/647102020-03-21T17:38:19Zjlausuchjalausuch@suse.com
<p>All the tests in Azure-HPC-BYOS fail to talk to Vault server. For other flavors it works: I have re-run tests at the same time in one flavor and the others and it always fails in Azure-HPC-BYOS flavor.</p>
<p><a href="https://openqa.suse.de/tests/4020950#step/run_ltp/32" class="external">https://openqa.suse.de/tests/4020950#step/run_ltp/32</a></p>
<p>Not sure what is happening in the background, but looks like when vault_get_secrets is called, it calls vault_api and fails the 3 times it calls __vault_api.</p>
<p>We should increase the debug messages here, cause it's difficult to debug with only these calls:</p>
<pre><code>[2020-03-21T18:26:42.592 CET] [debug] tests/publiccloud/run_ltp.pm:59 called publiccloud::basetest::provider_factory -> lib/publiccloud/basetest.pm:65 called publiccloud::azure::init -> lib/publiccloud/azure.pm:44 called publiccloud::azure::vault_create_credentials -> lib/publiccloud/azure.pm:64 called testapi::record_info
[2020-03-21T18:26:42.592 CET] [debug] <<< testapi::record_info(title="INFO", output="Get credentials from VAULT server.", result="ok")
[2020-03-21T18:27:12.732 CET] [debug] Maximum number of Vault request retries exceeded. Check Vault Server is up and running at /var/lib/openqa/cache/openqa.suse.de/tests/sle/lib/publiccloud/provider.pm line 549.
[2020-03-21T18:27:12.735 CET] [debug] lib/publiccloud/basetest.pm:94 called publiccloud::basetest::_cleanup -> lib/publiccloud/basetest.pm:80 called (eval) -> lib/publiccloud/basetest.pm:80 called run_ltp::cleanup -> tests/publiccloud/run_ltp.pm:103 called testapi::type_string
</code></pre> openQA Tests - action #64707 (Resolved): [qac][public cloud][ltp] epoll_wait02 test from LTP sysc...https://progress.opensuse.org/issues/647072020-03-20T22:10:27Zjlausuchjalausuch@suse.com
<p><a href="https://openqa.suse.de/tests/4019168#step/epoll_wait02/1">https://openqa.suse.de/tests/4019168#step/epoll_wait02/1</a></p>
<p>However, on other images it passes, e.g. <a href="https://openqa.suse.de/tests/4017274#step/epoll_wait02/1">https://openqa.suse.de/tests/4017274#step/epoll_wait02/1</a></p>
<p>This is the output form the test execution:</p>
<pre><code>sh-4.4# epoll_wait02; echo cmd-exit-129-$?
tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s
tst_timer_test.c:348: INFO: CLOCK_MONOTONIC resolution 1ns
tst_timer_test.c:360: INFO: prctl(PR_GET_TIMERSLACK) = 50us
tst_timer_test.c:264: INFO: epoll_wait() sleeping for 1000us 500 iterations, threshold 450.01us
tst_timer_test.c:307: INFO: min 1068us, max 1167us, median 1073us, trunc mean 1074.28us (discarded 25)
tst_timer_test.c:322: PASS: Measured times are within thresholds
tst_timer_test.c:264: INFO: epoll_wait() sleeping for 2000us 500 iterations, threshold 450.01us
tst_timer_test.c:307: INFO: min 2071us, max 2174us, median 2077us, trunc mean 2078.58us (discarded 25)
tst_timer_test.c:322: PASS: Measured times are within thresholds
tst_timer_test.c:264: INFO: epoll_wait() sleeping for 5000us 300 iterations, threshold 450.04us
tst_timer_test.c:307: INFO: min 5075us, max 5209us, median 5084us, trunc mean 5087.58us (discarded 15)
tst_timer_test.c:322: PASS: Measured times are within thresholds
tst_timer_test.c:264: INFO: epoll_wait() sleeping for 10000us 100 iterations, threshold 450.33us
tst_timer_test.c:307: INFO: min 10080us, max 10167us, median 10091us, trunc mean 10092.68us (discarded 5)
tst_timer_test.c:322: PASS: Measured times are within thresholds
tst_timer_test.c:264: INFO: epoll_wait() sleeping for 25000us 50 iterations, threshold 451.29us
tst_timer_test.c:307: INFO: min 25085us, max 25187us, median 25106us, trunc mean 25107.94us (discarded 2)
tst_timer_test.c:322: PASS: Measured times are within thresholds
tst_timer_test.c:264: INFO: epoll_wait() sleeping for 100000us 10 iterations, threshold 537.00us
tst_timer_test.c:307: INFO: min 100154us, max 104057us, median 100165us, trunc mean 100616.56us (discarded 1)
tst_timer_test.c:310: FAIL: epoll_wait() slept for too long
Time: us | Frequency
--------------------------------------------------------------------------------
100154 | ********************************************************************
100360 | *********+
100566 |
100772 |
100978 |
101184 |
101390 |
101596 |
101802 |
102008 |
102214 |
102420 |
102626 |
102832 |
103038 |
103244 |
103450 |
103656 |
103862 | *******************-
--------------------------------------------------------------------------------
206us | 1 sample = 9.71429 '*', 19.42857 '+', 38.85714 '-', non-zero '.'
tst_timer_test.c:264: INFO: epoll_wait() sleeping for 1000000us 2 iterations, threshold 4400.00us
tst_timer_test.c:307: INFO: min 1037244us, max 1039297us, median 1037244us, trunc mean 1037244.00us (discarded 1)
tst_timer_test.c:310: FAIL: epoll_wait() slept for too long
Time: us | Frequency
--------------------------------------------------------------------------------
1037244 | ********************************************************************
1037353 |
1037462 |
1037571 |
1037680 |
1037789 |
1037898 |
1038007 |
1038116 |
1038225 |
1038334 |
1038443 |
1038552 |
1038661 |
1038770 |
1038879 |
1038988 |
1039097 |
1039206 | ********************************************************************
--------------------------------------------------------------------------------
109us | 1 sample = 68.00000 '*', 136.00000 '+', 272.00000 '-', non-zero '.'
Summary:
passed 5
failed 2
skipped 0
warnings 0
</code></pre>