Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1807585

Summary: Helm Topology groups doesn't work for Helm 3 charts
Product: OpenShift Container Platform Reporter: Rohit Rai <rorai>
Component: Dev ConsoleAssignee: Rohit Rai <rorai>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, gamore, nmukherj, rgarg
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1807584 Environment:
Last Closed: 2020-05-13 21:59:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1807584    
Bug Blocks:    
Attachments:
Description Flags
Helm 3 charts grouping none

Description Rohit Rai 2020-02-26 16:33:25 UTC 
+++ This bug was initially created as a clone of Bug #1807584 +++

Description of problem:
Helm Topology groups rely on labels to identify all the resources created by helm release. This strategy doesn't work for Helm 3 charts since they do not have all the labels.

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


How reproducible:
Always

Steps to Reproduce:
1. Install bitnami/redis chart.
2. Go to topology

Actual results:
Resources created by Helm release are not grouped together.

Expected results:
All the resources created by helm release should be grouped together.

Additional info:
Comment 3 Gajanan More 2020-03-04 10:17:56 UTC 
Created attachment 1667453 [details]
Helm 3 charts grouping
Comment 4 Gajanan More 2020-03-04 10:19:37 UTC 
I have validated this bug on 
Build:4.4.0-0.nightly-2020-03-04-000622 
Browser:Google Chrome Version 78.0.3904.108
Marking this bug as verified
Comment 6 errata-xmlrpc 2020-05-13 21:59:57 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/RHBA-2020:0581