Justin,
What would the syntax be along those lines when looking up custom facts?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/BB3TAoW6PVEJ.
To post to
OK, I think this is probably something that is entirely my fault, but I
cannot access a facter fact that I need. It evaluates only on certain
clients, and is dependent upon the creation and value of another fact.
Client and server are puppet 2.6.6 and facter 1.5.9.
Custom fact defined in
Nan, that's exactly what I thought. I posted another thread with more
details on the issue I'm seeing though, so I won't go into my issues here.
On Friday, July 15, 2011 1:42:23 PM UTC-4, Nan Liu wrote:
Facts are top scope, so simply ::factname such as
scope.lookupvar('::operatingsystem')
Well, whatever problem I'm seeing is due to the nested Facter.add
statements...when I pulled the ldap_rid one out and ran it separately, it
worked.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
I have it working, but I'm curious if this might be a bug with nested
Facter.add statements?
I simply un-nested them and used a 'confine' statement to make things work.
New facts posted below:
Facter.add(is_ldap_server) do
setcode do
if FileTest.exists?(/usr/sbin/slapd)
%x{echo
Hey all...new to puppet, but desperately pushing it on everyone I see
around me :)...
I'm running into a relatively minor issue that keeps puppet from
properly completing its first run. Subsequent runs do not have these
issues, and I'm confused why. It appears to be looking for a different
repo's
