Bug 1372150

Summary: [RFE] Catalog Bundles cannot use more than one instance of a Catalog Item
Product: Red Hat CloudForms Management Engine Reporter: Jerome Marc <jmarc>
Component: AutomateAssignee: John Hardy <jhardy>
Status: CLOSED CURRENTRELEASE QA Contact: Shveta <sshveta>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: fdewaley, gmccullo, greartes, hkataria, jhardy, jocarter, kmorey, mkanoor, mpovolny, ngupta, obarenbo, tfitzger
Target Milestone: GAKeywords: FutureFeature, Reopened
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: service
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-19 14:51:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jerome Marc 2016-09-01 03:53:18 UTC 
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:
Comment 2 Nikhil Gupta 2016-09-09 08:46:35 UTC 
Is there any update on this bug?
Comment 3 Shveta 2016-09-12 18:59:03 UTC 
Yes that's true , only one instance of catalog item can be added to a bundle.
Comment 4 Greg McCullough 2016-10-07 16:46:29 UTC 
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.
Comment 9 Tina Fitzgerald 2018-02-22 19:49:02 UTC 
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.
Comment 10 Felix Dewaleyne 2018-06-12 08:22:01 UTC 
(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