Issue #2667
closed
Pulp 2.13 RHEL6 Builds Fail on Koji with Error
Description
The error, seen in this build log, makes Pulp 2.13 nightly builds fail on el6:
Processing files: pulp-server-2.13.0-0.1.alpha.git.18761.8bac271.el6.noarch
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.AZiLs9
+ umask 022
+ cd /builddir/build/BUILD
+ cd pulp-git-18761.8bac271
+ DOCDIR=/builddir/build/BUILDROOT/pulp-2.13.0-0.1.alpha.git.18761.8bac271.el6.noarch/usr/share/doc/pulp-server-2.13.0
+ export DOCDIR
+ rm -rf /builddir/build/BUILDROOT/pulp-2.13.0-0.1.alpha.git.18761.8bac271.el6.noarch/usr/share/doc/pulp-server-2.13.0
+ /bin/mkdir -p /builddir/build/BUILDROOT/pulp-2.13.0-0.1.alpha.git.18761.8bac271.el6.noarch/usr/share/doc/pulp-server-2.13.0
+ cp -pr README LICENSE COPYRIGHT /builddir/build/BUILDROOT/pulp-2.13.0-0.1.alpha.git.18761.8bac271.el6.noarch/usr/share/doc/pulp-server-2.13.0
+ exit 0
Provides: config(pulp-server) = 2.13.0-0.1.alpha.git.18761.8bac271.el6
Requires(interp): /bin/sh /bin/sh
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires(pre): /bin/sh
Requires(preun): /bin/sh
Requires: /bin/bash /bin/sh /usr/bin/env /usr/bin/python python(abi) = 2.6
Obsoletes: pulp
Processing files: pulp-nodes-common-2.13.0-0.1.alpha.git.18761.8bac271.el6.noarch
RPM build errors:
error: Explicit file attributes required in spec for: /builddir/build/BUILDROOT/pulp-2.13.0-0.1.alpha.git.18761.8bac271.el6.noarch/etc/pki/pulp/nodes/node.crt
Explicit file attributes required in spec for: /builddir/build/BUILDROOT/pulp-2.13.0-0.1.alpha.git.18761.8bac271.el6.noarch/etc/pki/pulp/nodes/node.crt
Child return code was: 1
EXCEPTION: Command failed. See logs for output.
# ['bash', '--login', '-c', 'rpmbuild -bb --target noarch --nodeps builddir/build/SPECS/pulp.spec']
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 70, in trace
result = func(*args, **kw)
File "/usr/lib/python2.6/site-packages/mockbuild/util.py", line 359, in do
raise mockbuild.exception.Error, ("Command failed. See logs for output.\n # %s" % (command,), child.returncode)
Error: Command failed. See logs for output.
# ['bash', '--login', '-c', 'rpmbuild -bb --target noarch --nodeps builddir/build/SPECS/pulp.spec']
LEAVE do --> EXCEPTION RAISED
Related issues
Updated by semyers about 7 years ago
This does not block the release of 2.13, but is unfortunate, since we do at least want to see el6 nightlies succeeding to build and get smashed as a bit of a safety net for downstream partners that still do deploy pulp into el6 environments.
I'm not really sure how we want to prioritize this. I think it's probably either important, or WONTFIX and we stop building unsupported packages for nightly testing.
As far as I can tell, the supported el6 packages (pulp-agent, some consumer stuff, etc) are still building without error.
Updated by semyers about 7 years ago
- Subject changed from Pulp 2.13 Builds Fail on Koji with Error to Pulp 2.13 RHEL6 Builds Fail on Koji with Error
Updated by mhrivnak about 7 years ago
This work might be related to causing the failure: https://github.com/pulp/pulp/pull/2898
Updated by semyers about 7 years ago
At this time, I cannot explain why that change only make el6 builds fail. The fact that EL7 and Fedora don't complain about this make me think it's a bug (or something) in rpmbuild that has since been fixed.
Updated by ttereshc about 7 years ago
During triage we skipped this one to decide whether or not we'd like to continue doing:
- nightlies for el6 at all
- nightlies for 2.12 on el6, but not for 2.13 on el6 if possible
Updated by semyers about 7 years ago
- Related to Task #2674: Disable el6 builds for 2.13 added
Updated by bmbouter about 7 years ago
+1 to disabling el6 builds since they are no longer supported.
Updated by ttereshc about 7 years ago
- Related to Task #2685: Build python-celery 3.1.17 for el6 added
Updated by ttereshc about 7 years ago
- Status changed from NEW to CLOSED - WONTFIX
If anyone feels strong that it is needed, please re-open the issue
.