Bug 1972821

Summary: 504 errors trying to "View YAML" for application resources
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Lars Kellogg-Stedman <lars>
Component: App LifecycleAssignee: Kevin Cormier <kcormier>
Status: CLOSED ERRATA QA Contact: Eveline Cai <ecai>
Severity: unspecified Docs Contact: bswope <bswope>
Priority: unspecified    
Version: rhacm-2.2CC: daliu, xiangli
Target Milestone: ---Flags: ming: rhacm-2.2.z+
Target Release: rhacm-2.2.6   
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: 2021-08-10 18:33:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lars Kellogg-Stedman 2021-06-16 16:51:46 UTC 
After deploying an application using ACM, I tried to "View Resource YAML" from the "Resource Topology" view.

In most cases, this would open the "Search" page and spin for a bit before failing with a 504 error. There seem to be several problems here:

1. We should be providing a human-friendly error message in the UI rather than just displaying a "504 Error" message, which doesn't tell anybody anything.
2. We should not be getting 504 errors in the first place -- if an operator selects "view resource yaml" for a resource, they should be able to view the YAML document without errors.

ACM 2.2.3
OCP 4.6.31 (hub cluster)
OCP 4.7.13 (managed cluster)
Comment 1 daliu 2021-06-22 04:17:41 UTC 
it's same as https://bugzilla.redhat.com/show_bug.cgi?id=1964161
will be fixed in 2.2.5
Comment 8 errata-xmlrpc 2021-08-10 18:33:12 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 (Red Hat Advanced Cluster Management 2.2.6 bug fix update), 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-2021:3126