Bug 1490838 - [ovirt-ansible-roles] ovirt-vm-infra: unconfigurable timeouts
Summary: [ovirt-ansible-roles] ovirt-vm-infra: unconfigurable timeouts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-ansible-roles
Version: 4.1.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Ondra Machacek
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks: 1492489
TreeView+ depends on / blocked
 
Reported: 2017-09-12 11:10 UTC by Petr Kubica
Modified: 2019-05-16 13:14 UTC (History)
3 users (show)

Fixed In Version: ovirt-ansible-roles-1.1.1-0.el7ev
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
: 1492489 (view as bug list)
Environment:
Last Closed: 2018-05-15 18:00:33 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/oVirt ovirt-ansible pull 82 0 None None None 2017-09-15 09:30:18 UTC
Red Hat Product Errata RHEA-2018:1534 0 None None None 2018-05-15 18:01:05 UTC

Description Petr Kubica 2017-09-12 11:10:31 UTC 
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
Comment 2 Petr Kubica 2018-01-03 12:04:19 UTC 
Verified
ovirt-ansible-vm-infra-1.1.3-1.el7ev.noarch
ansible-2.4.1.0-1.el7ae.noarch
Comment 7 errata-xmlrpc 2018-05-15 18:00: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/RHEA-2018:1534
Comment 8 Franta Kust 2019-05-16 13:07:30 UTC 
BZ<2>Jira Resync
Note You need to log in before you can comment on or make changes to this bug.