Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1434347 - FTBFS due silent crash in debuginfo extraction
Summary: FTBFS due silent crash in debuginfo extraction
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: docker
Version: rawhide
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2017-03-21 10:20 UTC by Dan Horák
Modified: 2017-03-21 16:24 UTC (History)
13 users (show)

Fixed In Version: rpm-4.13.0.1-14.fc27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 16:24:59 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dan Horák 2017-03-21 10:20:05 UTC 
Description of problem:

...
+ install -d /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/usr/share/man/man8
+ install -p -m 644 rhel-push-plugin.8 /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/usr/share/man/man8
+ install -d /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x//usr/libexec/docker
+ install -p -m 755 _build/src/docker-lvm-plugin /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x//usr/libexec/docker/docker-lvm-plugin
+ install -p -m 644 docker-lvm-plugin-bc03b5354aaa70ee14c482c4a861be08630bb755/systemd/docker-lvm-plugin.service docker-lvm-plugin-bc03b5354aaa70ee14c482c4a861be08630bb755/systemd/docker-lvm-plugin.socket /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/usr/lib/systemd/system
+ install -d /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/usr/share/man/man8
+ install -p -m 644 docker-lvm-plugin.8 /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/usr/share/man/man8
+ mkdir -p /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/etc/docker
+ install -p -m 644 docker-lvm-plugin-bc03b5354aaa70ee14c482c4a861be08630bb755/etc/docker/docker-lvm-plugin /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/etc/docker/docker-lvm-plugin
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --ver-rel 1.13.1-5.git5be1549.fc27 --unique-debug-arch s390x --unique-debug-src-base docker --run-dwz --dwz-low-mem-die-limit 0 --dwz-max-die-limit 50000000 /builddir/build/BUILD/docker-5be1549913ee9bdc5c30433345a76b36ac09bc02
extracting debug info from /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/usr/bin/docker-current
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.UHQccl (%install)
    Bad exit status from /var/tmp/rpm-tmp.UHQccl (%install)
Child return code was: 1
EXCEPTION: [Error()]
...

for full logs please see https://s390.koji.fedoraproject.org/koji/taskinfo?taskID=2529022

As docker-1.13.1-4.git5be1549.fc27 has been built successfully, I suspect something rather changed in the build environment than being docker related.


Version-Release number of selected component (if applicable):
docker-1.13.1-5.git5be1549.fc27
Comment 1 Dan Horák 2017-03-21 10:24:06 UTC 
The buildroot diff between docker-1.13.1-4.git5be1549.fc27 (OK) and docker-1.13.1-5.git5be1549.fc27 (BAD) is

6,8c6,8
< binutils-2.28-2.fc27.s390x
< btrfs-progs-4.9.1-2.fc26.s390x
< btrfs-progs-devel-4.9.1-2.fc26.s390x
---
> binutils-2.28-4.fc27.s390x
> btrfs-progs-4.10.1-1.fc27.s390x
> btrfs-progs-devel-4.10.1-1.fc27.s390x
15,16c15,16
< coreutils-8.26-7.fc26.s390x
< coreutils-common-8.26-7.fc26.s390x
---
> coreutils-8.27-2.fc27.s390x
> coreutils-common-8.27-2.fc27.s390x
18c18
< cpp-7.0.1-0.10.fc26.s390x
---
> cpp-7.0.1-0.12.fc27.s390x
21,23c21,23
< cryptsetup-libs-1.7.3-3.fc26.s390x
< curl-7.53.1-2.fc27.s390x
< cyrus-sasl-lib-2.1.26-28.fc26.s390x
---
> cryptsetup-libs-1.7.4-1.fc27.s390x
> curl-7.53.1-3.fc27.s390x
> cyrus-sasl-lib-2.1.26-29.fc27.s390x
50,53c50,53
< gc-7.6.0-2.fc26.s390x
< gcc-7.0.1-0.10.fc26.s390x
< gcc-c++-7.0.1-0.10.fc26.s390x
< gdb-headless-7.12.50.20170226-4.fc27.s390x
---
> gc-7.6.0-4.fc27.s390x
> gcc-7.0.1-0.12.fc27.s390x
> gcc-c++-7.0.1-0.12.fc27.s390x
> gdb-headless-7.12.50.20170309-5.fc27.s390x
59c59
< glib2-2.51.4-2.fc27.s390x
---
> glib2-2.51.5-1.fc27.s390x
66c66
< gmp-6.1.2-3.fc26.s390x
---
> gmp-6.1.2-4.fc27.s390x
69c69
< gnutls-3.5.9-2.fc26.s390x
---
> gnutls-3.5.10-1.fc27.s390x
75c75
< golang-github-cpuguy83-go-md2man-1.0.4-5.fc25.s390x
---
> golang-github-cpuguy83-go-md2man-1.0.4-7.fc27.s390x
83c83
< info-6.3-2.fc26.s390x
---
> info-6.3-3.fc27.s390x
87,88c87,88
< kernel-headers-4.11.0-0.rc0.git8.2.fc27.s390x
< keyutils-libs-1.5.9-9.fc26.s390x
---
> kernel-headers-4.11.0-0.rc2.git4.1.fc27.s390x
> keyutils-libs-1.5.10-1.fc27.s390x
90c90
< krb5-libs-1.15-9.fc27.s390x
---
> krb5-libs-1.15.1-2.fc27.s390x
94c94
< libasan-7.0.1-0.10.fc26.s390x
---
> libasan-7.0.1-0.12.fc27.s390x
97c97
< libatomic-7.0.1-0.10.fc26.s390x
---
> libatomic-7.0.1-0.12.fc27.s390x
100c100
< libbabeltrace-1.5.2-1.fc27.s390x
---
> libbabeltrace-1.5.2-2.fc27.s390x
106c106
< libcurl-7.53.1-2.fc27.s390x
---
> libcurl-7.53.1-3.fc27.s390x
112c112
< libgcc-7.0.1-0.10.fc26.s390x
---
> libgcc-7.0.1-0.12.fc27.s390x
114,116c114,116
< libgomp-7.0.1-0.10.fc26.s390x
< libgpg-error-1.25-2.fc26.s390x
< libgpg-error-devel-1.25-2.fc26.s390x
---
> libgomp-7.0.1-0.12.fc27.s390x
> libgpg-error-1.27-1.fc27.s390x
> libgpg-error-devel-1.27-1.fc27.s390x
132,133c132,133
< libselinux-2.6-2.fc27.s390x
< libselinux-devel-2.6-2.fc27.s390x
---
> libselinux-2.6-3.fc27.s390x
> libselinux-devel-2.6-3.fc27.s390x
140,141c140,141
< libstdc++-7.0.1-0.10.fc26.s390x
< libstdc++-devel-7.0.1-0.10.fc26.s390x
---
> libstdc++-7.0.1-0.12.fc27.s390x
> libstdc++-devel-7.0.1-0.12.fc27.s390x
144c144
< libubsan-7.0.1-0.10.fc26.s390x
---
> libubsan-7.0.1-0.12.fc27.s390x
152c152
< lz4-1.7.5-2.fc26.s390x
---
> lz4-libs-1.7.5-3.fc27.s390x
155c155
< mpfr-3.1.5-2.fc26.s390x
---
> mpfr-3.1.5-3.fc27.s390x
163c163
< nss-pem-1.0.3-1.fc27.s390x
---
> nss-pem-1.0.3-3.fc27.s390x
169a170
> openblas-srpm-macros-1-1.fc27.noarch
171,173c172,174
< openssh-7.4p1-3.fc26.s390x
< openssh-clients-7.4p1-3.fc26.s390x
< openssl-libs-1.1.0d-3.fc26.s390x
---
> openssh-7.4p1-4.fc27.s390x
> openssh-clients-7.4p1-4.fc27.s390x
> openssl-libs-1.1.0e-1.fc27.s390x
176c177
< pam-1.3.0-1.fc25.s390x
---
> pam-1.3.0-2.fc27.s390x
183c184
< perl-5.24.1-389.fc26.s390x
---
> perl-5.24.1-390.fc27.s390x
186c187
< perl-Errno-1.25-389.fc26.s390x
---
> perl-Errno-1.25-390.fc27.s390x
194c195
< perl-IO-1.36-389.fc26.s390x
---
> perl-IO-1.36-390.fc27.s390x
198c199
< perl-Pod-Perldoc-3.27-2.fc26.noarch
---
> perl-Pod-Perldoc-3.28-1.fc27.noarch
211,212c212,213
< perl-libs-5.24.1-389.fc26.s390x
< perl-macros-5.24.1-389.fc26.s390x
---
> perl-libs-5.24.1-390.fc27.s390x
> perl-macros-5.24.1-390.fc27.s390x
226c227
< python3-3.6.0-20.fc26.s390x
---
> python3-3.6.1-0.1.rc1.fc27.s390x
228c229
< python3-libs-3.6.0-20.fc26.s390x
---
> python3-libs-3.6.1-0.1.rc1.fc27.s390x
238,242c239,243
< rpm-4.13.0.1-3.fc26.s390x
< rpm-build-4.13.0.1-3.fc26.s390x
< rpm-build-libs-4.13.0.1-3.fc26.s390x
< rpm-libs-4.13.0.1-3.fc26.s390x
< rpm-plugin-selinux-4.13.0.1-3.fc26.s390x
---
> rpm-4.13.0.1-12.fc27.s390x
> rpm-build-4.13.0.1-12.fc27.s390x
> rpm-build-libs-4.13.0.1-12.fc27.s390x
> rpm-libs-4.13.0.1-12.fc27.s390x
> rpm-plugin-selinux-4.13.0.1-12.fc27.s390x
249,250c250,251
< system-python-3.6.0-20.fc26.s390x
< system-python-libs-3.6.0-20.fc26.s390x
---
> system-python-3.6.1-0.1.rc1.fc27.s390x
> system-python-libs-3.6.1-0.1.rc1.fc27.s390x
256c257
< tzdata-2016j-3.fc26.noarch
---
> tzdata-2017a-1.fc27.noarch
Comment 2 Mark Wielaard 2017-03-21 10:31:28 UTC 
I think this might indeed be caused by a recent change in rpm debugedit. Could I get access to the builder, a similar build environment or a copy of the file that causes trouble when extracting debug info from /builddir/build/BUILDROOT/docker-1.13.1-5.git5be1549.fc27.s390x/usr/bin/docker-current
Comment 3 Mark Wielaard 2017-03-21 16:24:59 UTC 
This was a "simple" off by one that for various reasons didn't trigger on any other arch or build. But it was a generic issue, nothing specific to go, docker or s390x.

Patch posted upstream:
http://lists.rpm.org/pipermail/rpm-maint/2017-March/005268.html

Added to fedora rpm in rawhide (rpm-4.13.0.1-14.fc27).
Note You need to log in before you can comment on or make changes to this bug.