bvt deployment waits too long to fail
Bug #1558505 reported by
Aleksandra Fedorova
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Kyrylo Galanov | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) | ||
Newton |
Fix Committed
|
Medium
|
Kyrylo Galanov |
Bug Description
http://
In this deployment see diagnostic snapshot attached according to astute.log there were three broken sets of tasks (HA_proxy, mysql and keystone_admin smth), which were hanging in 'running' state for more then half an hour, without any changes.
We should catch such situations early and fail the build.
Changed in fuel: | |
status: | New → Confirmed |
assignee: | nobody → Fuel Library Team (fuel-library) |
tags: | added: area-python |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Kyrylo Galanov (kgalanov) |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: |
added: area-library removed: area-python |
Changed in fuel: | |
status: | In Progress → Confirmed |
Changed in fuel: | |
assignee: | Kyrylo Galanov (kgalanov) → Fuel Library Team (fuel-library) |
To post a comment you must log in.
Hi Aleksandra,
There are 3 levels of timeouts:
1. puppet resource provider timeout
2. astute task timeout
3. automated test timeout
I cannot shrink timeouts inspired by intuition because it might break large scale deployments.
Which timeout specifically do you propose to decrease?
Best regards,
Kyrylo