Bug 1501528

Summary: Editing an Ansible Playbook Catalog Item - Cannot fetch dialog list when selected "Use Existing" and Cannot Assign it to a Catalog
Product: Red Hat CloudForms Management Engine Reporter: Kedar Kulkarni <kkulkarn>
Component: UI - OPSAssignee: Harpreet Kataria <hkataria>
Status: CLOSED DUPLICATE QA Contact: Kedar Kulkarni <kkulkarn>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: hkataria, jhardy, kkulkarn, mpovolny, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-03 18:50:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1438923    
Attachments:
Description Flags
Editing Ansible Catalog Item none

Description Kedar Kulkarni 2017-10-12 18:53:34 UTC
Created attachment 1337940 [details]
Editing Ansible Catalog Item

Description of problem:

When editing an existing playbook catalog item, the Catalog Item does not remember the "Dialog", asks to set the dialog again, and when clicked on "Use Existing" the list shows no dialog, even though there are previously created dialog present.

Version-Release number of selected component (if applicable):
5.9.0.2

How reproducible:
100%

Steps to Reproduce:
1.Create an Ansible Playbook catalog item with cloud credentials
2.choose Edit
3.Observe value for Dialog field

Actual results:
as shown in the screenshot

Expected results:
It should load previously created Dialog and also, if user clicks "Use Existing" the dropdown list should show existing dialog. 

Additional info:

Comment 3 Kedar Kulkarni 2017-10-12 19:48:17 UTC
I am facing difficulty assigning that Catalog Item to a Catalog as well. The dropdown does not show any catalog, even though there are 2 of them present.

Comment 7 Harpreet Kataria 2018-05-03 18:50:54 UTC

*** This bug has been marked as a duplicate of bug 1500833 ***