action #134276
closedtest fails in run_container_in_k3s
100%
Description
Observation¶
openQA test in scenario alp-1.0-Dolomite-Default-SelfInstall-x86_64-alp_k3s@64bit fails in
run_container_in_k3s
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 5.6
Expected result¶
Last good: 2.4 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by ph03nix 9 months ago
Cannot reproduce on a bare-metal host using ALP-Dolomite.x86_64-1.0-Default-SelfInstall-Build5.6.install.iso
# k3s-install
# systemctl --no-pager start k3s
# systemctl status k3s
# k3s -v
# k3s kubectl get node
# vim k8s_job_manifest.yaml
# kubectl apply -f k8s_job_manifest.yaml
job.batch/test created
With the k8s_job_manifest.yaml:
apiVersion: batch/v1
kind: Job
metadata:
name: test
spec:
template:
spec:
containers:
- name: nginx
image: registry.suse.com/bci/bci-base:latest
command: [ CMD ]
resources:
limits:
cpu: "0.5"
memory: 256Mi
requests:
cpu: "0.1"
memory: 128Mi
restartPolicy: Never
Updated by ph03nix 9 months ago
openqa-investigate suggests this is a sporadic issue: https://openqa.suse.de/t11815320
Might help to increase the RAM: https://duck-norris.qe.suse.de/tests/13423 (original) and https://duck-norris.qe.suse.de/tests/13424 (2 GiB RAM)
Updated by ph03nix 9 months ago
https://duck-norris.qe.suse.de/tests/13428# suggests that it is indeed a resource issue. Will increase the RAM for the corresponding jobs.