Added messages if the hostname is invalid, and if
the user is not the owner of the lock.
Fixes: 6295
Signed-off-by: Warren Usui <warren.usui@inktank.com>
Change kvm reference to qemu-system-x86_64 and use raw format
in kvm/qemu command. Tested on both Trusty and Precise.
Fixes: 7825
Signed-off-by: Warren Usui <warren.usui@inktank.com>
When reading job information from archive files, use the mtime of
teuthology.log as the job updated time
Signed-off-by: Zack Cerza <zack.cerza@inktank.com>
and '(remote,) = ctx.cluster.only(role).remotes.iterkeys()' would fail with
ValueError and no message if there were less than 0 or more than 1 key.
Now a new function, get_single_remote_value() is called which prints out
more understandable messages.
Fixes: 7510
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
Signed-off-by: Warren Usui <warren.usui@inktank.com>
Default to not printing job descriptions. Add -d/--description flag to
control that behavior. Change --delete's short option to -D. Other small
output tweaks.
Signed-off-by: Zack Cerza <zack.cerza@inktank.com>
For any cases where we just want to kill the running jobs and not delete
any scheduled jobs. This only applies to killing entire runs and is not
the default.
Signed-off-by: Zack Cerza <zack.cerza@inktank.com>
Using a small number of max entries is only needed for one test, so
make it configurable. Setting it too low makes s3tests fail.
Fixes http://tracker.ceph.com/issues/7742
Signed-off-by: Josh Durgin <josh.durgin@inktank.com>
2014-03-20T23:30:28.964 ERROR:teuthology.contextutil:Saw exception from nested tasks
Traceback (most recent call last):
File "/home/teuthworker/teuthology-firefly/teuthology/contextutil.py", line 27, in nested
vars.append(enter())
File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
File "/home/teuthworker/teuthology-firefly/teuthology/task/rgw.py", line 83, in ship_config
idle_timeout = conf.get('idle_timeout', 30)
AttributeError: 'NoneType' object has no attribute 'get'
This happens with job yamls like:
- rgw:
- client.0
(where it is a list and not a dict of clients)
Signed-off-by: Sage Weil <sage@inktank.com>
As of https://github.com/ceph/ceph/pull/1477 the erasure code parameters
are controled via the osd erasure-code-profile set command instead of
being inlined and duplicated in the crush ruleset creation and the pool
creation. There is no need to create the crush ruleset, it is done
implicitly.
Signed-off-by: Loic Dachary <loic@dachary.org>
