Bug 1785723

Summary:	Need ability to extend timeout between when the heat stack creation completes and waiting for ssh on port 22 for enable_ssh_admin
Product:	Red Hat OpenStack	Reporter:	Kevin Jones <kejones>
Component:	python-tripleoclient	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	15.0 (Stein)	CC:	aschultz, augol, dbecker, hbrock, jschluet, jslagle, mburns, morazi, ramishra
Target Milestone:	beta	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-12.3.2-0.20200130192329.78ac810.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-29 07:50:33 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:

Description Kevin Jones 2019-12-20 19:00:18 UTC

During deployment of RHOSP 15, after the heat stack goes CREATE_COMPLETE, the deployment waits for port 22 on all overcloud nodes to become available. Currently the timeout for this is 300 seconds in tripleoclient/constants.py.

On hardware with slow post times, this means that you have to run the command in two phases because without hand modifying the constants.py file, there is no way to set that particular timeout.

Version:
15

Reproducible:
Only on slow to post machines (old hardware or nodes with large amounts of ram)

Steps to reproduce:
1) deploy RHOSP 15 on nodes that take longer than 5 minutes to have SSH available on port 22 during overcloud deployment

Actual results:
times out waiting for port 22 on overcloud nodes to become available

Expected results:
Have ability to set a parameter which extends this timeout so that the deployment will run all the way through

Comment 1 Alex Schultz 2020-01-03 17:24:17 UTC

We'll likely add this timeout customization in a later OSP16 release. We probably won't backport this to OSP15 since it's not a long life release. For now the workaround would be to tweak the constant.

Comment 9 errata-xmlrpc 2020-07-29 07:50:33 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:3148