openSUSE Release Process » Jump 15.2

I am able to recreate the failure on a Leap15.2 ppc64le qemu guest.

tw152:~ # mkdir rootfs
tw152:~ # docker export $(docker create busybox) | tar -C rootfs -xvf -
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
368841f1302b: Pulling fs layer
368841f1302b: Download complete
368841f1302b: Pull complete
Digest: sha256:836945da1f3afe2cfff376d379852bbb82e0237cb2925d53a13f53d6e8a8c48c
Status: Downloaded newer image for busybox:latest
Error response from daemon: Error exporting container 9dcd31d6f246ba507c3f81bb477161328a248ec29e49b9296dfb4bf157906db8: error processing tar file: docker-tar: reloc
ation error: /lib64/libnss_files.so.2: symbol __libc_readline_unlocked, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
: exit status 127
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

about libnss_files.so.2 & libc.so.6 reported error, the two files are from same installed rpm:

tw152:~ # rpm -qf /lib64/libnss_files.so.2
glibc-2.26-lp152.24.9.ppc64le
tw152:~ # rpm -qf /lib64/libc.so.6
glibc-2.26-lp152.24.9.ppc64le
tw152:~ # rpm -qi glibc-2.26-lp152.24.9.ppc64le |grep -E 'Date|Source'
Install Date: Wed May 27 18:29:07 2020
Source RPM  : glibc-2.26-lp152.24.9.src.rpm
Build Date  : Mon May 25 14:10:16 2020

looking on the web, identified a similar moby issue that suggest to upgrade docker to 19.03.8
https://github.com/moby/moby/issues/39449

Is it the right direction ?

Oups, forgot to specify that current Leap15.2 docker is version 19.03.5

tw152:~ # docker -v
Docker version 19.03.5, build 633a0ea838f1
tw152:~ # rpm -qi docker |grep -E 'Date|Source'
Install Date: Thu May 28 09:16:53 2020
Source RPM  : docker-19.03.5_ce-lp152.1.18.src.rpm
Build Date  : Tue May 26 00:02:46 2020

BUT on TW we do not have above failure,with same docker 19.03.5

twppc64le2:~ # docker -v
Docker version 19.03.5, build 633a0ea838f1
twppc64le2:~ # rpm -qi docker |grep -E 'Date|Source'
Install Date: Thu May 28 10:31:47 2020
Source RPM  : docker-19.03.5_ce-4.1.src.rpm
Build Date  : Mon Jan 13 23:50:43 2020
twppc64le2:~ # rpm -qi glibc |grep -E 'Date|Source'
Install Date: Thu Apr  2 17:14:43 2020
Source RPM  : glibc-2.31-3.1.src.rpm
Build Date  : Wed Mar 18 12:23:55 2020

I do not know how to continue investigation.

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode_containers
https://openqa.opensuse.org/tests/1296843

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

• Interesting to note that test passed with Build 311.1 https://openqa.opensuse.org/tests/1308707#step/docker_runc/23
• failed on previous 310.3 https://openqa.opensuse.org/tests/1307968#step/docker_runc/22

The only think I could recommend would be to run the docker create and docker export explicitly so that it is obvious which of the commands failed.

same failure for Jump: https://openqa.opensuse.org/tests/1380979#step/docker_runc/24

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode_containers
https://openqa.opensuse.org/tests/1393255

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode_containers
https://openqa.opensuse.org/tests/1424052

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

This is imo fixed and can be closed now.