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 answering your questions and adding some informations. Following your procedure: 1: already done 2: done 3: yes the fact is properly transmitted 4: I can correctly see the fact running "facter --puppet" on the node I am using: Ubuntu 12.04.1 LTS puppet 2.7.11-ubuntu2.1 facter 1.6.5-1ubuntu2.1 However, for the use I would like to achieve with puppet, the fact the the command facter --puppet works correctly is not satisfactory. In fact I would like the node to synchronize with the agent using the puppet daemon launched with service puppet start. In this case the facter on the node do not gets evaluated correctly. To solve this problem I found that putting a value for the FACTERLIB including the folder where the facts are deployed from the master to the nodes, I would solve the error. So I added this directive in the /etc/default/puppet file which is sourced in the /etc/init.d/puppet init script. I hope you could test and reproduce the problem, using the fact from a manifest. If you then have a better and more "clean" solution (instead of the one I proposed) I will be glad to accept it. For the moment on my servers I will leave my modification which is working correctly and without evident problems. Thanks, A. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076286 Title: Puppet agent not correcly configuring facts synch'd from master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1076286/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
