[gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - cloud/stage4-cloud.spec

* dhcpcd has zeroconf support active by default.
 * This means it will always obtain an IP address even if no
 * DHCP server can be contacted, which will break any existing
 * failover support you may have configured in your net configuration.
 * This behaviour can be controlled with the noipv4ll configuration
 * file option or the -L command line switch.
 * See the dhcpcd and dhcpcd.conf man pages for more details.
 * 
 * Dhcpcd has duid enabled by default, and this may cause issues
 * with some dhcp servers. For more information, see
 * https://bugs.gentoo.org/show_bug.cgi?id=477356
 * 
 * If you activate the lookup-hostname hook to look up your hostname
 * using the dns, you need to install net-dns/bind-tools.
 * Messages for package sys-power/acpid-2.0.28:
 * 
 * You may wish to read the Gentoo Linux Power Management Guide,
 * which can be found online at:
 * https://wiki.gentoo.org/wiki/Power_management/Guide
 * 
 * You should reboot the system now to get /run mounted with tmpfs!
 * Messages for package dev-util/ctags-20161028:
 * You can set the version to be started by /usr/bin/ctags through
 * the ctags eselect module. "man ctags.eselect" for details.
 * Messages for package dev-python/pyjwt-1.4.0:
 * Available optional features:
 *   dev-python/flake8 for flake8
 * flake8 feature requires 'flake8-import-order' and 'pep8-naming', which are not in portage yet
 * Messages for package mail-mta/nullmailer-1.13-r5:
 * To create an initial setup, please do:
 * emerge --config =mail-mta/nullmailer-1.13-r5
 * Messages for package app-admin/logrotate-3.11.0:
 * The logrotate binary is now installed under /usr/bin. Please
 * update your links
 * 
 * If you wish to have logrotate e-mail you updates, please
 * emerge virtual/mailx and configure logrotate in
 * /etc/logrotate.conf appropriately
 * 
 * Additionally, /etc/logrotate.conf may need to be modified
 * for your particular needs.  See man logrotate for details.
 * Messages for package sys-boot/grub-2.02_beta3-r1:
 * For information on how to configure GRUB2 please refer to the guide:
 *     https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
 * 
 * For manual configuration, see /usr/share/doc/grub-2.02_beta3-r1/grub.cfg.example
 * 
 * You may consider installing the following optional packages:
 *   sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
 *   dev-libs/libisoburn for Create rescue media (grub-mkrescue)
 *   sys-fs/mdadm for Enable RAID device detection
 * Messages for package app-emulation/cloud-init-0.7.9:
 * cloud-init-local needs to be run in the boot runlevel because it
 * modifies services in the default runlevel.  When a runlevel is started
 * it is cached, so modifications that happen to the current runlevel
 * while you are in it are not acted upon.
 * Messages for package app-vim/gentoo-syntax-20170225:
 * Note for developers and anyone else who edits ebuilds:
 *     This release of gentoo-syntax now contains filetype rules to set
 *     fileencoding for ebuilds and ChangeLogs to utf-8 as per GLEP 31.
 *     If you find this feature breaks things, please submit a bug and
 *     assign it to vim@g.o. You can use the 'ignore-glep31' USE
 *     flag to remove these rules.
 * Messages for package app-admin/sudo-1.8.18_p1:
 * To use the -A (askpass) option, you need to install a compatible
 * password program from the following list. Starred packages will
 * automatically register for the use with sudo (but will not force
 * the -A option):
 * 
 *  [*] net-misc/ssh-askpass-fullscreen
 *      net-misc/x11-ssh-askpass
 * 
 * You can override the choice by setting the SUDO_ASKPASS environmnent
 * variable to the program you want to use.




























removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309/tmp/stage4-chroot.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309/tmp/chroot-functions.sh from the chroot
09 Mar 2017 08:08:33 UTC: NOTICE  : --- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309/tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309 /tmp/pre-kmerge.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/genkernel-3.4.52.4-r2
>>> Emerging (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 2) app-arch/cpio-2.12-r1::gentoo
>>> Emerging (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
>>> Installing (2 of 2) sys-kernel/genkernel-3.4.52.4-r2::gentoo
 * Messages for package sys-kernel/genkernel-3.4.52.4-r2:
 * Documentation is available in the genkernel manual page
 * as well as the following URL:
 * https://www.gentoo.org/doc/en/genkernel.xml
 * This package is known to not work with reiser4.  If you are running
 * reiser4 and have a problem, do not file a bug.  We know it does not
 * work and we don't plan on fixing it since reiser4 is the one that is
 * broken in this regard.  Try using a sane filesystem like ext4.
 * The LUKS support has changed from versions prior to 3.4.4.  Now,
 * you use crypt_root=/dev/blah instead of real_root=luks:/dev/blah.


removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309/tmp/pre-kmerge.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309/tmp/chroot-functions.sh from the chroot
Copying kmerge.sh to /tmp
copying kmerge.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309/tmp
Ensure the file has the executable bit set
Running kmerge.sh in chroot:
    chroot /home/release/buildroot/amd64-dev/tmp/default/stage4-amd64-cloud-20170309 /tmp/kmerge.sh
>>> Regenerating /etc/ld.so.cache...
Genkernel version 3.4.52.4 found ... OK
emerge --quiet --usepkg --buildpkg --newuse gentoo-sources
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-kernel/gentoo-sources-4.9.6-r1::gentoo
>>> Installing (1 of 1) sys-kernel/gentoo-sources-4.9.6-r1::gentoo
>>> Recording sys-kernel/gentoo-sources in "world" favorites file...
 * Messages for package sys-kernel/gentoo-sources-4.9.6-r1:
 * If you are upgrading from a previous kernel, you may be interested
 * in the following document:
 *   - General upgrade guide: https://wiki.gentoo.org/wiki/Kernel/Upgrade


Adjusting /usr/src/linux to point to /usr/src/linux-4.9.6-gentoo-r1
Setting extraversion to openstack
* Gentoo Linux Genkernel; Version 3.4.52.4
* Running with options: --all-ramdisk-modules --cachedir=/tmp/kerncache/gentoo-genkernel_cache-cloud-20170309 --no-mountboot --kerneldir=/usr/src/linux --modulespackage=/tmp/kerncache/gentoo-modules-cloud-20170309.tar.bz2 --minkernpackage=/tmp/kerncache/gentoo-kernel-initrd-cloud-20170309.tar.bz2 all --kernel-config=/var/tmp/gentoo.config

* Using genkernel.conf from /etc/genkernel.conf
* Sourcing arch-specific config.sh from /usr/share/genkernel/arch/x86_64/config.sh ..
* Sourcing arch-specific modules_load from /usr/share/genkernel/arch/x86_64/modules_load ..

* Linux Kernel 4.9.6-gentoo-r1-openstack for x86_64...
* .. with config file /var/tmp/gentoo.config
* kernel: Using config from /var/tmp/gentoo.config
* kernel: >> Running mrproper...
*         >> Running oldconfig...
* kernel: >> Cleaning...
*         >> Compiling 4.9.6-gentoo-r1-openstack bzImage...
10 Mar 2017 03:38:52 UTC: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'kernel', 'gentoo']) exited -15
10 Mar 2017 03:38:52 UTC: ERROR   : CatalystError: build aborting due to kernel build error.
Traceback (most recent call last):
  File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1532, in build_kernel
    self._build_kernel(kname = kname)
  File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1569, in _build_kernel
    env=self.env)
  File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 54, in cmd
    print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'kernel', 'gentoo']) exited -15
10 Mar 2017 03:38:52 UTC: ERROR   : Exception running action sequence build_kernel
Traceback (most recent call last):
  File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1532, in build_kernel
    self._build_kernel(kname = kname)
  File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1569, in _build_kernel
    env=self.env)
  File "/usr/lib64/python3.4/site-packages/catalyst/support.py", line 54, in cmd
    print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'kernel', 'gentoo']) exited -15

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1412, in run
    getattr(self, x)()
  File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1538, in build_kernel
    print_traceback=True)
catalyst.support.CatalystError: build aborting due to kernel build error.
10 Mar 2017 03:38:52 UTC: NOTICE  : Cleaning up... Running unbind()
Command exited with non-zero status 2
1140.68user 245.40system 19:54:40elapsed 1%CPU (0avgtext+0avgdata 343828maxresident)k
1793inputs+7527257outputs (0major+183605711minor)pagefaults 0swaps



Full build log at /home/release/tmp/run/catalyst-auto.20170309.bt5alz/log/cloud_stage4-cloud.log