Bug 1496749

Summary: Custom Button set on Providers does not show up in OpenShift Providers.
Product: Red Hat CloudForms Management Engine Reporter: Loic Avenel <lavenel>
Component: UI - OPSAssignee: Zita Nemeckova <znemecko>
Status: CLOSED ERRATA QA Contact: Yadnyawalk Tale <ytale>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: akarol, dclarizi, epacific, hkataria, jhardy, lavenel, mpovolny, obarenbo, simaishi, smallamp
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:18:32 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:

Description Loic Avenel 2017-09-28 09:34:25 UTC 
Description of problem: Custom Button set on Providers does not show up in OpenShift Providers.


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


How reproducible: Always


Steps to Reproduce:
1. Go to Automation>Automate>Customisation>Buttons
2. Create a button Group and Button on Provider
3. Go to OCP provider

Actual results: Button is not there


Expected results: Button is visible


Additional info:
Comment 2 Dave Johnson 2017-09-28 09:44:54 UTC 
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.
Comment 3 Sudhir Mallamprabhakara 2017-09-28 17:05:23 UTC 
Can you pls assign the severity on this??
Comment 5 Zita Nemeckova 2017-10-02 10:05:15 UTC 
https://github.com/ManageIQ/manageiq-ui-classic/pull/2269
Comment 9 errata-xmlrpc 2018-03-01 13:18:32 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/RHSA-2018:0380