Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ovirtlago: change --with-vms timeout in 'lago ovirt start' to 8 minutes #518

Merged
merged 1 commit into from
Apr 27, 2017

Conversation

nvgoldin
Copy link
Contributor

@nvgoldin nvgoldin commented Apr 24, 2017

ovirtlago: reconfigure timeouts in 'lago ovirt start'

  1. Increased default timeout for waiting until the VMs connected
    to the Engine report 'up' status to 8 minutes.
  2. Added '--vms-timeout' parameter to allow configuring that timeout.
  3. Increased 'ovirt-engine'/'vdsmd' service timeout to 3 minutes.
  4. Added default timeouts in all relevant functions headers, and set
    the timeouts explicitly in 'do_ovirt_start' for visibility.

@nvgoldin nvgoldin added the bug label Apr 24, 2017
@nvgoldin nvgoldin requested review from mykaul and gbenhaim April 24, 2017 11:54
ovirtlago/cmd.py Outdated
with LogTask('Starting oVirt environment'):
prefix.start()
with LogTask('Waiting for ovirt-engine status'):
prefix.virt_env.assert_engine_alive()
prefix.virt_env.assert_engine_alive(timeout=2 * 60)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm afraid that we will hit this timeout also, what do you think ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be - this would mean it takes libvirt to boot the VM and until the engine service is running more than 2 minutes, which seems a lot. I never had it timed out on that stage, though I never had it timed out on the 'vms' start either. I actually think that the timeout for the VMs now is huge - 8 minutes. But practically I can't think of any other 'hot fix' for that..

You experienced it timing out on this engine service stage?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to 3 minutes.

@nvgoldin nvgoldin force-pushed the increase_start_vm_timeout branch 3 times, most recently from fc89c24 to 74f75d8 Compare April 27, 2017 07:50
1. Increased default timeout for waiting until the VMs connected
to the Engine report 'up' status to 8 minutes.
2. Added '--vms-timeout' parameter to allow configuring that timeout.
3. Increased 'ovirt-engine'/'vdsmd' service timeout to 3 minutes.
4. Added default timeouts in all relevant functions headers, and set
the timeouts explicitly in 'do_ovirt_start' for visibility.

Signed-off-by: Nadav Goldin <ngoldin@redhat.com>
@nvgoldin nvgoldin force-pushed the increase_start_vm_timeout branch from 74f75d8 to 33ca8c0 Compare April 27, 2017 07:53
@gbenhaim
Copy link
Member

ci merge please

@ovirt-infra ovirt-infra merged commit 4520202 into lago-project:master Apr 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants