http://bugzilla.suse.com/show_bug.cgi?id=1131084 Bug ID: 1131084 Summary: Build packages in docker fails /usr/lib/rpm/find-debuginfo.sh: line 519: /dev/fd/62: No such file or directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: william.brown@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- [ 125s] /usr/lib/rpm/find-debuginfo.sh: line 519: /dev/fd/62: No such file or directory [ 125s] sort: fflush failed: 'standard output': Broken pipe [ 125s] sort: write error [ 125s] cpio: acl.yy.cpp: Cannot stat: No such file or directory [ 125s] cpio: aclscan.l: Cannot stat: No such file or directory [ 125s] cpio: acltext.y: Cannot stat: No such file or directory [ 125s] 28724 blocks [ 125s] + /usr/lib/rpm/brp-compress [ 126s] + /usr/lib/rpm/brp-suse [ 126s] calling /usr/lib/rpm/brp-suse.d/brp-05-permissions [ 126s] /usr/sbin/ns-slapd: unknown group dirsrv [ 126s] setting / to root:root 0755. (wrong owner/group abuild:abuild) [ 126s] setting /etc/ to root:root 0755. (wrong owner/group abuild:abuild) [ 126s] setting /usr/ to root:root 0755. (wrong owner/group abuild:abuild) [ 126s] setting /var/log/ to root:root 0755. (wrong owner/group abuild:abuild) [ 126s] calling /usr/lib/rpm/brp-suse.d/brp-15-strip-debug [ 126s] /usr/lib/rpm/brp-suse.d/brp-15-strip-debug: line 33: /dev/fd/62: No such file or directory [ 126s] /usr/lib/rpm/brp-suse.d/brp-15-strip-debug: line 47: /dev/fd/62: No such file or directory [ 126s] error: Bad exit status from /var/tmp/rpm-tmp.PueDSo (%install) [ 126s] [ 126s] [ 126s] RPM build errors: [ 126s] Bad exit status from /var/tmp/rpm-tmp.PueDSo (%install) [ 126s] [ 126s] failed "build 389-ds.spec" at Mon Apr 1 03:03:29 UTC 2019. [ 126s] This can be demonstrated by using docker with no udev running. I was building the 389-ds package from network:ldap when I received this error. Using this exact same spec and build on a real virtual machine, the build is able to succeed. Both were fully updated on Apr 1st 2019. As a result, it can only be concluded that there is some kind of issues with find-debuginfo.sh, bash, or something else, that only affects execution while inside of docker without udev present. -- You are receiving this mail because: You are on the CC list for the bug.