Actions
Bug #9099
closedVPS machines are taking unusually long time to start running tests
Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
It's more like a behavioral observation, however I noticed that lately newly scheduled runs after locking a VM taking long time and sometime to start actual run.
Log shows:
422005 (pid 29221) 2014-08-13T10:19:15.750 INFO:teuthology.task.internal:virtual machine is still unavailable
And that can be even if we have lots of free VPS'es and only one test was scheduled.
Updated by Yuri Weinstein over 9 years ago
Sandon found out that mira010 was to blame.
Is there any way to monitor this in the future automatically?
Actions