Comparing installed_pkgs.log between success and failure cases, I note that the failed build was using the stock CentOS rpm, while the success case used rpm-4.14.0-1.tis.1.

I think we should try adding...

    BuildRequires:    rpm-devel >= 4.14.0
    BuildRequires:    rpm-libs >= 4.14.0

... to the containerd spec.

This should induce an upgrade to the newer rpm.


On 2020-02-05 10:42 a.m., Penney, Don wrote:

I don’t see any recent updates that would point to this, but I’m trying a build of my own to see if I can reproduce this failure.

 

 

From: Scott Little [mailto:scott.little@windriver.com]
Sent: Wednesday, February 05, 2020 10:25 AM
To: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure!

 

Failed to build containerd-1.3.0-1.tis.src.rpm

 

+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src
extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc
extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl
*** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl

 

Previous build success looked like this ... note the extra arguments ...

+ /usr/lib/rpm/find-debuginfo.sh -j24 --strict-build-id -m --build-id-seed 1.3.0-1.tis --unique-debug-suffix -1.3.0-1.tis.x86_64 --unique-debug-src-base containerd-1.3.0-1.tis.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src
extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl
extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc
*** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl
readelf: /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/lib/debug/usr/bin/runc-1.3.0-1.tis.x86_64.debug: Error: the dynamic segment offset + size exceeds the size of the file
/usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 1 CRC32s did match.
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
+ /usr/lib/rpm/redhat/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Processing files: containerd-1.3.0-1.tis.x86_64
warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim
warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v1
warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v2
warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl
Provides: containerd containerd = 1.3.0-1.tis containerd(x86-64) = 1.3.0-1.tis containerd.io runc
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) libseccomp.so.2()(64bit) rtld(GNU_HASH)
Processing files: containerd-debuginfo-1.3.0-1.tis.x86_64
Provides: containerd-debuginfo = 1.3.0-1.tis containerd-debuginfo(x86-64) = 1.3.0-1.tis
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64
Wrote: /builddir/build/RPMS/containerd-1.3.0-1.tis.x86_64.rpm
Wrote: /builddir/build/RPMS/containerd-debuginfo-1.3.0-1.tis.x86_64.rpm
 

There is nothing obvious in the change log.  Looking for something environmental...

 

Scott

 

 

 

On 2020-02-04 11:58 p.m., build.starlingx@gmail.com wrote:

Project: STX_build_master_master
Build #: 408
Status: Failure
Timestamp: 20200205T023000Z
 
Check logs at:
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs
--------------------------------------------------------------------------------
Parameters
 
BUILD_CONTAINERS_DEV: false
BUILD_CONTAINERS_STABLE: false



_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss