I have added a simple notify check into our manifest for the offending
fact. If the value is set to expected it print a message into the
puppet log, however the nodes that aren't storing this fact in
database also are processing this conditional in the manifest as
expected.
Further more i have run
We have many modules and many nodes, every node may use different module, so
it's very unpleasant to modify the nodes.pp
Then i saw the external node, but seems it only support class and we have
many defines called in node.pp
So here is my question: Is there another way for us to manage so many no
Well, it would help if you can find out if the problem is with storeconfigs
of the rest of puppet. Does the fact seem to be affecting the manifest?
On Sun, Jun 19, 2011 at 7:48 PM, josbal wrote:
> Hi Guys,
>
> Was wondering if someone could point me in a way to diagnose my issue.
>
> I have a c
Hi Guys,
Was wondering if someone could point me in a way to diagnose my issue.
I have a custom fact that i deployed on all my nodes. If i run the
fact manually i get results as expected. When puppet runs only 5 or so
nodes are storing this particular fact in the storeconfig mysql
database. All o
hi,
no, it use facts architecture in facter and not the lsb_release facts
architecture => i386
we have debian and redhat nodes, no ubuntu, but i think it's the same result
2011/6/15 Nathan Clemons
> Do you have any machines which show the 32-bit machines as i686? I know at
> least 32-bit Ubu
On Sat, Jun 18, 2011 at 6:24 PM, d0ugb wrote:
> Need some help here. I am using puppet to mange some Gentoo boxes, and
> when working with packages I keep getting the following error:
>
> Could not find a default provider for package
>
> Version:
>
> * app-admin/puppet
> Latest version avai
