uuid generation is unreliable

[Deepti B. Kalakeri]

lava-test fails to complete for beagle board hwpack. Here is the traceback of the error:

Cause

A test with UUID 2600f98a-4f00-11e1-98b8-376b2c52277f already exists

Deserialization failure traceback

Traceback (most recent call last):
  File "/srv/lava/instances/production/local/lib/python2.7/site-packages/dashboard_app/models.py", line 483, in deserializeself._do_deserialize(prefer_evolution)
  File "/srv/lava/instances/production/local/lib/python2.7/site-packages/dashboard_app/models.py", line 504, in _do_deserializehelper.deserialize(self,prefer_evolution)
  File "/srv/lava/instances/production/local/lib/python2.7/site-packages/dashboard_app/helpers.py", line 757, in deserializeimporter().import_document(s_bundle,doc)
  File "/srv/lava/instances/production/local/lib/python2.7/site-packages/dashboard_app/helpers.py", line 62, in import_documentself._import_sanity_check(doc)
  File "/srv/lava/instances/production/local/lib/python2.7/site-packages/dashboard_app/helpers.py", line 95, in _import_sanity_checkraiseValueError("A test with UUID {0} already exists".format(analyzer_assigned_uuid))ValueError: A test with UUID 2600f98a-4f00-11e1-98b8-376b2c52277f already exists

The above error shows that the tests are failing because of duplicate uuid.
The uuid are not part of the json file the is submitted for test, hence it must be something which the lava assigns automatically.
This is blocking the beagle board testing for quite sometime now and needs to be fixed ASAP.

[Zygmunt Krynicki (zyga)]

I think we need to change how uuids are generated when the dispatcher is used. IMHO we should return to uuid1() - based on MAC and current time and pass the UUID to the lava-test invocation.

[Paul Larson (pwlars)]

Deepti, just out of curiosity, can you point to some of the test runs where you saw this happening?