Bug 1833449

Summary: Uninformative message when no helm releases are installed
Product: OpenShift Container Platform Reporter: Jeff Phillips <jephilli>
Component: Dev ConsoleAssignee: Jeff Phillips <jephilli>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium 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:
Version: 4.5.0-0.ci-2020-05-08-095803 Cluster ID: 48f37dfa-8cbd-4ecc-8a7a-80eb70ed44a2 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
Last Closed: 2020-07-13 17:36:23 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:
Attachments:
Description Flags
no releases none

Description Jeff Phillips 2020-05-08 17:06:36 UTC
Created attachment 1686544 [details]
no releases

Description of problem:

The Helm section of the developer perspective shows a simple `Not Found` message. The page should tell me that there are no helm releases installed for the current project.

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


How reproducible:


Steps to Reproduce:
1. Create a new project
2. Navigate to the developer perspective -> Helm

Actual results:

A page is shown with a simple 'Not Found' message

Expected results:

We need to have better messaging. UX recommendation is No Helm Releases Found


Additional info:

Comment 3 Gajanan More 2020-05-21 05:39:29 UTC
I have validated the bugzilla on:
Build: 4.5.0-0.nightly-2020-05-20-235311
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.

Comment 4 errata-xmlrpc 2020-07-13 17:36:23 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