The zabbix_host custom type doesn't appear to recognise the "group" parameter

[Sher-Chowdhury]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 2016.1.1
• Distribution: Cento 7 master, and centos 6 agent
• Module version: 2.5.0

How to reproduce (e.g Puppet code you use)

I created the following custom type:

@@zabbix_host { $zabbix_hostname:
  ensure    => 'present',
  group     => 'test',
  templates => hiera_array('xxx::zabbix_profile'),
  tag       => ['zabbix3', 'zabbix_server_url'],
}

The parameters I used here (in particular 'group') are based on the instructions here:

https://forge.puppet.com/puppet/zabbix/types

Then when I perform a puppet run I get the following error message:

[root@zabbixagent ~]# puppet agent -t
Warning: Setting 'pluginsync' is deprecated.
   (at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/defaults.rb:1607:in `block in <module:Puppet>')
Info: Using configured environment 'feature_dev'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: no parameter named 'group' at /etc/puppetlabs/code/environments/feature_dev/site/profile/manifests/zabbix/agent.pp:21 on Zabbix_host[zabbixagent.local] at /etc/puppetlabs/code/environments/feature_dev/site/profile/manifests/zabbix/agent.pp:21 on node zabbixagent.local
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Does any one have any idea why this is?

[Sher-Chowdhury]

I think I have found the problem. In the other directory environments we are using another zabbix module:

https://forge.puppet.com/fiddyspence/zabbix

This modules happens to have custom types of the same name. This is causing conflicts beteen this module and the fiddyspence module, since custom types are treated at the machine level rather than at the directory environment.

This problem is a limitation of puppet itself, and to a small extent defeats the point of using things like control repos and r10k.

As far as I can see, the only way round this is to build a new puppetmaster and continue my work there, or remove the old zabbix modules from the Puppetfile of all the control repo branches. Neither is this option is particularly appealing though.