Project

General

Profile

Actions
Copy link

action #153151

open

test fails in bci_test_podman

Added by etchubykalo over 1 year ago. Updated 6 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2024-01-05
Due date:
% Done:

0%

Estimated time:
Tags:
containers

Description

Observation

openQA test in scenario sle-15-SP5-BCI-Updates-aarch64-bci-sle15-kernel-module-devel_15.5_on_SLES_15-SP5_podman@aarch64-virtio fails in
bci_test_podman

Observed in multiple BCI kernel-module-devel-image on all SP1 to SP5, for aarch64, ppc64le and s390x

Error: building at STEP "RUN set -euxo pipefail; curl -Lsf -o - https://fast.dpdk.org/rel/dpdk-23.07.tar.gz | tar xzf - ; cd dpdk-23.07; meson --prefix=/usr --includedir=/usr/include/ -Ddefault_library=shared -Denable_docs=false -Db_lto=false -Dplatform="$(uname -m)" -Dcpu_instruction_set=generic -Denable_kmods=true -Dkernel_dir="/usr/src/linux-obj/$(uname -m)/default" build; meson compile -C build": while running runtime: exit status 1

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 2.25_sle15-kernel-module-devel-image

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by ph03nix over 1 year ago

  • Status changed from New to Rejected
Actions
Copy link
 #2

Updated by ph03nix 6 months ago

  • Tags set to containers
Actions
Copy link
 #3

Updated by asmorodskyi 28 days ago

  • Status changed from Rejected to New

reopening because looks like it happens again , and if you check runs history it is sporadic so please don't close if it will passes once https://openqa.suse.de/tests/17091640#step/_root_BCI-tests_kernel_/1

Actions
Copy link
 #5

Updated by mdati 6 days ago ยท Edited

To help making more clear the context, consider we here that the basic issue described in the ticket header, occurred >1 year ago, was dealing with the dockerfile build phase, in particular a STEP 2 where much probably problematic were either curl -Lsf -o - https://fast.dpdk.org/rel/dpdk-23.07.tar.gz(unresponsive url?) or meson(missing?).

Instead, the faults named in the next notes 3 and 4, happened, after 1 year, in a next phase,test execution (after the build occurred), failed on git clone: 

E               subprocess.CalledProcessError: Command '['git', 'clone', '--depth', '1', '--branch', 'main', 'https://dpdk.org/git/dpdk-kmods']' returned non-zero exit status 128.

/usr/lib64/python3.11/subprocess.py:571: CalledProcessError

Still the same dpdk url involved, here https://dpdk.org/git/dpdk-kmods and probably unresponsive, but after few retries the test passed ok.

The issue seems very sporadic and unpredictable (difficult to reproduce) and from that build 15days ago, it didn't occurr anymore till now.

Actions
Copy link

Also available in: Atom PDF