Bug 1767886

Summary: [RFE] custom service catalog icons being deleted are not actually deleted
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: UI - OPSAssignee: Brian McLaughlin <bmclaugh>
Status: CLOSED ERRATA QA Contact: Niyaz Akhtar Ansari <nansari>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.5CC: bmidwood, fdewaley, hkataria, jocarter, lavenel, mpovolny, mshriver, obarenbo
Target Milestone: GAKeywords: RFE, ZStream
Target Release: 5.11.1Flags: simaishi: cfme-5.11.z+
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 5.11.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1728197 Environment:
Last Closed: 2019-12-13 00:35:54 UTC Type: ---
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:
Bug Depends On: 1728197    
Bug Blocks:    

Comment 2 CFME Bot 2019-11-01 19:29:13 UTC
New commit detected on ManageIQ/manageiq-ui-classic/ivanchuk:

https://github.com/ManageIQ/manageiq-ui-classic/commit/2b0101f06951c3cf00f1b7168b99eca5495017f8
commit 2b0101f06951c3cf00f1b7168b99eca5495017f8
Author:     Harpreet Kataria <hkataria>
AuthorDate: Tue Aug 27 14:52:56 2019 -0400
Commit:     Harpreet Kataria <hkataria>
CommitDate: Tue Aug 27 14:52:56 2019 -0400

    Merge pull request #6111 from bmclaughlin/update-tree-after-deleting-service-icon

    Refresh trees after deleting catalog custom icon

    (cherry picked from commit a6a7c3f86b988ea5459a742628a98102db5ac5b2)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1767886

 app/controllers/catalog_controller.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 3 Niyaz Akhtar Ansari 2019-12-04 09:40:48 UTC
Verified in Version 5.11.1.1.20191122174937_707df01

Comment 5 errata-xmlrpc 2019-12-13 00:35:54 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-2019:4201