Closed Tuxdiver closed 9 years ago
Hi,
You will need to pass the force_install
parameter to true
when using the module - I do plan to make this automatic based on the osfamily and version of VMware, but as always time is my enemy!
Can you let me know if this fixes your problem?
Thanks, Craig
Hi, yes, force_install did help and did uninstall the open-vm-tools and install the original one. Thanks for the quick fix!
Question: if VMware recommends the open-vm-tools, shouldn't your module detect the distributions for that and use the open-vm-tools instead of the other one? Maybe support for open-vm is better in some distributions than the tools from VMware?
Thanks for confirming - ultimately I think the module is doing it's job, I originally wrote it to install the VMware Tools from tarball as the vSphere console still classes the open-vm-tools as "third party".
After reading the linked VMware KB article, I'm unsure if any of the benefits are still "benefits" if you're using Puppet to install the "official" Tools (either from tar or OSP), it seems that VMware are recommending installing open-vm-tools
for convenience.
In my last installation, vmwaretools are not installed because the installer returns:
so installation stops here an starts at next puppet run again.
VMware-Tools: VMwareTools-9.4.11-2400950.tar.gz Distro: Ubuntu Trusty