Puppet users - Nov 2011 - Weird opsviewmonitored module behavior

Hi all,
I wonder if any of you ever encountered this weird issue.

I''m using Opsviewmonitored module to manage my servers inside opsview, 
exporting the resource to a central server and making sure all of the 
available servers are monitored and exist in opsview.
I have around 30 servers that are being managed by opsview just fine, but 
there is a specific group of servers which keeps disappearing from puppet 
as a managed resource, causing puppet to constantly try to apply the 
resource and reloading my opsview server endlessly.

Here is an example of what happens:
# puppet apply -e "opsviewmonitored { ''proxy3'': ensure
=> present,
reloadopsview => true, hostgroup => ''Proxy Servers'', 
hosttemplates =>
[''Proxy Server''], ip => ''proxy3'' }"
notice: /Stage[main]//Opsviewmonitored[proxy3]/hostgroup: defined 
''hostgroup'' as ''Proxy Servers''
notice: /Stage[main]//Opsviewmonitored[proxy3]/ip: defined
''ip'' as ''proxy3''
notice: /Stage[main]//Opsviewmonitored[proxy3]/hosttemplates: defined 
''hosttemplates'' as ''Proxy Server''
notice: Finished catalog run in 14.96 seconds

# puppet resource opsviewmonitored proxy3
opsviewmonitored { ''proxy3'':
  ensure => ''present'',
}

I see that specific server being created in opsview so the module is 
working just fine, but for some reason it disappears as a managed 
resource... I have many other servers that are working just fine, for some 
reason this happens only for servers in this specific group (and not all of 
them, there are other servers in that group that I do see using puppet 
resource..)

Has anybody ever dealt with an issue like this before?

Thanks alot!
Galed.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/G-bZjevC09sJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

> I''m using Opsviewmonitored module to manage my servers inside
opsview, > exporting the resource to a central server and making sure all of
the > available servers are monitored and exist in opsview.
> I have around 30 servers that are being managed by opsview just fine, but
> there is a specific group of servers which keeps disappearing from puppet
> as a managed resource, causing puppet to constantly try to apply the
> resource and reloading my opsview server endlessly.
This module is pretty basic, and doesn''t do any error checking after
sending the config to Opsview.  If you specify a non-existant
hostemplate or hostgroup, then the resources will appear to be applied
by puppet, but they won''t actually be written to Opsview.  As a result
you''ll end up seeing the resources get applied on every puppet run.

> # puppet resource opsviewmonitored proxy3
> opsviewmonitored { ''proxy3'':
>   ensure => ''present'',
>
> }
I would expect the output of "puppet resource" to list the hostgroup,
ip, and hostemplates parameters for this node if they exist.  In this
case they''re blank, so it''s probably not setup properly.

So, is the ''proxy3'' host actually present in Opsview, with the
proper
settings?  I''d double check to make sure that the hosttemplate and
hostgroup you''re specifying are actually setup.


Btw - you might want to check out a fork of the opsview module, which
allows you to manage a whole lot more than just nodes (hostgroups,
servicechecks, contacts, etc):
http://forge.puppetlabs.com/cparedes/puppet_opsview

-devon

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi,
Thanks for trying to help.

I agree with that you wrote, the weird thing that I mentioned in my
previous mail was that indeed the ''proxy3'' server appears in
opsview. Also
to add to this mess there are other proxy servers that use the same
opsviewmonitored manifest that appear in opsview and in puppet resource,
this happens occasionally for some but not all of the servers.

I found out that deleting the servers entirely from opsview and letting
puppet create them again solves this for some time, but after a while it
enters that loop again, sometimes with the same servers and sometimes with
others...

Any ideas?

Thanks again!

On Mon, Nov 7, 2011 at 9:04 PM, devon <devon.peters@gmail.com> wrote:
> > I''m using Opsviewmonitored module to manage my servers inside
opsview, >
> exporting the resource to a central server and making sure all of the >
> available servers are monitored and exist in opsview.
> > I have around 30 servers that are being managed by opsview just fine,
but
> > there is a specific group of servers which keeps disappearing from
puppet
> > as a managed resource, causing puppet to constantly try to apply the
> > resource and reloading my opsview server endlessly.
>
> This module is pretty basic, and doesn''t do any error checking
after
> sending the config to Opsview.  If you specify a non-existant
> hostemplate or hostgroup, then the resources will appear to be applied
> by puppet, but they won''t actually be written to Opsview.  As a
result
> you''ll end up seeing the resources get applied on every puppet
run.
>
>
> > # puppet resource opsviewmonitored proxy3
> > opsviewmonitored { ''proxy3'':
> >   ensure => ''present'',
> >
> > }
>
> I would expect the output of "puppet resource" to list the
hostgroup,
> ip, and hostemplates parameters for this node if they exist.  In this
> case they''re blank, so it''s probably not setup properly.
>
> So, is the ''proxy3'' host actually present in Opsview,
with the proper
> settings?  I''d double check to make sure that the hosttemplate and
> hostgroup you''re specifying are actually setup.
>
>
> Btw - you might want to check out a fork of the opsview module, which
> allows you to manage a whole lot more than just nodes (hostgroups,
> servicechecks, contacts, etc):
> http://forge.puppetlabs.com/cparedes/puppet_opsview
>
> -devon
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> 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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.