[systemd-bugs] [Bug 87732] New: nspawn catches kill signal only when using jenkins

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87732

            Bug ID: 87732
           Summary: nspawn catches kill signal only when using jenkins
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: joel at teichroeb.net
        QA Contact: systemd-bugs at lists.freedesktop.org

When running 217 on arch linux everything works exactly as expected, but after
upgrading to 218 nspawn will always report "Container root terminated by signal
KILL." when it is run by jenkins, but if I run it with the exact same
environment through ssh it succeeds. I've been trying all day to find a way to
reproduce the issues outside of jenkins, but I have been unable to.

The exact task I'm trying to do is build packages for arch linux using the
mkchrootpkg command provided by the arch devtools, which in turn uses
systemd-nspawn in order to create a clean environment for building the package
in.

I've tried
217: Works
218: Does not work
master: Does not work

I'm going to try bisecting, but I'd appreciate if anyone has any better ideas
about what could be causing this.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141226/35d8413c/attachment.html>