Bug 1833343

Summary:	Helm actions timeout for some charts that take more time
Product:	OpenShift Container Platform	Reporter:	Rohit Rai <rorai>
Component:	Dev Console	Assignee:	Rohit Rai <rorai>
Status:	CLOSED ERRATA	QA Contact:	Gajanan More <gamore>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	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:
Clones:	1833344 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:36:10 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:
Bug Depends On:
Bug Blocks:	1833344

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