Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1827721

Summary:	Downloading an image with the direct deploy interface can stuck forever on a flaky server
Product:	Red Hat OpenStack	Reporter:	Dmitry Tantsur <dtantsur>
Component:	openstack-ironic-python-agent	Assignee:	Dmitry Tantsur <dtantsur>
Status:	CLOSED ERRATA	QA Contact:	Alistair Tonner <atonner>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.0 (Train)	CC:	amcleod, bfournie, dtantsur, mburns, rpittau, slinaber
Target Milestone:	beta	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ironic-python-agent-5.0.2-0.20200425123423.656294f.el8ost	Doc Type:	Bug Fix
Doc Text:	Before this update, there were no retries and no timeout when downloading a final instance image with the direct deploy interface in the Bare Metal Provisioning service (ironic). As a result, the deployment could fail if the server that hosts the image fails to respond. + With this update, the image download process attempts two retries and has a connection timeout of 60 seconds.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-29 07:52:07 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:	1822763

Description Dmitry Tantsur 2020-04-24 15:57:27 UTC

There are no retries and no timeout, so if a server doesn't respond, the ramdisk will hang for a while, then fail.

Comment 4 Alex McLeod 2020-06-16 12:28:37 UTC

If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to '-'.

Comment 6 errata-xmlrpc 2020-07-29 07:52:07 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