Bug 1650559

Summary: Ansible playbook button type not working while creating button on generic object class
Product: Red Hat CloudForms Management Engine Reporter: Niyaz Akhtar Ansari <nansari>
Component: UI - OPSAssignee: Zita Nemeckova <znemecko>
Status: CLOSED ERRATA QA Contact: John Dupuy <jdupuy>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.0CC: bmidwood, hkataria, lavenel, mfeifer, mpovolny, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.11.0.11 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 13:34:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
no catalog dropdown none

Description Niyaz Akhtar Ansari 2018-11-16 13:51:11 UTC
Created attachment 1506415 [details]
no catalog dropdown

Description of problem:


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

How reproducible:
100%

Steps to Reproduce:
1.Go to automation->Automate->Generic Objects
2.Create Generic Objects Class
3.Go Add New button
4.Change button type to Ansible Playbook

Actual results:
Custom Button page not reflecting for ansbile playbook while changing button type to ansible playbook. It only showing default Custom Button page

Expected results:
It should display ansbile playbook button fields 

Additional info:

Comment 4 Niyaz Akhtar Ansari 2019-08-19 09:40:29 UTC
Verified in Version 5.11.0.19.20190813184334_ed72c9f

Comment 6 errata-xmlrpc 2019-12-12 13:34:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:4199