Can't create an artifact when other artifact is activating

[Mike Fedosin]

When trying to update status of two different artifacts I got an error:

Cause : Glare Error - [ {"explanation": "There was a conflict when trying to complete your request.", "code": 409, "error":
{"message": "Cannot lock an item with key CloudBandNetworkDirector. Lock already acquired by other request", "type": "Conflict"}
, "title": "Conflict"} ]

It happens because glare sets unnecessary global lock on whole user scope when modifying the status.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/507909
Committed: https://git.openstack.org/cgit/openstack/glare/commit/?id=d2ce390ca83c60b20a1f2b75205ab34d416284fe
Submitter: Zuul
Branch: master

commit d2ce390ca83c60b20a1f2b75205ab34d416284fe
Author: Mike Fedosin <email address hidden>
Date: Wed Sep 27 18:55:37 2017 +0300

    Revert scoped lock format

    Recently scoped lock format was mistakenly changed
    from "type_name:name:version" to "owner". New format
    prevents simultaneuos modifications of different
    artifacts by one tenant, because it locks the whole
    tenant scope, not just a single artifact.

    For this reason it's suggested to revert the format as
    it was before.

    Closes-bug: #1720139

    Change-Id: I9dc26da85f424a4ced1ca232d1f33c548b602f0f

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/508846

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/508846
Committed: https://git.openstack.org/cgit/openstack/glare/commit/?id=5c0139f2bc3a0e4883d30bd60bfaab90c6917524
Submitter: Zuul
Branch: stable/pike

commit 5c0139f2bc3a0e4883d30bd60bfaab90c6917524
Author: Mike Fedosin <email address hidden>
Date: Wed Sep 27 18:55:37 2017 +0300

    Revert scoped lock format

    Recently scoped lock format was mistakenly changed
    from "type_name:name:version" to "owner". New format
    prevents simultaneuos modifications of different
    artifacts by one tenant, because it locks the whole
    tenant scope, not just a single artifact.

    For this reason it's suggested to revert the format as
    it was before.

    Closes-bug: #1720139

    Change-Id: I9dc26da85f424a4ced1ca232d1f33c548b602f0f
    (cherry picked from commit d2ce390ca83c60b20a1f2b75205ab34d416284fe)