There is a difference between cloud-init sometimes running after local-
fs.target and being guaranteed to run after local-fs.target. The change
here guarantees it.
For the moment, this isn't too bad, as cloud-init can't really affect
local-fs.target because it isn't guaranteed to run before. But I
suspect we will change that at some point, which would cause a
Could someone that can recreate this actually collect *all* output of
systemctl status open-vm-tools
or even more ideally, modifying the job to 'strace -o -ff /run/open-vm-tools.'
and then collecting the /run/open-vm-tools files
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Race with local file systems can make open-vm-tools fail to start
To manage notifications about this bug go to:
ubuntu-bugs mailing list