Bug 1768576

Summary: Sporadic 404 Error when deleting custom button on generic object class
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
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.11.0CC: bmidwood, dmetzger, hkataria, jdupuy, lavenel, mpovolny, obarenbo, smallamp
Target Milestone: GAKeywords: ZStream
Target Release: 5.11.1Flags: simaishi: cfme-5.11.z+
simaishi: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.11.1.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1753388 Environment:
Last Closed: 2019-12-13 00:35:56 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: 1753388    
Bug Blocks:    

Comment 2 Satoe Imaishi 2019-11-18 16:50:22 UTC
PR: https://github.com/ManageIQ/manageiq-ui-classic/pull/6380

Comment 3 John Dupuy 2019-11-26 13:22:18 UTC
Verified in CFME 5.11.1.1.20191122174937_707df01 by creating and deleting multiple generic objects and observing that 404 flash error occurred. The issue in the additional info:

("The custom button is deleted from the UI but if you try to add a custom button of the same name as the one just deleted you hit a "Server Error" and cannot add it. If you click "Add" again it results in a "Name already taken" flash message. If you then hit "Cancel", the button is still created!") 

also appears to have been fixed.

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