Open fnoop opened 5 years ago
This still isn't fixed, it's because manifests/service.pp references:
service { 'collectd':
This then doesn't allow us to reference Service['collectd']
elsewhere:
Error: Evaluation Error: Error while evaluating a Resource Statement, Cannot alias Service[system-collectd] to ["collectd"] at (file: /srv/maverick/software/maverick/manifests/maverick-modules/maverick_analysis/manifests/collect.pp, line: 140); resource ["Service", "collectd"] already declared (file: /srv/maverick/software/maverick/manifests/puppet-modules/collectd/manifests/service.pp, line: 6) (file: /srv/maverick/software/maverick/manifests/maverick-modules/maverick_analysis/manifests/collect.pp, line: 140, column: 5) on node mvrk.org
If the code was changed to something like: service { 'managed_collectd':
, then it wouldn't clash.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
What behaviour did you expect instead
Not to have conflicting resource
Any additional information you'd like to impart
As per #688 and #771 , $collectd::service_name should be used instead of Service['collectd']. service.pp controls the service with a static name:
service { 'collectd':
This should be:service { $collectd::service_name:
PR to follow