On 03/17/2018 09:12 AM, Patrick Matthäi wrote:
> Hi,
>
> Then the dependency still needs to get fixed in VMware Tools.
which won't help you as that systemd version is not in jessie and stretch.
(just fyi: bug reports to backports versions have to go on the backports
user list, not into the
> Why does it need to run before cloud-init i.e. why does cloud-init need
> open-vm-tools?
because cloud-init pulls the configuration it should apply from vmtoolsd.
But that is not the bug here and nothing that needs to be changed.
If you would finally read
Am 10.03.2018 um 01:39 schrieb Bernd Zeimetz:
> Hi,
>
> because it needs to run before cloud-init.
Why does it need to run before cloud-init i.e. why does cloud-init need
open-vm-tools?
Feel free to point me to the relevant parts of the bug report which
explain that.
--
Why is it that all of
Hi,
because it needs to run before cloud-init. Please read free Ubuntu bug I've
linked, most details are discussed there.
Thanks,
Bernd
Am 10. März 2018 00:22:32 MEZ schrieb Michael Biebl :
>On Fri, 2 Feb 2018 09:31:28 +0100 =?UTF-8?Q?Patrick_Matth=c3=a4i?= >
>for
>the
On Fri, 2 Feb 2018 09:31:28 +0100 =?UTF-8?Q?Patrick_Matth=c3=a4i?= > for
the public:
> systemd does not start open-vm-tools at all in this scenario. If you
> configure open-vm-tools.service to use DefaultDependencies=yes instead
> of =no, it works as a workaround.
Why does open-vm-tools.service
On Wed, 31 Jan 2018 16:06:16 +0100 =?UTF-8?Q?Patrick_Matth=c3=a4i?=
wrote:
> Package: open-vm-tools
> Version: 2:10.2.0-2
> Severity: important
>
> Dear Maintainer,
>
> here all systems on vSphere 6.0/6.5 fail to start open-vm-tools.service
> on boot.
> The only thing I