Each repo and yumrepo should only be declared once.
Actual Behavior
When multiple other modules add a repo of the same name in their code, collisions occur on compilation.
Steps to Reproduce the Problem
Add multiple other modules to Puppetfile (creating custom modules would suffice) that defined the same resource - Yumrepo['epel'] as a example
Puppet will generate the following error on compilation:
Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate declaration: Yumrepo[epel] is already declared in file /etc/puppet/modules/epel/manifests/init.pp:90; cannot redeclare at /etc/puppet/modules/yum/manifests/managed_yumrepo.pp:80 on node
Specifications
Affects all versions and clients. (A PR has been opened on the epel module as well.)
Please add this info:
Output of facter -p on the failing node (at least the OS related facts)
Expected Behavior
Each repo and yumrepo should only be declared once.
Actual Behavior
When multiple other modules add a repo of the same name in their code, collisions occur on compilation.
Steps to Reproduce the Problem
Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate declaration: Yumrepo[epel] is already declared in file /etc/puppet/modules/epel/manifests/init.pp:90; cannot redeclare at /etc/puppet/modules/yum/manifests/managed_yumrepo.pp:80 on node
Specifications
Affects all versions and clients. (A PR has been opened on the epel module as well.)
Please add this info:
Output of
facter -p
on the failing node (at least the OS related facts)Version of Puppet and of the module
The relevant Puppet code and eventually Hiera data