When the Puppet agent want to upgrade the vmware tools in the background with the -d switch, I get this in the Puppet logs:
Notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[install_vmwaretools]/returns: The answer "" is invalid. It must be the complete name of a binary file.
Notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[install_vmwaretools]/returns:
Notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[install_vmwaretools]/returns: Use of uninitialized value $gOption{"default"} in numeric eq (==) at /tmp/vmwaretools/vmware-tools-distrib/vmware-install.pl line 2541.
Notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[install_vmwaretools]/returns: What is the location of the "lsmod" program on your
Notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[install_vmwaretools]/returns: machine? Use of uninitialized value $gOption{"default"} in numeric eq (==) at /tmp/vmwaretools/vmware-tools-distrib/vmware-install.pl line 866.
It seems lsmod is not in the PATH during the execution of the vmware-install.pl command.
On RHEL 6, this is in /sbin.
Can the "path" environment be updated so this works?
Hi
When the Puppet agent want to upgrade the vmware tools in the background with the -d switch, I get this in the Puppet logs:
It seems lsmod is not in the PATH during the execution of the vmware-install.pl command. On RHEL 6, this is in /sbin.
Can the "path" environment be updated so this works?
Thanks Filip Nollet