Project

General

Profile

Actions
Copy link

Bug #9239

closed

Process from starting locking machines till tests start running take long time (~1 hour)

Added by Yuri Weinstein over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Sandon Van Ness
Category:
-
Target version:
-
% Done:

100%

Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

We are seeing this on late runs.

For example - http://qa-proxy.ceph.com/teuthology/teuthology-2014-08-26_08:50:02-rgw-dumpling-testing-basic-vps/451997/teuthology.log

2014-08-26T08:50:27.537 INFO:teuthology.task.internal:Locking machines...
.........
2014-08-26T09:52:12.157 INFO:teuthology.task.internal:Locked targets:

Compare time stamps ^

Actions
Copy link
 #1

Updated by Ian Colle over 9 years ago

  • Priority changed from Normal to Urgent
Actions
Copy link
 #2

Updated by Yuri Weinstein over 9 years ago

Something is badly broken, this suite actually never got off the ground - http://pulpito.front.sepia.ceph.com/teuthology-2014-08-26_11:03:49-rgw-dumpling-testing-basic-vps/

Actions
Copy link
 #3

Updated by Sandon Van Ness over 9 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

sending a sighup to dhcpd daemon insures lease file stays fresh without tons of duplicates which prevents DNS from getting lagged which is what was causing this.

Actions
Copy link

Also available in: Atom PDF