Bug 4171

Summary:	Plan splitter produces duplicate items in child plans
Product:	DAnCE	Reporter:	Will Otte <wotte>
Component:	LocalityManager	Assignee:	DOC Center Support List (internal) <tao-support>
Status:	NEW ---
Severity:	normal
Priority:	P3
Version:	1.2.7
Hardware:	All
OS:	All

Description Will Otte 2014-07-08 07:14:08 CDT

Given the following plan (this is grossly simplified, but the notation is [type of element:id of element:references other element](Node if appropriate)

[implementation:A1:C1]
[implementation:A2:C2]
[instance:B1:A1](Node1)
[instance:B2:A1](Node2)
[instance:B3:A2](Node1)
[instance:B4:A2](Node2)
[instance:B5:A1](Node1)
[instance:B6:A2](Node2)
[instance:B7:A2](Node1)
[instance:B8:A1](Node2)
[artifact:C1]
[artifact:C2]

will produce child plans that look something like this:

Node 1:
[implementation:A1:C1]
[implementation:A2:C2]
[implementation:A1:C1]
[implementation:A2:C2]
[instance:B1:A1](Node1)
[instance:B3:A2](Node1)
[instance:B5:A1](Node1)
[instance:B7:A2](Node1)
[artifact:C1]
[artifact:C2]
[artifact:C1]
[artifact:C2]

(The node 2 plan is similar).  

Note the duplicate implementation and artifact elements.  This bug was observed in the F6 fork of DAnCE, but I believe it to be present in the mainline code, as we haven't modified the split plan code. 

This bug does not produce run-time failures, due to the way that we process the plans at the node and locality level, but it can be observed in the log messages produced by the artifact installation handlers at the node level.