Bug ID 1008898
Summary KIWI can't unmount sysfs (is in use by systemd-logind)
Classification openSUSE
Product openSUSE Distribution
Version Leap 42.1
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee ms@suse.com
Reporter svollath@suse.com
QA Contact qa-bugs@suse.de
CC thardeck@suse.com
Found By ---
Blocker ---

Created attachment 700932 [details]
KIWI logs + config

When building an appliance with kiwi (in this case using "machinery build"),
kiwi finishes SUCCESSFUL, but machinery can't cleanup its temporary files. This
is because kiwi leaves a sysfs mount open which requires a reboot to get rid
of.

((Reproduced with Leap 42.1, 42.2, kiwi-7.03.97, kiwi-7.04.8, kiwi-7.04.13))

Buildlog snippets:
...
Nov-07 14:52:18 <1> : EXEC [mount -n -t sysfs sysfs
/tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys]
...
Nov-07 14:56:36 <1> : EXEC [umount
"/tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys" 2>&1]
Nov-07 14:56:36 <2> : Umount of
/tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys failed: umount:
/tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)
...
Nov-07 15:02:05 <1> : Closing session with ecode: 0
Nov-07 15:02:06 <1> : KIWI exited successfully

... see full log and config attached.

# mount | grep sysfs
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
sysfs on /tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys type
sysfs (rw,relatime)

# lsof /tmp/machinery-image20161107-10165-1js1i2p/build/image-root/sys
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/10570/gvfs
      Output information may be incomplete.
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
systemd-l 2046 root    6r   REG   0,17     4096 18025
/sys/devices/virtual/tty/tty0/active
((root      2046  0.0  0.0  20108  2608 ?        Ss   Nov04   0:01
/usr/lib/systemd/systemd-logind))


You are receiving this mail because: