Closed eyemyth closed 9 years ago
Er, nevermind. I ran puppet agent -t
on the master and now it works.
You have a mac_battery_charge_percent fact? Nice.
Yeah, the real reason this happens is because of a problem with Puppet plugin sync -- not a managedmac issue per se, but one that affects the distribution of custom types/providers (which managedmac relies on (heavily)).
Yep, mac_battery_charge_percent comes from https://github.com/grahamgilbert/grahamgilbert-mac_facts
I am going to raid Mr. Gilbert's repo some day. Uh, pardon?
Similar to https://github.com/dayglojesus/managedmac/issues/40
I'm just getting into puppet and have my master and a test client set up. I've added and used other modules with no issue. I installed and included managedmac in the node definition of my test node, and when I run
puppet agent -t
on the test node, I get:I'm running puppet 3.7.4 and facter 2.4.0 on both master and the test node.
gem list
reports CFPropertyList v 2.2.0 and sqlite3 1.3.7 on the client. I setpluginsync = true
under[agent]
in puppet.conf on both client and server. The client has stock Ruby:ruby -V
reportsruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin13]
,facter rubyversion
reports2.0.0
, andfacter rubysitedir
reports/Library/Ruby/Site/2.0.0