cloud-init-dev team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

Scott Moser has proposed merging ~smoser/cloud-init:bug/1767131-snap-seeded into cloud-init:master.

Commit message:
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

Requested reviews:
  Dan Watkins (daniel-thewatkins)
  cloud-init commiters (cloud-init-dev)
Related bugs:
  Bug #1767131 in cloud-init (Ubuntu): "Pre-seeded snaps are not necessarily available for use in cloud-init user-data"
  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767131

For more details, see:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/345365

see commit message
-- 
Your team cloud-init commiters is requested to review the proposed merge of ~smoser/cloud-init:bug/1767131-snap-seeded into cloud-init:master.

diff --git a/systemd/cloud-config.service.tmpl b/systemd/cloud-config.service.tmpl
index bdee3ce..9d928ca 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]