)]}'
{"zun/api/controllers/v1/containers.py":[{"author":{"_account_id":11536,"name":"hongbin","email":"hongbin034@gmail.com","username":"hongbin"},"change_message_id":"38ce3ec987059468d9b49b7defec1ef280d9f611","unresolved":false,"context_lines":[{"line_number":583,"context_line":"        if \u0027name\u0027 in patch:"},{"line_number":584,"context_line":"            patch[\u0027name\u0027] \u003d str(patch[\u0027name\u0027])"},{"line_number":585,"context_line":"            if container.name \u003d\u003d patch[\u0027name\u0027]:"},{"line_number":586,"context_line":"                raise exception.Conflict(\u0027The new name for the container is \u0027"},{"line_number":587,"context_line":"                                         \u0027the same as the old name.\u0027)"},{"line_number":588,"context_line":"        context \u003d pecan.request.context"},{"line_number":589,"context_line":"        compute_api \u003d pecan.request.compute_api"}],"source_content_type":"text/x-python","patch_set":1,"id":"bf659307_a516d0f0","line":586,"range":{"start_line":586,"start_character":16,"end_line":586,"end_character":21},"updated":"2018-04-10 00:00:05.000000000","message":"@Shengqin,\n\nIs there any reason to raise this exception? By looking at other OpenStack services such as nova and neutron, they didn\u0027t raise any exception for renaming a resource with the same name. Therefore, my default position is not to raise this exception for consistency with other services. Perhaps, we could simply return instead?","commit_id":"44b59c56dc5438d80fa76b854e30efe5b64a6604"}]}