summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2018-05-14 15:38:22 -0400
committerScott Moser <smoser@brickies.net>2018-05-14 15:38:22 -0400
commitd5374bba2f1b4607a773ebff00e1ee7d66e23033 (patch)
treee554ab96c6a6aeb35fa579a5236a424902645504
parent3b712fcea9ca685c5cb761ea19c5126acf8ffaa1 (diff)
downloadvyos-cloud-init-d5374bba2f1b4607a773ebff00e1ee7d66e23033.tar.gz
vyos-cloud-init-d5374bba2f1b4607a773ebff00e1ee7d66e23033.zip
cloud-config.service: run After snap.seeded.service.
This makes cloud-config.service (and as a result cloud-final.service) run After snap.seeded.service. This is required to ensure that pre-seeded snaps can be used by cloud-init or user-data input. The snap.seeded.service was added to snapd at:   https://github.com/snapcore/snapd/pull/5124 Note that the following would be a workaround:  snap:   commands:    00: snap wait system seed.loaded LP: #1767131
-rw-r--r--systemd/cloud-config.service.tmpl1
1 files changed, 1 insertions, 0 deletions
diff --git a/systemd/cloud-config.service.tmpl b/systemd/cloud-config.service.tmpl
index bdee3ce0..9d928ca2 100644
--- a/systemd/cloud-config.service.tmpl
+++ b/systemd/cloud-config.service.tmpl
@@ -2,6 +2,7 @@
[Unit]
Description=Apply the settings specified in cloud-config
After=network-online.target cloud-config.target
+After=snapd.seeded.service
Wants=network-online.target cloud-config.target
[Service]