Bug 1831752

Summary:	Configurable timeout for installer itself
Product:	OpenShift Container Platform	Reporter:	Pablo Iranzo Gómez <pablo.iranzo>
Component:	Installer	Assignee:	Abhinav Dahiya <adahiya>
Installer sub component:	openshift-installer	QA Contact:	Johnny Liu <jialiu>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	medium
Priority:	unspecified
Version:	4.4
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-08 18:35:50 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:	1831748

Description Pablo Iranzo Gómez 2020-05-05 14:58:35 UTC

Description of problem:

Currently, when testing installation several times the installer times out before completing the installationm, but the status of the operators keep changing and becoming available if extra time is given.

It would be great to have configurable extra time, so that installer doesn't timeout and allows operators and infra in general to settle.


Does the actual timeout is based on a specific amount of workers?, i.e. having 4 workers instead of 2, does increase the total timeout?


Expected results:
 
Configurable timeout multiplier or fixed extension to allow installer to still return 'success' in environments where it fails now, only because of the installer itself timing out.

Comment 1 Abhinav Dahiya 2020-05-08 18:35:50 UTC

This seems like a RFE and we don't track these in bugzilla. please open on in https://issues.redhat.com/projects/RFE/issues

> It would be great to have configurable extra time, so that installer doesn't timeout and allows operators and infra in general to settle.

failing to install in the alloted time is a failure, and we should open bugs on the operator that took the longest.

also the wait-for install-complete subcommand can be run multiple times to wait for 30 min intervals.. $(retry wait-for install-complete)

in don't think the installer will allow configuring the time because we want think the already provided time is almost always good enough 20+30 minutes for productions environemnts. and we can discuss more in the RFE.