From: Loic Dachary <loic@dachary.org>
To: Zack Cerza <zack.cerza@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: teuthology task waiting for machines (> 8h)
Date: Sat, 28 Jun 2014 12:27:06 +0200 [thread overview]
Message-ID: <53AE987A.6080500@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Hi Zack,
http://pulpito.ceph.com/loic-2014-06-27_18:45:37-upgrade:firefly-x:stress-split-wip-8475-testing-basic-plana/329515/
seems to indicate that the tasks cannot obtain the machines it needs:
2014-06-27T17:55:19.072 INFO:teuthology.task.internal:Locking machines...
2014-06-27T17:55:19.110 INFO:teuthology.task.internal:waiting for more machines to be free (need 3 see 5)...
2014-06-27T17:55:29.175 INFO:teuthology.task.internal:waiting for more machines to be free (need 3 see 5)...
...
2014-06-28T03:22:13.745 INFO:teuthology.task.internal:waiting for more machines to be free (need 3 see 0)...
2014-06-28T03:22:23.787 INFO:teuthology.task.internal:waiting for more machines to be free (need 3 see 0)...
Is it something expected (for instance when tasks with a higher priorty take precedence) ? If it is then all that's needed is patience right ?
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next reply other threads:[~2014-06-28 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 10:27 Loic Dachary [this message]
2014-06-28 15:47 ` teuthology task waiting for machines (> 8h) Yuri Weinstein
2014-06-28 16:51 ` Loic Dachary
2014-06-30 14:11 ` Zack Cerza
2014-06-30 14:10 ` Zack Cerza
2014-06-30 15:10 ` Loic Dachary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53AE987A.6080500@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=zack.cerza@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.