Bug 2102273 - Inconsistent cluster resource statuses between "All Subscription" topology and individual topologies
Summary: Inconsistent cluster resource statuses between "All Subscription" topology an...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: App Lifecycle
Version: rhacm-2.5.z
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: rhacm-2.6
Assignee: Feng Xiang
QA Contact: Almen Ng
bswope@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-29 14:45 UTC by Almen Ng
Modified: 2022-09-13 20:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-13 20:06:21 UTC
Target Upstream Version:
Embargoed:
almng: rhacm-2.5.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 23856 0 None None None 2022-06-29 18:55:27 UTC
Red Hat Product Errata RHSA-2022:6507 0 None None None 2022-09-13 20:06:30 UTC

Comment 3 bot-tracker-sync 2022-06-29 23:22:35 UTC 
G2Bsync 1170423023 comment 
 fxiang1 Wed, 29 Jun 2022 19:52:02 UTC 
 G2Bsync
Discussed with Almen, deploying two of the same app with same app resource name in the same namespace/cluster is probably no a valid scenario since Kubernetes will block the resource creation for the second app due to an existing resource with the same name.
![image](https://user-images.githubusercontent.com/38960034/176529714-91e97ecc-d7ee-400e-8439-7a85bd9a61ee.png)


However, this problem will still appear with the same app but different clusters(ie. the node status will only display on resource node for one of the clusters) so I think I will keep this BZ to fix that scenario.
Comment 12 errata-xmlrpc 2022-09-13 20:06:21 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 (Critical: Red Hat Advanced Cluster Management 2.5.2 security fixes 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:6507
Note You need to log in before you can comment on or make changes to this bug.