Confirmations for:

1) lxd-images import ubuntu wily --alias ubuntu; lxc launch ubuntu test; sleep 
10s; lxc stop test
Confirmed: It does not shutdown.

2) Executing "shutdown" manually inside the container (through lxc exec) does 
shutdown the container
Confirmed: It does not shutdown.

3) Manually doing "kill -SIGPWR <PID>" where <PID> is the init pid as reported 
by "lxc info test", also doesn't shutdown the container for you.
Confirmed: It does not shutdown.


These are the process trees before and after 1), 2) and 3):

BEFORE
22172 ?        Ss     0:00 /usr/bin/lxd forkstart test /var/lib/lxd/containers 
/tmp/lxd_lxc_startconfig_380151542
22191 ?        Ss     0:00  \_ /sbin/init
22413 ?        Ss     0:00      \_ /lib/systemd/systemd-journald
22857 ?        Ss     0:00      \_ dhclient -1 -v -pf /run/dhclient.eth0.pid 
-lf /var/lib/dhcp/dhclient.eth0.leases eth0
22991 ?        Ss     0:00      \_ /usr/sbin/irqbalance 
--pid=/var/run/irqbalance.pid
22992 ?        Ss     0:00      \_ /usr/bin/dbus-daemon --system 
--address=systemd: --nofork --nopidfile --systemd-activation
23040 ?        Ss     0:00      \_ /usr/sbin/cron -f
23092 ?        S      0:00      \_ /bin/sh /etc/init.d/ondemand background
23119 ?        S      0:00      |   \_ sleep 60
23093 ?        Ss     0:00      \_ /lib/systemd/systemd-logind
23152 ?        Ssl    0:00      \_ /usr/lib/accountsservice/accounts-daemon
23207 ?        S      0:00      \_ dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.4.1 
--dhcp-range 10.0.4.2,10.0.4.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
23215 ?        Ss     0:00      \_ /sbin/cgproxy
23240 ?        Ssl    0:00      \_ /usr/sbin/rsyslogd -n
23288 ?        Ss     0:00      \_ /usr/sbin/atd -f
23329 ?        Ssl    0:00      \_ /usr/lib/policykit-1/polkitd --no-debug
23633 ?        Ss     0:00      \_ /usr/sbin/sshd -D
23751 pts/4    Ss+    0:00      \_ /sbin/agetty --noclear --keep-baud console 
115200 38400 9600 vt220

AFTER
22172 ?        Ss     0:00 /usr/bin/lxd forkstart test /var/lib/lxd/containers 
/tmp/lxd_lxc_startconfig_380151542
22191 ?        Ss     0:00  \_ /sbin/init
22413 ?        Ss     0:00      \_ /lib/systemd/systemd-journald
22992 ?        Ss     0:00      \_ /usr/bin/dbus-daemon --system 
--address=systemd: --nofork --nopidfile --systemd-activation
23092 ?        Z      0:00      \_ [ondemand] <defunct>
24998 ?        Zs     0:00      \_ [systemctl] <defunct>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499

Title:
  [systemd] SIGPWR doesn't always lead to shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to