Bug 1492489

Summary:	[downstream clone - 4.1.7] [ovirt-ansible-roles] ovirt-vm-infra: unconfigurable timeouts
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-ansible-roles	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED ERRATA	QA Contact:	Petr Kubica <pkubica>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.5	CC:	lsvaty, mgoldboi, mperina
Target Milestone:	ovirt-4.1.7	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-ansible-roles-1.0.4-1.el7ev	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:	1490838	Environment:
Last Closed:	2017-11-07 17:27:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1490838
Bug Blocks:

Description rhev-integ 2017-09-17 19:41:03 UTC

+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1490838 +++
======================================================================

Description of problem:
Importing VM from template took 3 minutes and 41 second for me (preallocated disk) but implicit timeout is only 180 second. When user will create more (50+) VM with slower storage domain, it can take far longer and user can't set these timeouts (waiting for IP, waiting for adding VM... etc). 180 second is generally very short timeout so in relevant cases should be adjusted.

Version-Release number of selected component (if applicable):
ovirt-ansible-roles-1.0.3-1.el7ev.noarch
ansible-2.3.2.0-2.el7.noarch

(Originally by Petr Kubica)

Comment 2 Petr Kubica 2017-10-18 09:03:22 UTC

Verified in
ansible-2.3.2.0-2.el7.noarch
ovirt-ansible-roles-1.0.4-1.el7ev.noarch

Comment 4 errata-xmlrpc 2017-11-07 17:27:31 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-2017:3137