I dont think I really agree with this fix.

Adding 'After=local-fs.target' essentially pushes cloud-init to have that same 
dependency, which it does not have.  We don't really want cloud-init to have to 
wait for local-fs.target.
For example see bug 1691489 (and related fallout bug 1717477).


If the only reason for local-fs.target was actually PrivateTmp, then there is a 
bug in systemd.

https://www.freedesktop.org/software/systemd/man/systemd.exec.html
 | Implicit Dependencies
 | Similar, units with PrivateTmp= enabled automatically get mount unit
 | dependencies for all mounts required to access /tmp and /var/tmp. They
 | will also gain an automatic After= dependency on systemd-tmpfiles-
 | setup.service(8).
 
 So there must have been a different read-only filesystem involved.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750780

Title:
  Race with local file systems can make open-vm-tools fail to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to