Description of problem: When creating a multi-tier application definition in a catalog bundle, it is not possible to select the same catalog item (e.g. RHEL7 template) multiple times. This forces to create multiple instance of the same catalog item. Version-Release number of selected component (if applicable): 5.6.1.2.20160810181333_8ba817b How reproducible: Always Steps to Reproduce: 1. Create a Service Item (e.g. RHEL7 provisioning) 2. Create a Service Bundle and add the Service Item previously created 3. Try to add a second instance of the service item in the bundle Actual results: The Service Item is not present in the list of service item which can be added to the Service Bundle because it is already in the bundle. Expected results: The service item should not be filtered out of the list. Additional info:
Is there any update on this bug?
Yes that's true , only one instance of catalog item can be added to a bundle.
I think this could be supported but there are underlying changes that would need to be made first. The current design assumes only one instance of any model would be connected to a service template. When adding or deleting those items only the connected item is passed. The issue is when removing a resource, if the same item is connected more than once, the code is not aware of which connection is being removed and in fact removes all the connections. This issue exists from both the UI and automate.
I think the requirement here is to be able to include the same Service item multiple times in a Service bundle since the Service dialog values can alter the items functionality.
(In reply to Tina Fitzgerald from comment #9) > I think the requirement here is to be able to include the same Service item > multiple times in a Service bundle since the Service dialog values can alter > the items functionality. correct