Bug 2039315 - Helm release list page should only fetch secrets for deployed charts
Summary: Helm release list page should only fetch secrets for deployed charts
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Rohit Rai
QA Contact: spathak@redhat.com
Depends On:
Blocks: 2044292
TreeView+ depends on / blocked
Reported: 2022-01-11 13:38 UTC by Rohit Rai
Modified: 2022-03-12 04:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-12 04:40:34 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10812 0 None open Bug 2039315: Filter superseded helm secrets and fix firehose to support partial metadata 2022-01-11 13:47:27 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:40:44 UTC

Description Rohit Rai 2022-01-11 13:38:57 UTC
Description of problem: Helm release list page and topology page fetches all the secrets for helm release that are not deployed.

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

How reproducible: Always

Steps to Reproduce:
1. Install a helm chart from the catalog.
2. Upgrade or rollback the helm release a few times.
3. Go to helm release list page or topology.

Actual results: List page fetches all the secrets.

Expected results: It should only fetch the latest revision of the release.

Additional info:

Comment 3 Christoph Jerolimov 2022-01-26 08:32:27 UTC
Verified on 4.10.0-0.ci-2022-01-26-071949

Comment 6 errata-xmlrpc 2022-03-12 04:40:34 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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.