Bug 1940196 - View Resource YAML option shows 404 error when reviewing a Subscription for an application
Summary: View Resource YAML option shows 404 error when reviewing a Subscription for a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: App Lifecycle
Version: rhacm-2.2.z
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: rhacm-2.2.2
Assignee: Kevin Cormier
QA Contact: Eveline Cai
bswope@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-17 19:18 UTC by Sam Yangsao
Modified: 2021-08-06 00:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-06 00:51:36 UTC
Target Upstream Version:
Embargoed:
juhsu: rhacm-2.3+


Attachments (Terms of Use)
single application resource deployed on 1 cluster (70.70 KB, image/png)
2021-03-17 19:18 UTC, Sam Yangsao
no flags Details
404 error seen when selecting the "View Resource YAML" option on top (31.07 KB, image/png)
2021-03-17 19:19 UTC, Sam Yangsao
no flags Details
same app deployed to many clusters, all YAML outputs look fine (76.95 KB, image/png)
2021-03-17 19:19 UTC, Sam Yangsao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 10594 0 None None None 2021-03-17 22:12:59 UTC
Red Hat Product Errata RHSA-2021:3016 0 None None None 2021-08-06 00:52:11 UTC

Description Sam Yangsao 2021-03-17 19:18:22 UTC
Created attachment 1764165 [details]
single application resource deployed on 1 cluster

Description of problem:

Viewing a Subscription for an application does not show the entire YAML file when selecting the "View Resource YAML" option and shows a `404` instead.  While the "View Resource YAML" option under "Cluster deploy status" does show the YAML file in its entirety. 

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

OCP 4.6.18
ACM 2.2.1

How reproducible:

Always

Steps to Reproduce:

1.  Deploy an application following [1] and deploying on only 1 OCP cluster

2.  Under the application UI, select the Subscription/NGINX icon, then select the "View Resource YAML" option on top [2] 404 error shows up [3].  

But when you select the "View Resource YAML" option underneath the "Cluster deploy status" area for the cluster the resource is running on, the YAML file shows up properly.

3.  Deploy this same application to 2+ OCP clusters.  All the "View Resource YAML" options do not show any 404 errors and output the data fine.

[1] https://trello.com/c/0yUvqvc1/51-hf305-application-lifecycle-version-bump
[2] single-resource-yaml.png
[3] 404-error.png
[4] multiple-ocp.png

Actual results:

404 code with one application deployed when viewing the YAML output via the "View Resource YAML" option

Expected results:

There should be no errors when viewing this option, whether the Subscription/app is deployed on 1 cluster or more.

Additional info:

Comment 1 Sam Yangsao 2021-03-17 19:19:06 UTC
Created attachment 1764166 [details]
404 error seen when selecting the "View Resource YAML" option on top

Comment 2 Sam Yangsao 2021-03-17 19:19:44 UTC
Created attachment 1764167 [details]
same app deployed to many clusters, all YAML outputs look fine

Comment 3 Mike Ng 2021-04-06 14:58:07 UTC
G2Bsync 805829219 comment 
 KevinFCormier Wed, 24 Mar 2021 13:38:38 UTC 
 G2Bsync Fixed for 2.2.2 and newer.

Comment 8 juhsu 2021-08-05 20:26:11 UTC
Fixed in 2.2.2 and 2.3

Comment 9 errata-xmlrpc 2021-08-06 00:51:36 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 (Important: Red Hat Advanced Cluster Management for Kubernetes version 2.3), 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-2021:3016


Note You need to log in before you can comment on or make changes to this bug.