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
Andrea,
Can you post the output of your puppet run using `puppet agent -t --trace
--debug` on the agent? That might help figure out what's going on.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
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
Andrea,
The first example was master and agent on the same machine, so it found the
module in the modulepath without pluginsync. The second example was agent and
master on different machines.
Can you post the output of your puppet.conf and `puppet agent -t --trace
--debug` on the agent? That
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.
I wasn't able to reproduce this on precise. I used the following
manifest to test the fact:
node default {
file { '/tmp/puppettest':
ensure = present,
content = $test_fact,
}
}
I had just the fact example you used in
(/etc/puppet/modules/modulewithfact/lib/facter/test_fact.rb)...
And running it from a remote agent had the correct content as well once
pluginsync=true was added to the agent's puppet.conf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1076286
Matthaus,
Thanks for trying. Did you use a puppetmaster in your test our was it
local only? I get the impression that it won't reproduce unless it is
the former.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
So if the problem is that custom facts don't get to agents by default
after installing the puppet package, a solution could be to add
pluginsync=true to the puppet.conf in the package, but that might be
surprising to users, depending on what behavior they expect.
Side note: pluginsync defaults to
Robie,
I used a puppetmaster in both cases. In the first example the agent and master
were on the same sytem, in the second they were on seperate systems.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
Puppet sources additional directories for facts, (hence facter -p).
If I understand this report correctly, it sounds to me that the problem
is that puppet is not sourcing /var/lib/puppet/lib/facter for facts,
which is where factsync is writing them. Setting FACTERLIB in
/etc/default/puppet is a
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
Thanks Andrea.
I'm not sure about fixing /etc/default/puppet in Ubuntu as in my
judgement changing puppet agent --test to behave differently from the
daemon would be worse for users. For the time being, users can find this
bug and the associated workaround.
For a proper fix, the next step is to
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
If I understand this report correctly, you're getting the exact
experience as designed.
Puppet sources additional directories for facts, (hence facter -p).
If you want standalone facter to source more directories you will always
have to modify FACTERLIB. Where/how you choose to do that is up to
15 matches
Mail list logo
