You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: 5.1.3
Ruby: 2.4.1p111
Distribution: Debian 8
Module version: 7.0.0
How to reproduce (e.g Puppet code you use)
class { '::splunk::params':
version => $version,
build => $build,
src_root => $src_root,
}
include ::splunk::forwarder
puppet agent -t
What are you seeing
Error 500 on agent
What behaviour did you expect instead
Forwarder installed.
Output log
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'purge_forwarder_deploymentclient' at /etc/puppetlabs/code/environments/master/modules/splunk/manifests/params.pp:258 on Splunk_config[splunk] at /etc/puppetlabs/code/environments/master/modules/splunk/manifests/params.pp:258 on node XXX
Any additional information you'd like to impart
I have been using puppet-splunk version 5.1.0 so far.
After upgrading to version 7.0.0 I get following error and can't install forwarder any more.
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
puppet agent -t
What are you seeing
Error 500 on agent
What behaviour did you expect instead
Forwarder installed.
Output log
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'purge_forwarder_deploymentclient' at /etc/puppetlabs/code/environments/master/modules/splunk/manifests/params.pp:258 on Splunk_config[splunk] at /etc/puppetlabs/code/environments/master/modules/splunk/manifests/params.pp:258 on node XXX
Any additional information you'd like to impart
I have been using puppet-splunk version 5.1.0 so far.
After upgrading to version 7.0.0 I get following error and can't install forwarder any more.
The text was updated successfully, but these errors were encountered: