root@master [rc=0]# <LAVA_DISPATCHER>2013-09-10 12:26:25 PM INFO: setting status pass
<LAVA_DISPATCHER>2013-09-10 12:26:25 PM INFO: finally status pass
<LAVA_DISPATCHER>2013-09-10 12:26:25 PM INFO: [ACTION-E] lava_test_shell is finished successfully.
<LAVA_DISPATCHER>2013-09-10 12:26:25 PM INFO: Passing results bundle to LAVA Coordinator.
<LAVA_DISPATCHER>2013-09-10 12:26:25 PM DEBUG: sending result bundle
<LAVA_DISPATCHER>2013-09-10 12:26:25 PM DEBUG: Connecting to LAVA Coordinator on localhost:3079
<LAVA_DISPATCHER>2013-09-10 12:26:25 PM DEBUG: sending message: {"sub_id": "77.0", "blocksize": 4096, "cli
<LAVA_DISPATCHER>2013-09-10 12:26:26 PM DEBUG: Connecting to LAVA Coordinator on localhost:3079
<LAVA_DISPATCHER>2013-09-10 12:26:26 PM DEBUG: sending message: {"sub_id": "77.0", "blocksize": 4096, "cli
<LAVA_DISPATCHER>2013-09-10 12:26:27 PM DEBUG: Connecting to LAVA Coordinator on localhost:3079
<LAVA_DISPATCHER>2013-09-10 12:26:27 PM DEBUG: sending message: {"sub_id": "77.0", "blocksize": 4096, "cli
<LAVA_DISPATCHER>2013-09-10 12:26:27 PM INFO: Submitting bundle 'aaf7788b0dcbb2855c9aff7e59894ddf29dc7ea1' and aggregating with pending group results.
<LAVA_DISPATCHER>2013-09-10 12:26:28 PM DEBUG: server RPC endpoint URL: http://tekkamanninja@192.168.1.12/RPC2/
<LAVA_DISPATCHER>2013-09-10 12:26:28 PM WARNING: xmlrpclib.Fault occurred
<LAVA_DISPATCHER>2013-09-10 12:26:28 PM WARNING: Fault code: -32603
<LAVA_DISPATCHER>2013-09-10 12:26:28 PM WARNING: Fault string: Internal Server Error (details hidden :)
On Wed, 11 Sep 2013 18:13:59 -0000
Launchpad Bug Tracker <email address hidden> wrote:
> Submti the multinode job which only has one device in the
> device_group will cause error when submit the result bundle
> https:/
> notification because you are a bug assignee.
There are two options here:
0: Automatically convert the JSON to traditional singlenode format by
dropping device_group, count and role and promoting device_type and
tags to replace it.
1: Refuse such submissions as invalid JSON.
The problem with 0: is that the tests within the job may well be
expecting MultiNode behaviour. The most likely cause of the JSON
structure described is editing a working MultiNode JSON file to change
the devices involved from two different types to just one type, without
changing the count.
I'll initially investigate option 1:.
--
Neil Williams
=============
http://