Issue #2112 has been updated by egerlach.

Note to self while trying to find this:

Initial git bisect said it could be in any of:
commit:5bef4a55b3489a6404ee34b900621af8b784749a
commit:3cc3e0f5b21deee4fbdbcbae18fba47c7a0cbb1e
commit:488c43771aea482e0212b605bde054bf8cb0533c
commit:cfda651f88d12249f29706d2bedbfddce7a2e6f7
commit:fe9b453650755e66e29eca259075e2e7245a5219
commit:4165edaeb71ee2883b1bb85ff39a52d5628b259f
commit:b7b11bd4858a4d6dd0661aa7c546d03b4a85ca7d
commit:88dc49cb7b0efe757c92ce28c807b91335acb07a

But... I'm not sure I bisected well.  It was hard because it didn't error out 
the same way... will continue this tomorrow.
----------------------------------------
Bug #2112: Puppet fails with "Duplicate Definition" on any ParsedFile type when 
using "resources { purge => true }"
http://projects.reductivelabs.com/issues/2112

Author: egerlach
Status: Unreviewed
Priority: Normal
Assigned to: 
Category: 
Target version: 
Complexity: Unknown
Affected version: 0.25.0
Keywords: 


If you use @resources { type: purge => true }@ on a type which uses a 
ParsedFile provider, and the entry is already in the default target file, 
puppet fails with (e.g.): 

<pre>
err: Could not apply complete catalog: Duplicate definition: 
Firehol[eth0-http-server] is already defined in file 
/home/egerlach-/tmp/test.pp at line 15
</pre>

Attached are a type, provider, and test case which trigger this bug.  Run the 
test case twice to trigger (once to create the file, once to trigger).  It's 
not confined to this type, though.  You can also use the test case in #2111, 
but doing so will also trigger the infinite recursion bug (I found #2111 when 
trying to create a simple test for this).


----------------------------------------
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://reductivelabs.com/redmine/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
-~----------~----~----~----~------~----~------~--~---

Reply via email to