I didn't know there was such a difference between exporting the ensure and
setting it when collecting, I thought it was supposed to be the same thing
...
Anyways, I fixed this but I still see the error happening from time to
time, got a few of those this morning:
Oct 30 07:34:16 ubuntu puppet-master[10501]: Exported resource Host[proxy4]
cannot override local resource on node lb2
Oct 30 07:34:16 ubuntu puppet-master[10501]: Exported resource Host[proxy4]
cannot override local resource on node lb2
Oct 30 07:34:17 ubuntu puppet-master[10337]: Exported resource Host[proxy4]
cannot override local resource on node lb5
Oct 30 07:34:17 ubuntu puppet-master[10337]: Exported resource Host[proxy4]
cannot override local resource on node lb5
Oct 30 07:34:19 ubuntu puppet-master[10337]: Exported resource Host[proxy4]
cannot override local resource on node lb3back
This is the new manifest:
proxy* servers:
@@host { "$hostname":
comment => "$hostname",
ip => "$ec2_local_ipv4",
name => "stable_host$proxy_id",
tag => "production-proxy",
ensure => present,
}
lb* servers:
Host <<| tag == "production-proxy" |>> {
}
Host <<| tag =="backup-proxy" |>> {
}
Still no idea why this is happening. I have some hosts that sometime change
their IP address and I have to sync this with the other servers. Is it
possible that the cause is that there is already a host record in the
/etc/hosts file that has another IP address in it? (Although I'd assume
puppet should just change it and not take it as a local resource...)
I'd appreciate the help, quite desperate about this...
Thanks!
On Thu, Oct 27, 2011 at 3:10 PM, jcbollinger <[email protected]>wrote:
>
>
> On Oct 27, 2:23 am, Galed Friedmann <[email protected]> wrote:
> > Hmm..
> > I'm not setting up local Host resources any where in the manifests, my
> nodes
> > only collect the exported resources.
> >
> > Almost all of my nodes are exporting their Host resource, and I have
> several
> > hosts that collect the resource according to their tag name:
> >
> > Host <<| tag == "production-proxy" |>> {
> > ensure => present,
> > }
> >
> > Host <<| tag =="backup-proxy" |>> {
> > ensure => present,
> > }
> >
> > This also happens to me for an Opsviewmonitored resource I'm exporting,
> > which is being collected only by one server that has no local resources
> like
> > this set..
>
>
> Then perhaps you're collecting the same resource twice. I wouldn't
> normally expect that to be a problem, but when you add property
> overrides to the mix then that could change things. Even if the
> overrides match. That also ties in even closer to the error messages,
> which mention overriding.
>
> Why do you need to override 'ensure' anyway? Can't you just export it
> with that 'ensure' value in the first place?
>
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
