Debian: fact vmwaretools_version is not set
becker-IT opened this issue · comments
Hello,
i run Debian GNU/Linux 6.0 and the fact vmwaretools_version is not set.
But I even know where the ruby script which should set it is called?
Always puppet exec these:
info: Applying configuration version '1373969803'
notice: /Stage[main]/Vmwaretools::Config/File[/tmp/vmwaretools]/ensure: created
notice: /Stage[main]/Vmwaretools::Install::Archive/File[/tmp/vmwaretools/VMwareTools-8.3.17-784891.tar.gz]/ensure: defined content as '{md5}d5d09420adc02c99828f41e9fb7a6d63'
info: /Stage[main]/Vmwaretools::Install::Archive/File[/tmp/vmwaretools/VMwareTools-8.3.17-784891.tar.gz]: Scheduling refresh of Exec[uncompress_vmwaretools]
notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[uncompress_vmwaretools]: Triggered 'refresh' from 1 events
info: /Stage[main]/Vmwaretools::Install::Exec/Exec[uncompress_vmwaretools]: Scheduling refresh of Exec[install_vmwaretools]
notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[install_vmwaretools]: Triggered 'refresh' from 1 events
info: /Stage[main]/Vmwaretools::Install::Exec/Exec[install_vmwaretools]: Scheduling refresh of Exec[clean_vmwaretools]
notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[clean_vmwaretools]: Triggered 'refresh' from 1 events
info: /Stage[main]/Vmwaretools::Install::Exec/Exec[clean_vmwaretools]: Scheduling refresh of Exec[remove_vmwaretools_working_dir]
notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[remove_vmwaretools_working_dir]: Triggered 'refresh' from 1 events
notice: Finished catalog run in 99.50 seconds
Thanks
Björn
Hi Bjorn,
Can you post the output of facter on your Puppet node?
Thanks,
Craig
Can you also check you have pluginsync enabled (add pluginsync = true in the [main] section of your node's puppet.conf? You'll need pluginsync to be enabled for the custom fact to be synchronised across to your nodes.
Hi,
pluginsync wasn't set. Now he don't try to install vmwaretools again, but the fact seems to be not set anyway:
architecture => amd64
domain =>
facterversion => 1.5.7
fqdn =>
hardwareisa => unknown
hardwaremodel => x86_64
hostname =>
id => root
interfaces => eth0
is_virtual => true
kernel => Linux
kernelmajversion => 2.6
kernelrelease => 2.6.32-5-amd64
kernelversion => 2.6.32
lsbdistcodename => squeeze
lsbdistdescription => Debian GNU/Linux 6.0.7 (squeeze)
lsbdistid => Debian
lsbdistrelease => 6.0.7
lsbmajdistrelease => 6
macaddress => 00:50:56:b5:7f:02
macaddress_eth0 => 00:50:56:b5:7f:02
manufacturer => VMware, Inc.
memoryfree => 822.46 MB
memorysize => 1002.82 MB
netmask => 255.255.255.0
netmask_eth0 => 255.255.255.0
network_eth0 => 10.128.20.0
operatingsystem => Debian
operatingsystemrelease => 6.0.7
path => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
physicalprocessorcount => 0
processor0 => Intel(R) Xeon(R) CPU E5345 @ 2.33GHz
processorcount => 1
productname => VMware Virtual Platform
ps => ps -ef
puppetversion => 2.6.2
rubysitedir => /usr/local/lib/site_ruby/1.8
rubyversion => 1.8.7
selinux => false
serialnumber => VMware-42 35 4e d0 01 30 58 dd-ab af 51 aa c1 c2 61 68
swapfree => 1.52 GB
swapsize => 1.53 GB
timezone => CEST
type => Other
uniqueid => 007f0101
uptime => 20:05 hours
uptime_days => 0
uptime_hours => 20
uptime_seconds => 72336
virtual => vmware
My apologies, you'll need to run facter -p to see the Puppet facts in addition to facter's facts :)