Hi Matt,
Thats a bit odd, when using external nodes you shouldn't need any node
definitions within your manifests.
any chance you have some leftover nodes definitions?
Ohad
On Mon, Sep 28, 2009 at 5:52 PM, Matt wrote:
>
> Update:-
>
> I added a default node to a manifest file, just -
>
> node
Matt schrieb:
> Hi all,
>
> I've hit a wall trying to get external nodes working on our production
> puppet master. I'm using the foreman to supply the external nodes
> information and have it all working in the dev environment.
>
> manually -
> # su - puppet
> -bash-3.2$ cd /etc/puppet
> -bash-
You're right, I removed all /var/lib/puppet/* from the client except
the ssl directory and the next poll worked.
Still requires me to have a default node though on the puppetmaster.
Should the client really cache bad catalogs?
2009/9/28 Nicolas Szalay :
> Le lundi 28 septembre 2009 à 10:52 +010
Le lundi 28 septembre 2009 à 10:52 +0100, Matt a écrit :
> Update:-
>
> I added a default node to a manifest file, just -
>
> node default {
> include env
> }
>
> This appears to have made the puppetmasterd kick in to action and
> compile the catalog from the foreman for that node. i.e. I se
Update:-
I added a default node to a manifest file, just -
node default {
include env
}
This appears to have made the puppetmasterd kick in to action and
compile the catalog from the foreman for that node. i.e. I see
puppetmasterd compile all the correct classes for the node and not
just th
