action #160967
opentest fails in slem_rancher
100%
Description
Observation¶
openQA test in scenario sle-micro-5.5-Container-Image-Updates-x86_64-sle_micro_rancher_image@64bit fails in
slem_rancher
Error: can only create exec sessions on running containers: container state improper
Not sure what happens here, this needs to be investigated.
Updated by ph03nix about 1 month ago
The registry.suse.de/suse/sle-15-sp5/update/products/elemental55/update/cr/totest/images/suse/sle-micro-iso/5.5:latest image is 855.6 MiB large.
Updated by ph03nix about 1 month ago
slem55:~ # podman run --name slem_image -dt registry.suse.de/suse/sle-15-sp5/update/products/elemental55/update/cr/totest/images/suse/sle-micro-iso/5.5:latest
Trying to pull registry.suse.de/suse/sle-15-sp5/update/products/elemental55/update/cr/totest/images/suse/sle-micro-iso/5.5:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob fd1a11dfeb8e done |
Copying blob 5a42b736fa37 done |
Copying config 52e8972906 done |
Writing manifest to image destination
Storing signatures
e0661f1fcfc317ef494d3051895e03878520c5a90daeee1f7a974377bb662926
slem55:~ # podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e0661f1fcfc3 registry.suse.de/suse/sle-15-sp5/update/products/elemental55/update/cr/totest/images/suse/sle-micro-iso/5.5:latest sh 15 seconds ago Up 15 seconds slem_image
slem55:~ # podman exec slem_image /bin/sh -c 'ls /boot'
slem55:~ # podman exec slem_image /bin/sh
slem55:~ # podman exec -ti slem_image /bin/sh
# ls /boot
# cd /
# ls
bin dev etc lib mnt proc run selinux sys usr
boot elemental-iso home lib64 opt root sbin srv tmp var
#
slem55:~ #
Cannot reproduce the openQA issue, however /boot is empty, which is unexpected.
Updated by ph03nix about 1 month ago
I do see the following error in https://duck-norris.qe.suse.de/tests/14665 where the container is borked:
# podman logs slem_image
bash: applet not found
Updated by ph03nix about 1 month ago
Can reproduce using the HDD image from OSD:
localhost:~ # podman run --name slem_image -dt registry.suse.de/suse/sle-15-sp5/update/products/elemental55/update/cr/totest/images/suse/sle-micro-iso/5.5:latest /bin/bash
Trying to pull registry.suse.de/suse/sle-15-sp5/update/products/elemental55/update/cr/totest/images/suse/sle-micro-iso/5.5:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 5a42b736fa37 done |
Copying blob fd1a11dfeb8e done |
Copying config 52e8972906 done |
Writing manifest to image destination
Storing signatures
WARN[0099] Path "/etc/SUSEConnect" from "/etc/containers/mounts.conf" doesn't exist, skipping
0dc450fd3d9c8605a3ecf1e530615c9ff11ed0e5228486e095c98e854ae737cc
localhost:~ # podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
localhost:~ # podman logs slem_image
bash: applet not found
localhost:~ #
Updated by ph03nix about 1 month ago
Updated by ph03nix about 1 month ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Updated by openqa_review 23 days ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sle_micro_rancher_image
https://openqa.suse.de/tests/14555524#step/slem_rancher/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.