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>
Newer btfs userland tools needs a -f like xfs instead of a prompt
for yes. Trusty needs this change.
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
Newer btfs userland tools needs a -f like xfs instead of a prompt
for yes. Trusty needs this change.
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
With thrashing, cleanup will require recovering the degraded objects
first, while the initial write out doesn't since they they are new
objects.
Signed-off-by: Samuel Just <sam.just@inktank.com>
Made a task that simply prints the output that is given to it as
an argument. Can be used like any other task (under sequential,
etc...)
IE:
tasks:
- print: "String"
- chef: null
- print: "Another String"
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
Signed-off-by: Yuri Weinstein <yuri.weinstein@inktank.com>
For now hard code the max-entries for the radosgw-agent, since
this is the only test that is affected by it.
Signed-off-by: Josh Durgin <josh.durgin@inktank.com>
I've noticed sometimes try_push_job_info() fails because of server load
issues. It should try more than once (and now does).
Signed-off-by: Zack Cerza <zack.cerza@inktank.com>
I didn't love the way safe_while was encouraged to be used and it didn't
fit right with the new no-raising behavior. Now it's encouraged to be
used like this:
with safe_while() as proceed:
while proceed():
do_things()
Signed-off-by: Zack Cerza <zack.cerza@inktank.com>
