Ussuri content provider job failing during validations-common rpm build with error: Directory not found: /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/ansible

Bug #1952773 reported by Sandeep Yadav
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Critical
Unassigned

Bug Description

Description:

Ussuri content provider job failing during validations-common rpm build with error: Directory not found: /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/ansible

Failure started on 30th Nov:

https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-8-content-provider-ussuri

Logs:-

https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_a91/818794/4/gate/tripleo-ci-centos-8-content-provider-ussuri/a919923/logs/undercloud/home/zuul/DLRN/data/repos/component/validation/01/8c/018c23c1881ef01259cfa786995ea2abd127fdf7_dev/build.log
~~~
Processing files: validations-common-1.0.1-0.20211130141046.018c23c.el8.noarch
error: Directory not found: /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/ansible
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.ApO7cx
+ umask 022
+ cd /builddir/build/BUILD
+ cd validations-common-1.0.1.dev2
+ DOCDIR=/builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/doc/validations-common
+ export LC_ALL=C
+ LC_ALL=C
+ export DOCDIR
+ /usr/bin/mkdir -p /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/doc/validations-common
+ cp -pr README.rst /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/doc/validations-common
+ cp -pr AUTHORS /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/doc/validations-common
+ cp -pr ChangeLog /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/doc/validations-common
+ exit 0
Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.moG4Pt
+ umask 022
+ cd /builddir/build/BUILD
+ cd validations-common-1.0.1.dev2
+ LICENSEDIR=/builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/licenses/validations-common
+ export LC_ALL=C
+ LC_ALL=C
+ export LICENSEDIR
+ /usr/bin/mkdir -p /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/licenses/validations-common
+ cp -pr LICENSE /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/licenses/validations-common
+ exit 0
RPM build errors:
    Directory not found: /builddir/build/BUILDROOT/validations-common-1.0.1-0.20211130141046.018c23c.el8.x86_64/usr/share/ansible
Child return code was: 1
EXCEPTION: [Error()]
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 95, in trace
    result = func(*args, **kw)
  File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 746, in do_with_status
    raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode)
mockbuild.exception.Error: Command failed:
 # /usr/bin/systemd-nspawn -q -M d4795b486d88460cafbf2827116fba29 -D /var/lib/mock/dlrn-centos8-x86_64-1/root -a --capability=cap_ipc_lock --bind=/tmp/mock-resolv.o6jej8wc:/etc/resolv.conf --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=en_US.UTF-8 -u mockbuild bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/validations-common.spec
~~~

Changed in tripleo:
status: New → Triaged
tags: removed: promotion-blocker
Revision history for this message
Sandeep Yadav (sandeepyadav93) wrote :

This failure was cleared on rerun, Keeping this issue under observation in case it reappears.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.