Bug 1834354

Summary: Helm resource tab on topology side panel creates wrong resource links for CLI charts
Product: OpenShift Container Platform Reporter: Rohit Rai <rorai>
Component: Dev ConsoleAssignee: Rohit Rai <rorai>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:37:32 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 Rohit Rai 2020-05-11 14:57:02 UTC
Description of problem: Helm charts installed using CLI have wrong resource links created in side panel for helm release. The links created are using `all-namespaces` instead of release namespace

Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce:
1. Add stable helm repo in CLI
2. Install mariadb - `helm install maria-test stable/mariadb`
3. Go to the topology and select the release.
4. Click on any of the resources in the list.

Actual results: It takes you to all-namespaces page

Expected results: It should take you to the correct resource link.

Reproducibility (Always/Intermittent/Only Once):  Always.

Build Details:
Additional info:

Comment 3 Gajanan More 2020-05-15 06:24:02 UTC
I have validated the bugzilla on:
Build: 4.5.0-0.ci-2020-05-14-224329
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.

Comment 4 errata-xmlrpc 2020-07-13 17:37:32 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:2409