Public bug reported:
Hi all,
I'm writing to signal a very easy to fix potential problem to your puppet
package.
The package for the agent, as provided, does not permit to facts defined on the
master to be correctly deployed and used on the agent side.
To reproduce the error, for example, I coul
Hi, yes I know it is not needed to have a manifest file to propagate the fact
to the node.
In fact the facter gets propagated and is available on the node machine,
however whey I try to recall it from a manifest, the fact simply is not
evaluated.
I try to better describe the problem by answerin
Robie, yes the problem is exactly the one you described.
The puppet daemon does not source /var/lib/puppet/lib/facter for facts and my
proposed modification is a workaround to have it properly running.
Also the command "puppet agent --test" does not source the facts in
/var/lib/puppet/lib/facter
Robie, I tested it on Debian wheezy and the situation is exactly the same.
I will try and track the problem to signal it at the more appropriate level.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launc
On my linux box the fact is synched on the agent (with pluginsync=true
attribute) and the fact file is created in the folder
/var/lib/puppet/lib/facter (and not in
/etc/puppet/modules/modulewithfact/lib/facter/test_fact.rb as by your
example).
At this point the puppet daemon is not able to find th
Hi Matthaus,
I just re-executed the operations described. I work with master and agent on
two different machines.
On the agent machine the /etc/puppet/puppet.conf is as follows:
<<
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vard
