diff options
| author | Scott Moser <smoser@ubuntu.com> | 2014-09-11 10:50:04 -0400 |
|---|---|---|
| committer | Scott Moser <smoser@ubuntu.com> | 2014-09-11 10:50:04 -0400 |
| commit | 26c1cf9eeeb39e9bfcc1a37743679e5c76ab97b0 (patch) | |
| tree | 87a96028c4cc1bb6a00cfc97de83a4ec7fd06b72 | |
| parent | 2755274f34ef11651a5ee57a31955f3e413cdfc4 (diff) | |
| download | vyos-cloud-init-26c1cf9eeeb39e9bfcc1a37743679e5c76ab97b0.tar.gz vyos-cloud-init-26c1cf9eeeb39e9bfcc1a37743679e5c76ab97b0.zip | |
cloud-init-local depends on /run. reflect that in upstart job.
With the writing of cloud-init status, cloud-init-local needs to
have /run mounted. The issue we were seeing was a race where:
cloud-init-local creates /run/cloud-init
/run is mounted
cloud-init-local tries to link a file into /run/cloud-init
that directory was no longer visisable as /run was mounted over
the top.
LP: #1353008
| -rw-r--r-- | upstart/cloud-init-local.conf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/upstart/cloud-init-local.conf b/upstart/cloud-init-local.conf index 061fe406..713b36d9 100644 --- a/upstart/cloud-init-local.conf +++ b/upstart/cloud-init-local.conf @@ -1,6 +1,6 @@ # cloud-init - the initial cloud-init job # crawls metadata service, emits cloud-config -start on mounted MOUNTPOINT=/ +start on mounted MOUNTPOINT=/ and mounted MOUNTPOINT=/run task |