openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-09-22T06:11:38ZopenSUSE Project Management Tool
Redmine openQA Tests - action #136298 (Resolved): Leap Micro test fails in transactional_updatehttps://progress.opensuse.org/issues/1362982023-09-22T06:11:38Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario leap-micro-5.5-MicroOS-Image-x86_64-microos_image_default@64bit fails in<br>
<a href="https://openqa.opensuse.org/tests/3591732/modules/transactional_update/steps/96" class="external">transactional_update</a></p>
<p>As the job says, there should be an expected change when <a href="https://openqa.opensuse.org/tests/3591732#step/transactional_update/23" class="external">installing the local rpm</a><br>
<code>transactional-update -n ptf install update-test-trivial/update-test-security-5.1-1.20.x86_64.rpm</code><br>
and <a href="https://openqa.opensuse.org/tests/3591732#step/transactional_update/73" class="external">adding the utt repo</a> along with <code>transactional-update -n cleanup up</code>. </p>
<p>The local package is <code>/data/microos/utt-opensuse-x86_64.tgz</code> and the repo is <code>/data/microos/utt-leap.repo</code>, both in the data directory:<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/data/microos" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/data/microos</a></p>
<p>This was working on Leap Micro 5.4 (no existing jobs), so for some reason now the packages seem to be the same or the local rpm is already a higher version than the one in the repo, and zypper says <code>zypper: nothing to update</code>.</p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>MicroOS image boot with ignition disk and default tests. Default tests are transactional-update, rebootmgr, health_check, cockpit service and some other checks specific to MicroOS.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since the beginning.</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>
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 #111010 (Resolved): type_password does not hide the string in autoinst-log.txthttps://progress.opensuse.org/issues/1110102022-05-12T11:30:11Zjlausuchjalausuch@suse.com
<p>I am doing some tests using <code>type_password</code> command to put some sensitive information into a file in a running system.<br>
According to the documentation [1]: <code>A convenience wrapper around type_string, which doesn’t log the string.</code></p>
<p>However, if I do:<br>
<code>type_password("echo 'yada yada' > /root/influxdb_conf\n");</code></p>
<p>This info is shown in autoinst-log.txt:</p>
<pre><code>[2022-05-12T13:05:09.897059+02:00] [debug] tests/jeos/image_info.pm:130 called testapi::type_password
[2022-05-12T13:05:09.897329+02:00] [debug] <<< testapi::type_string(string="echo 'yada yada' > /root/influxdb_conf\n", max_interval=100, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
</code></pre>
<p>This is using root-console. If I use serial_terminal, I get it in the <code>serial_terminal.txt</code> log:</p>
<pre><code>...
SCRIPT_FINISHEDGItcm-0-
# echo 'yada yada' > /root/influxdb_conf
</code></pre>
<p>Also, openQA tests are showing this </p>
<p>2 months ago (before <a href="https://github.com/os-autoinst/os-autoinst/pull/2002" class="external">https://github.com/os-autoinst/os-autoinst/pull/2002</a>)<br>
<a href="https://openqa.suse.de/tests/8405529/logfile?filename=autoinst-log.txt" class="external">https://openqa.suse.de/tests/8405529/logfile?filename=autoinst-log.txt</a></p>
<pre><code>[2022-03-26T12:33:40.095557+01:00] [debug] tests/jeos/firstrun.pm:116 called testapi::type_password
[2022-03-26T12:33:40.095850+01:00] [debug] <<< testapi::type_string(string="SECRET STRING", max_interval=100, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
</code></pre>
<p>Now:<br>
<a href="https://openqa.suse.de/tests/8738443/logfile?filename=autoinst-log.txt" class="external">https://openqa.suse.de/tests/8738443/logfile?filename=autoinst-log.txt</a></p>
<pre><code>[2022-05-12T06:09:58.666172+02:00] [debug] tests/jeos/firstrun.pm:116 called testapi::type_password
[2022-05-12T06:09:58.666561+02:00] [debug] <<< testapi::type_string(string="nots3cr3t", max_interval=100, wait_screen_changes=0, wait_still_screen=0, timeout=30, similarity_level=47)
</code></pre>
<p>[1] <a href="http://open.qa/api/testapi/#_type_password" class="external">http://open.qa/api/testapi/#_type_password</a></p>
openQA Tests - action #109882 (Resolved): Leap Micro 5.2 autoyast installation misses the repo-ma...https://progress.opensuse.org/issues/1098822022-04-12T22:14:27Zjlausuchjalausuch@suse.com
<p>After doing an <a href="https://openqa.opensuse.org/tests/2293631" class="external">autoyast installation</a>, the system doesn't have the repository </p>
<pre><code>install:~ # zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | URI
--+---------------------------+---------------------------+---------+-----------+---------+--------------------------------------------------------
1 | openSUSE-Leap-Micro-5.2-1 | openSUSE-Leap-Micro-5.2-1 | No | ---- | ---- | cd:/?devices=/dev/disk/by-id/scsi-0QEMU_QEMU_CD-ROM_cd0
</code></pre>
<p>And because of this, the installation of some packages fail (e.g. <a href="https://openqa.opensuse.org/tests/2293631#step/cockpit_service/8" class="external">cockpit</a>)</p>
<p>This is how it should look like from the regular <a href="https://openqa.opensuse.org/tests/2294237" class="external">DVD installation</a>:</p>
<pre><code>localhost:~ # zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | URI
--+---------------------------+----------------------------+---------+-----------+---------+----------------------------------------------------------------------------------------------------
1 | openSUSE-Leap-Micro-5.2-1 | openSUSE-Leap-Micro-5.2-1 | No | ---- | ---- | cd:/?devices=/dev/disk/by-id/scsi-0QEMU_QEMU_CD-ROM_cd0
2 | repo-main | Leap Micro Main Repository | Yes | (r ) Yes | Yes | https://download.opensuse.org/distribution/leap-micro/5.2/product/repo/Leap-Micro-5.2-x86_64-Media/
</code></pre>
<p>The used autoyast profile is <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/autoyast_opensuse/autoyast_leap-micro.xml.ep" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/autoyast_opensuse/autoyast_leap-micro.xml.ep</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 #107623 (Resolved): Investigate which update causes rootless_podman regress...https://progress.opensuse.org/issues/1076232022-02-25T08:13:10Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Since 24 Feb, one of the updates in <code>BASE_TEST_ISSUES</code> is causing a regression in rootless podman.<br>
<img src="https://progress.opensuse.org/attachments/download/12904/rootless%20podman.png" alt="" loading="lazy" /></p>
<p>It only happens in 15-SP3 Update jobs. <br>
<code>BASE_TEST_ISSUES=21897,22201,22540,22559,22637,22670,22688,22700,22721,22726,22748,22752,22756,22834,22837,22848,22857,22863,22881,22884,22909,22914,22921,22926,22933,22948,22951,22955,22961,22965,22970,22971,22973,22977,22990</code></p>
<p>podman version: 2.1.1</p>
<p>I have started doing some small investigation and neither <a href="https://smelt.suse.de/incident/22201/" class="external">https://smelt.suse.de/incident/22201/</a> or <a href="https://smelt.suse.de/incident/22843/" class="external">https://smelt.suse.de/incident/22843/</a> (buildah update) cause the issue.</p>
<p>openQA test in scenario sle-15-SP3-JeOS-for-kvm-and-xen-Updates-x86_64-jeos-containers@64bit-virtio-vga fails in<br>
<a href="https://openqa.suse.de/tests/8225835/modules/rootless_podman/steps/102" class="external">rootless_podman</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<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/8219750" class="external">20220224-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/8214690" class="external">20220223-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=64bit-virtio-vga&test=jeos-containers&version=15-SP3" 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 #93339 (Resolved): test fails in validate_btrfshttps://progress.opensuse.org/issues/933392021-06-01T09:16:42Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Server-DVD-Updates-x86_64-sle_image_on_sle_host@64bit fails in<br>
<a href="https://openqa.suse.de/tests/6149331/modules/validate_btrfs/steps/39" class="external">validate_btrfs</a><br>
Other failures:<br>
All Container jobs, e.g. <a href="https://openqa.suse.de/tests/6151606" class="external">https://openqa.suse.de/tests/6151606</a><br>
All Public Cloud jobs, e.g. <a href="https://openqa.suse.de/tests/6149926#step/validate_btrfs/39" class="external">https://openqa.suse.de/tests/6149926#step/validate_btrfs/39</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/6149331" class="external">20210601-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: (unknown) (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=sle_image_on_sle_host&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #89287 (Resolved): test fails in yast2_lanhttps://progress.opensuse.org/issues/892872021-03-01T14:48:17Zjlausuchjalausuch@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-JeOS-for-MS-HyperV-x86_64-jeos-main@svirt-hyperv fails in<br>
<a href="https://openqa.suse.de/tests/5552124/modules/yast2_lan/steps/21" class="external">yast2_lan</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<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/5462492" class="external">23.32</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: (unknown) (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=JeOS-for-MS-HyperV&machine=svirt-hyperv&test=jeos-main&version=15-SP3" class="external">latest</a></p>
openQA Tests - action #66949 (Resolved): [qac][wicked] New test: wicked ifreload all fails to det...https://progress.opensuse.org/issues/669492020-05-18T06:42:57Zjlausuchjalausuch@suse.com
<p>Provide a new test covering bridges and basic wicked function <code>ifreload all</code>.</p>
<p>Basically, we should create a test to cover this bug: <br>
<a href="https://gitlab.suse.de/wicked-maintainers/wicked/-/issues/156" class="external">https://gitlab.suse.de/wicked-maintainers/wicked/-/issues/156</a><br>
<a href="http://bugzilla.suse.com/show_bug.cgi?id=1168155" class="external">http://bugzilla.suse.com/show_bug.cgi?id=1168155</a></p>
openQA Tests - action #65121 (Resolved): [qac][public cloud][ltp] ioctl08 test from LTP syscalls ...https://progress.opensuse.org/issues/651212020-04-01T08:06:25Zjlausuchjalausuch@suse.com
<p>Some failed jobs: <br>
<a href="https://openqa.suse.de/tests/4070442" class="external">https://openqa.suse.de/tests/4070442</a><br>
<a href="https://openqa.suse.de/tests/4070449" class="external">https://openqa.suse.de/tests/4070449</a></p>
<pre><code>Summary:
passed 1
failed 0
skipped 0
warnings 0
cmd-exit-406-0
sh-4.4# ioctl08; echo cmd-exit-407-$?
tst_device.c:88: INFO: Found free device 0 '/dev/loop0'
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with btrfs opts='' extra opts=''
cmd-exit-407-255
sh-4.4# printf tainted-; cat /proc/sys/kernel/tainted; echo cmd-exit-408-$?
tainted-0
cmd-exit-408-0
sh-4.4# ioctl_ns01; echo cmd-exit-409-$?
tst_test.c:1241: INFO: Timeout per run is 0h 05m 00s
ioctl_ns01.c:57: PASS: NS_GET_PARENT fails with EPERM
ioctl_ns01.c:57: PASS: NS_GET_PARENT fails with EPERM
</code></pre> openQA Tests - action #65115 (Resolved): [qac][public cloud] Storage perf test failing in ssh con...https://progress.opensuse.org/issues/651152020-04-01T06:24:17Zjlausuchjalausuch@suse.com
<p>PC tools helper VM fails to connect to the VM</p>
<p><a href="https://openqa.suse.de/tests/4070444#" class="external">https://openqa.suse.de/tests/4070444#</a><br>
<a href="https://openqa.suse.de/tests/4067508#" class="external">https://openqa.suse.de/tests/4067508#</a></p>
<pre><code># nc -vz -w 1 34.76.215.65 22; echo Hsf3L-$?-
Connection to 34.76.215.65 22 port [tcp/ssh] succeeded!
Hsf3L-0-
# cat > /tmp/scripthW6mh.sh << 'EOT_hW6mh'; echo hW6mh-$?-
> ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=ERROR -i '/root/.ssh/id_rsa' "susetest@34.76.215.65" -- 'uname -r'
> EOT_hW6mh
hW6mh-0-
# echo hW6mh; bash -oe pipefail /tmp/scripthW6mh.sh ; echo SCRIPT_FINISHEDhW6mh-$?-
hW6mh
susetest@34.76.215.65: Permission denied (publickey).
</code></pre> openQA Tests - action #64797 (Resolved): [kernel][public cloud] EC2 command fails to upload imageshttps://progress.opensuse.org/issues/647972020-03-25T07:43:38Zjlausuchjalausuch@suse.com
<p>There is a new issue happening in latest build corresponding to SLES build 163.11.</p>
<p><a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP2&build=0011&groupid=274" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP2&build=0011&groupid=274</a></p>
<pre><code># ec2uploadimg --access-id 'AKIAYWW2BWC7ZK6D6TDV' -s 'LhgJISWo2A9drw67gvybqU3whwAFViXyeos3ihq6' --backing-store ssd --grub2 --machine 'x86_64' -n 'openqa-SLES15-SP2-CHOST-BYOS.x86_64-0.9.5-EC2-Build1.3.raw.xz' --virt-type hvm --sriov-support --ena-support --verbose --regions 'eu-central-1' --ssh-key-pair 'openqa1585121012_0' --private-key-file QA_SSH_KEY.pem -d 'OpenQA tests' 'SLES15-SP2-CHOST-BYOS.x86_64-0.9.5-EC2-Build1.3.raw.xz'; echo i5Gu5-$?-
Successfully created VPC with id vpc-0c8dfe70b8a7b2ffe
Successfully created internet gateway igw-07ae0d90e57169a80
Successfully created route table rtb-0b44872ab7935b9d3
Successfully created VPC subnet with id subnet-0de5c035c815caa93
Creating temporary security group
Temporary Security Group Created sg-0b495d816b0c739d1 in vpc vpc-0c8dfe70b8a7b2ffe
Successfully allowed incoming SSH port 22 for security group sg-0b495d816b0c739d1 in vpc-0c8dfe70b8a7b2ffe
Waiting for instance: i-0ae73ed595a9aba4f
. .
Waiting for volume creation: vol-08e5155f3378cefee
.
Wait for volume attachment
.
Waiting to obtain instance IP address
.
Attempt ssh connection to 18.194.37.145
. . . /root/.venv_ec2uploadimg/lib/python3.6/site-packages/paramiko/client.py:837: UserWarning: Unknown ssh-ed25519 host key for 18.194.37.145: b'fa5f17f0f6a344c0504dde11927b4cf5'
key.get_name(), hostname, hexlify(key.get_fingerprint())
An error occurred (DependencyViolation) when calling the DeleteSecurityGroup operation: resource sg-0b495d816b0c739d1 has a dependent object
</code></pre> 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>