Public bug reported:
Since snappy is now installed by default on cloud images, it fails to
start:
● ubuntu-snappy.boot-ok.service - Notify bootloader that boot was successful
Loaded: loaded (/lib/systemd/system/ubuntu-snappy.boot-ok.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2016-04-08 08:33:05 CEST; 6min
ago
Process: 938 ExecStart=/usr/bin/snappy booted (code=exited, status=1/FAILURE)
Main PID: 938 (code=exited, status=1/FAILURE)
Apr 08 08:33:05 autopkgtest systemd[1]: Starting Notify bootloader that boot
was successful...
Apr 08 08:33:05 autopkgtest snappy[938]: No option snappy_os in section
Apr 08 08:33:05 autopkgtest /usr/bin/snappy[938]: main.go:50: DEBUG:
[/usr/bin/snappy booted] failed: No option snappy_os in section
Apr 08 08:33:05 autopkgtest systemd[1]: ubuntu-snappy.boot-ok.service: Main
process exited, code=exited, status=1/FAILURE
Apr 08 08:33:05 autopkgtest systemd[1]: Failed to start Notify bootloader that
boot was successful.
Apr 08 08:33:05 autopkgtest systemd[1]: ubuntu-snappy.boot-ok.service: Unit
entered failed state.
Apr 08 08:33:05 autopkgtest systemd[1]: ubuntu-snappy.boot-ok.service: Failed
with result 'exit-code'.
ubuntu-snappy.run-hooks.service - Regenerate snappy security policies
Loaded: loaded (/lib/systemd/system/ubuntu-snappy.run-hooks.service;
enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2016-04-08 08:33:04 CEST; 6min
ago
Process: 596 ExecStart=/bin/sh -c set -ex; if ! cmp
/usr/share/snappy/security-policy-version
/var/lib/snappy/security-policy-version; then /usr/bin/snappy policygen
--regenerate-all; cp /usr/share/snappy/security-policy-version
/var/lib/snappy/; fi (code=exited, status=1/FAILURE)
Main PID: 596 (code=exited, status=1/FAILURE)
Apr 08 08:33:04 autopkgtest systemd[1]: Starting Regenerate snappy security
policies...
Apr 08 08:33:04 autopkgtest sh[596]: + cmp
/usr/share/snappy/security-policy-version
/var/lib/snappy/security-policy-version
Apr 08 08:33:04 autopkgtest sh[596]: cmp:
/usr/share/snappy/security-policy-version: No such file or directory
Apr 08 08:33:04 autopkgtest sh[596]: + /usr/bin/snappy policygen
--regenerate-all
Apr 08 08:33:04 autopkgtest sh[596]: + cp
/usr/share/snappy/security-policy-version /var/lib/snappy/
Apr 08 08:33:04 autopkgtest sh[596]: cp: cannot stat
'/usr/share/snappy/security-policy-version': No such file or directory
Apr 08 08:33:04 autopkgtest systemd[1]: ubuntu-snappy.run-hooks.service: Main
process exited, code=exited, status=1/FAILURE
Apr 08 08:33:04 autopkgtest systemd[1]: Failed to start Regenerate snappy
security policies.
Apr 08 08:33:04 autopkgtest systemd[1]: ubuntu-snappy.run-hooks.service: Unit
entered failed state.
Apr 08 08:33:04 autopkgtest systemd[1]: ubuntu-snappy.run-hooks.service: Failed
with result 'exit-code'.
** Affects: snappy (Ubuntu)
Importance: Undecided
Assignee: Snappy Developers (snappy-dev)
Status: New
** Affects: snappy (Ubuntu Xenial)
Importance: Undecided
Assignee: Snappy Developers (snappy-dev)
Status: New
** Also affects: snappy (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: snappy (Ubuntu Xenial)
Assignee: (unassigned) => Snappy Developers (snappy-dev)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567780
Title:
Fails to start boot-ok and run-hooks services in a default install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snappy/+bug/1567780/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
