Bug 2072829 - When Argo App with jsonnet object is deployed, topology and cluster status would fail to display the correct statuses.
Summary: When Argo App with jsonnet object is deployed, topology and cluster status wo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: rhacm-2.5
Assignee: Kevin Cormier
QA Contact: Almen Ng
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-07 04:01 UTC by Almen Ng
Modified: 2022-06-09 02:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-09 02:10:35 UTC
Target Upstream Version:
Embargoed:
almng: rhacm-2.5+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 21507 0 None None None 2022-04-07 09:05:10 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:10:41 UTC

Comment 1 bot-tracker-sync 2022-04-08 00:41:42 UTC 
G2Bsync 1092245329 comment 
 fxiang1 Thu, 07 Apr 2022 21:51:33 UTC 
 G2Bsync

@almen-ng This has nothing to do with jsonnet. Looks like the destinationNamespace(default) is different than the resource namespace(pacman-app) which is not supported. We only support deploying app resources to the same namespace as the destinationNamespace:

![image](https://user-images.githubusercontent.com/38960034/162325457-f0eaf961-dfc2-4ee3-bcef-bfd6e7f78770.png)

![image](https://user-images.githubusercontent.com/38960034/162325519-52d22aa2-8afc-448f-a383-55c093eb4a4c.png)

After using the same destinationNamespace and resource namespace, the topology displays properly:

![image](https://user-images.githubusercontent.com/38960034/162325708-a112cc76-d67c-438f-ab91-30a2eba66276.png)

![image](https://user-images.githubusercontent.com/38960034/162325813-d230c191-60ae-4805-80c2-e8e3273ffeb9.png)
Comment 6 errata-xmlrpc 2022-06-09 02:10:35 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 2.5 security updates, images, and bug fixes), 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-2022:4956
Note You need to log in before you can comment on or make changes to this bug.