search

canonical / core18

The core18 base snap
14 stars 26 forks source link

hooks: add hook to ensure cloud-config runs in the right order #97

Closed mvo5 closed 5 years ago

mvo5 commented 5 years ago

On a core18 system on a first boot we do not have a "snapd.seeded.service" because we only boot from a pristine core18 snap which does not include any snapd units. The snapd.seeded unit gets created during the seeding.

This means that systemd will ignore the "After=snapd.seeding" on bootup in cloud-config because at this point it does not know about the unit and when it gets added it will (AFAIK) not re-eval the dependency chain.

To ensure that cloud-config does not start too early we add a sync point with core18.start-snapd.service which is part of the core18 snap and which will block until the system is fully seeded.

mvo5 commented 5 years ago

We decided to add snapd.seeded.service to core18 so this PR is obsolete.