#62 Fedora-27-updates-testing-20180309.0 FINISHED_INCOMPLETE
Opened 2 years ago by dustymabe. Modified 2 years ago

pungi.global.log

[INFO    ] [FAIL] Ostree (variant Everything, arch x86_64) failed, but going on anyway.
[INFO    ] Runroot task failed: 25583176. See /mnt/koji/compose/updates/Fedora-27-updates-testing-20180309.0/logs/x86_64/Everything/ostree-4/runroot.log for more details.

weird.. here is the error:

DEBUG util.py:522:  Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '20e12ea6f30046b19fad8b894cf2d7f6', '-D', '/var/lib/mock/f27-build-11744657-873486/root', '-a', '--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', '/bin/sh', '-c', '{ rm -f /var/lib/rpm/__db*; rm -rf /var/cache/yum/*; set -x; pungi-make-ostree tree --repo=/mnt/koji/compose/atomic/repo --log-dir=/mnt/koji/compose/updates/Fedora-27-updates-testing-20180309.0/logs/x86_64/Everything/ostree-4 --treefile=/mnt/koji/compose/updates/Fedora-27-updates-testing-20180309.0/work/ostree-4/config_repo/fedora-ostree-workstation-updates-testing.json --extra-config=/mnt/koji/compose/updates/Fedora-27-updates-testing-20180309.0/work/ostree-4/extra_config.json; } < /dev/null 2>&1 | /usr/bin/tee /builddir/runroot.log; exit ${PIPESTATUS[0]}'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8'} and shell False
DEBUG util.py:296:  Unsharing. Flags: 134217728
DEBUG util.py:439:  Failed to register machine: File exists
DEBUG util.py:577:  Child return code was: 1
DEBUG util.py:188:  kill orphans

The Failed to register machine: File exists is interesting.. I wonder what packages changed since yesterday..

And Failed to register machine: File exists seems to be the fatal error?

Offhand I'd guess it's a race condition/bug in nspawn. Does running nspawn directly work? What about in a loop/concurrently?

Since it's FAW and it didn't FAIL the run I guess it's safe to wait and see if it happens again (I've got enough other stuff to investigate right now anyway). Will see if the next run has the same problem.

Login to comment on this ticket.

Metadata