Issue #6823 has been updated by John Crenshaw.

Hmm, that's the darndest thing. I just fought with this for a solid 6 hours, 
and now I can't make it happen anymore. Blast. I DID change a couple of things 
in the mean time:
1. I removed a node classifier (the whole point of the facter was to replace 
the node classifier). Putting the classifier back doesn't seem to cause the 
problem to return.
2. I didn't remove the working (symlinked) facter to rerun the test. The facter 
that now mysteriously works is located in the same directory as the symlinked 
one (but is not loaded with `facter --puppet` so I think this is probably not 
the trigger either).
3. I uninstalled puppetmaster (not needed for standalone.) Perhaps this did 
something to a cache? Reinstalling didn't cause the problem to return.
4. I uninstalled pcregrep (I no longer needed it, but I can't imagine this is 
related)
5. I ran once with --trace and --verbose.

That's the full list of everything I can think of that changed between the time 
that this didn't work, and now.
----------------------------------------
Bug #6823: Facts from plugins not working with standalone
https://projects.puppetlabs.com/issues/6823

Author: John Crenshaw
Status: Needs More Information
Priority: Normal
Assignee: 
Category: 
Target version: 
Affected Puppet version: 2.6.2
Keywords: 
Branch: 


1. Create a simple facter and place it in a module plugin:
`Facter.add("foobar") { setcode { "foobar" } }`
2. Add a line to dump the contents of foobar:
`notice("test: $foobar")`
3. Run puppet standalone:
`sudo puppet apply --noop --debug /etc/puppet/manifests/site.pp`
4. Output will indicate that the custom facts were loaded, but will also show 
an empty foobar

I was able to work around the issue by adding a symlink in 
/usr/lib/ruby/1.8/facter/ pointing to the file from the plugin. With the 
symlink in place, the foobar fact is available and the notice prints the 
expected value. I'm wondering if something about the plugin sync isn't fully 
working for standalone?


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to