Issue #5037 has been reported by Martha Greenberg.
----------------------------------------
Bug #5037: Duplicate definition when a class is included from ldap both
directly and via an include
https://projects.puppetlabs.com/issues/5037
Author: Martha Greenberg
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version: 2.6.1
Keywords:
Branch:
We use LDAP external nodes. In 2.6.1, if a class is directly included via LDAP
and then also included via a second class, you get errors about duplicate
definitions for all the objects in that class.
Both client and server are Debian Lenny, using the 2.6.1 packages from
experimental.
To replicate:
1) Add the following classes via LDAP:
puppetclass: test::one
puppetclass: test::two
2) Create some test classes like these:
puppet:~# cat /etc/puppet/dev_martha/modules/test/manifests/one.pp
class test::one {
include test::two
}
puppet:~# cat /etc/puppet/dev_martha/modules/test/manifests/two.pp
class test::two {
file {"/tmp/foo":
owner => root,
group => root,
mode => 644,
content => "bar\n",
}
}
3) Run puppet agent on test node:
debiantest:~# puppetd -t
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Duplicate definition: File[/tmp/foo] is already defined in file
/etc/puppet/dev_martha/modules/test/manifests/two.pp at line 7; cannot redefine
at /etc/puppet/dev_martha/modules/test/manifests/two.pp:7 on node
debiantest.example.com
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.