kvm/generic-amd64: system got in a broken state in the second boot

[Ricardo Salveti]

$ sudo ubuntu-device-flash core 15.04 --channel edge --oem generic-amd64 --install=webdm --enable-ssh --output ubuntu-15.04-snappy-amd64-generic.img
[sudo] password for rsalveti:
Determining oem configuration
Starting download of generic-amd64
41.70 KB / 41.70 KB [] 100.00 % 94.93 KB/s
Done
Starting download of icon for package
38.97 KB / 38.97 KB ] 100.00 % 82.12 KB/s
Done
Fetching information from server...
Downloading and setting up...
42.13 MB / 42.13 MB [] 100.00 % 655.21 KB/s
96.06 MB / 96.06 MB [] 100.00 % 581.35 KB/s
Installing generic-amd64
Starting download of generic-amd64
41.70 KB / 41.70 KB [] 100.00 % 90.61 KB/s
Done
Starting download of icon for package
38.97 KB / 38.97 KB [] 100.00 % 80.65 KB/s
Done
Installing webdm
Starting download of webdm
6.16 MB / 6.16 MB [] 100.00 % 1.00 MB/s
Done
Starting download of icon for package
38.97 KB / 38.97 KB [] 100.00 % 40.49 KB/s
Done
New image complete
Summary:
 Output: ubuntu-15.04-snappy-amd64-generic.img
 Architecture: amd64
 Channel: edge
 Version: 121

Did first boot, was able to login via console and ssh, then decided to abort kvm with control+c. Started the image again (second boot), and now I can't login anymore, image is in a broken state.

syslog attached.

[Ricardo Salveti (rsalveti)]

Some interesting pieces from syslog:
Jul 10 13:48:21 localhost systemd[1]: ubuntu-snappy.boot-ok.service: main process exited, code=exited, status=1/FAILURE
Jul 10 13:48:21 localhost systemd[1]: Failed to start Notify bootloader that boot was successful.
Jul 10 13:48:21 localhost systemd[1]: Unit ubuntu-snappy.boot-ok.service entered failed state.
Jul 10 13:48:21 localhost systemd[1]: ubuntu-snappy.boot-ok.service failed.
Jul 10 13:48:21 localhost systemd[1]: Started Run snappy compatibility hooks.

Jul 10 13:48:46 localhost dbus[565]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Jul 10 13:48:46 localhost systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Jul 10 13:48:46 localhost systemd[1]: Failed to start Login Service.
Jul 10 13:48:46 localhost systemd[1]: Unit systemd-logind.service entered failed state.

Which my explain why I can't login anymore.

[Leo Arias (elopio)]

happens here too.

[Ricardo Salveti (rsalveti)]

The reason is that the writeable partition is in a broken state, files are all empty:

# ls -l etc/dbus-1/system.d
total 0
-rw-r--r-- 1 root root 0 Apr 18 18:11 org.freedesktop.hostname1.conf
-rw-r--r-- 1 root root 0 Apr 18 18:11 org.freedesktop.locale1.conf
-rw-r--r-- 1 root root 0 Apr 18 18:11 org.freedesktop.login1.conf
-rw-r--r-- 1 root root 0 Apr 18 18:11 org.freedesktop.machine1.conf
-rw-r--r-- 1 root root 0 Apr 18 18:11 org.freedesktop.network1.conf
-rw-r--r-- 1 root root 0 Apr 18 18:11 org.freedesktop.resolve1.conf
-rw-r--r-- 1 root root 0 Apr 18 18:11 org.freedesktop.systemd1.conf
-rw-r--r-- 1 root root 0 Apr 18 18:11 org.freedesktop.timedate1.conf
-rw-r--r-- 1 root root 0 Jun 15 12:12 wpa_supplicant.conf

# ls -l apps/webdm/0.9/meta
total 4
-rw-r--r-- 1 root rsalveti 0 Jul 10 10:46 hashes.yaml
drwxr-xr-x 2 syslog fuse 4096 Jul 10 10:46 hooks
-rw-r--r-- 1 syslog fuse 0 Jul 10 10:46 package.yaml
-rw-r--r-- 1 syslog fuse 0 Jul 10 10:46 readme.md
-rw-r--r-- 1 syslog fuse 0 Jul 10 10:46 snappy-config.apparmor
-rw-r--r-- 1 syslog fuse 0 Jul 10 10:46 snappyd.profile
-rw-r--r-- 1 syslog fuse 0 Jul 10 10:46 snappyd.seccomp
-rw-r--r-- 1 syslog fuse 0 Jul 10 10:46 snappyd.snappy-systemd
-rw-r--r-- 1 syslog fuse 0 Jul 10 10:46 webdm-icon.png

[Ricardo Salveti (rsalveti)]

The broken image http://people.canonical.com/~rsalveti/ubuntu-15.04-snappy-amd64-generic-broken.img.xz

[Leo Arias (elopio)]

If I reboot once with sudo reboot, then I'm able to ctrl+c as many times as I want and I still can log in.

All our testing manual and automated does a proper reboot. We'll have to add some tests to kill the machine. adt-run can't kill the vm, but we can probably extend it.

[Leo Arias (elopio)]

I can't reproduce this anymore on rolling/edge/allsnaps.

[Leo Arias (elopio)]

sorry, scratch that. I've just reproduced it.

[Michael Vogt (mvo)]

We are using ubuntu-image for the image building now.

[Zygmunt Krynicki (zyga)]

I'm marking this bug as won't fix as it was reported in snapd 15.04 era. Please re-open with updated information if the original issue is still a problem for you.