On Tue, Oct 2, 2012 at 9:56 AM, Gregory Farnum <greg@xxxxxxxxxxx> wrote: >> File "/home/lokesh/Downloads/ceph-teuthology-78b7b02/teuthology/misc.py", >> line 501, in read_config >> ctx.teuthology_config.update(new) >> ValueError: dictionary update sequence element #0 has length 1; 2 is >> required > I haven't looked at teuthology much in a while, but the error is > complaining that you have a list of length 1 that requires length 2. > I'm pretty sure your problem is that you only have one machine > available, but the default Ceph task wants 2. Actually, that error seems to be bubbling up from where it reads ~/.teuthology.yaml -- it expects a file like this: lock_server: http://foo.example.com/locker/lock queue_host: bar.example.com queue_port: 1234 Teuthology doesn't have much in the way of data format enforcement -- it kind of assumes the target audience is programmers, so they can just dig in. > Rather more importantly than that, teuthology is a piece of our > internal infrastructure. We make it available to others, but if you > plan to use it in your own testing you will need infrastructure of > your own to run it on — we have a generic server farm, but also > "special" machines like a lock server, in addition to the client > actually running the test. You should not play with it casually. Hey, I resent that remark! We *want* outside users for teuthology. That would be awesome. That would probably also mean needing to split the current "tasks" out of the teuthology core, so that the core becomes a general-purpose multi-machine test runner. But you are correct in that there are a lot of assumptions about the environment in there. Tread carefully. -- 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
