Arvados

We've been seeing CR logs with messages like this:

2017-03-01T17:31:40.739323663Z While creating log collection: arvados API server error: #<PG::UniqueViolation: ERROR:  duplicate key value violates unique constraint "index_collections_on_owner_uuid_and_name" 
2017-03-01T17:31:40.739323663Z DETAIL:  Key (owner_uuid, name)=(tb05z-tpzed-000000000000000, logs for tb05z-dz642-eie1eal1059y9bb) already exists.

If for some reason the process quits after writing the log collection, the next time that is retried, it will cause a PG::UniqueViolation error.

Should be a matter of using the ensure_unique_name flag.

LGTM.

11166-log-name-collision @ cb0b666f86ce87d35667e8e23e3775b703a37841