Bug 1833343 - Helm actions timeout for some charts that take more time
Summary: Helm actions timeout for some charts that take more time
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.0
Assignee: Rohit Rai
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks: 1833344
TreeView+ depends on / blocked
 
Reported: 2020-05-08 13:27 UTC by Rohit Rai
Modified: 2020-07-13 17:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1833344 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:36:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5360 0 None closed Bug 1833343: Remove fetch timeout for Helm actions 2020-07-03 10:05:35 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:36:28 UTC

Description Rohit Rai 2020-05-08 13:27:23 UTC 
Description of problem: Helm chart installation takes more time than usual which is why the fetch request timeouts. We increased timeout to 60s in 4.5 but for 4.4 the chart installation consistently fails for IBM charts.

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce:
1. In 4.4 cluster, go to helm catalog.
2. Try to install IBM charts

Actual results:
Request Times out error on install form.

Expected results:
Request should not timeout.

Reproducibility (Always/Intermittent/Only Once):
Intermittent
Comment 3 Gajanan More 2020-05-12 12:49:01 UTC 
I have validated the bugzilla. Currently I don't see helm actions timeout for charts that take more time to install.
Validation done on:
Build: 4.5.0-0.ci-2020-05-11-234936
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.
Comment 4 errata-xmlrpc 2020-07-13 17:36:10 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
Note You need to log in before you can comment on or make changes to this bug.