On Wed, 3 Oct 2012, Gregory Farnum wrote: > Check out the thread titled "[ceph-commit] teuthology lock_server error". :) In case it didn't hit ceph-devel: Add check-locks: false to your yaml file and the lock checks will all go away. sage > > On Wed, Oct 3, 2012 at 5:41 AM, Pradeep S <pradeeps192@xxxxxxxxx> wrote: > > hi, i am getting the following error while executing ceph-qa-suite in > > teuthology. > > INFO:teuthology.run_tasks:Running task internal.save_config... > > INFO:teuthology.task.internal:Saving configuration > > INFO:teuthology.run_tasks:Running task internal.check_lock... > > INFO:teuthology.task.internal:Checking locks... > > INFO:teuthology.lock:GET request to > > 'http://pradeep:4000/lock/pradeep@xxxxxxxxxxx' with body 'None' failed > > with response code 404 > > ERROR:teuthology.run_tasks:Saw exception from tasks > > Traceback (most recent call last): > > File "/home/pradeep/Downloads/ceph-teuthology-0395df3/teuthology/run_tasks.py", > > line 25, in run_tasks > > manager = _run_one_task(taskname, ctx=ctx, config=config) > > File "/home/pradeep/Downloads/ceph-teuthology-0395df3/teuthology/run_tasks.py", > > line 14, in _run_one_task > > return fn(**kwargs) > > File "/home/pradeep/Downloads/ceph-teuthology-0395df3/teuthology/task/internal.py", > > line 110, in check_lock > > 'could not read lock status for {name}'.format(name=machine) > > AssertionError: could not read lock status for pradeep@xxxxxxxxxxx > > > > The conf file is: lock_server: http://pradeep:4000/lock. > > > > With thanks > > Pradeep S > > -- > > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
