ds=nocloud-net & cloud-init-local.conf breaks system init
Bug #1380948 reported by
Marc Riemer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
After upgrading cloud-init to 0.7.5 the init process is broken. The VM was previously configured via cloud-init.
CMDLINE:
ds=nocloud-net;s=http://
Changing cloud-init-
- start on mounted MOUNTPOINT=/ and mounted MOUNTPOINT=/run
+ start on mounted MOUNTPOINT=/
affects: | cloud-init → cloud-init (Ubuntu) |
To post a comment you must log in.
I found a solution, which will solve this and a previous bug (no /run mounted).
I guess the problem is, the event "mouted / and mounted /run" will never be triggered at the same time. As a result cloud-init-local will not be stopped at all and cloud-init-nonet wait until cloud-init-local has been stopped, what will never happen.
Using the event "mounted MOUNTPOINT=/run TYPE=tmpfs" makes sure / and also /run was mounted when cloud-init-local start the cloud-init local process.