)]}'
{"tempest/tests/compute/__init__.py":[{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"27be9a600701ccc1f1735445aeb39d9b2b9353ac","unresolved":false,"context_lines":[{"line_number":67,"context_line":"    # users (config.compute.allow_tenant_isolation is true,"},{"line_number":68,"context_line":"    # then we allow multi-user."},{"line_number":69,"context_line":"    if not CONFIG.compute.allow_tenant_isolation:"},{"line_number":70,"context_line":"        MULTI_USER \u003d False"},{"line_number":71,"context_line":"    else:"},{"line_number":72,"context_line":"        user1 \u003d CONFIG.identity.username"},{"line_number":73,"context_line":"        user2 \u003d CONFIG.identity.alt_username"}],"source_content_type":"text/x-python","patch_set":1,"id":"AAAAM3%2F%2B49o%3D","line":70,"updated":"2013-02-15 13:28:21.000000000","message":"No, this is incorrect. MULTI_USER variable is a switch that indicates whether there are two distinct user credentials available. In the case of allow_tenant_isolation, the Keystone admin is used to create users and therefore, it is guaranteed that mutliple distinct users will be available.\n\nIn the case when allow_tenant_isolation is false, then we must rely on the values of username and alt_username being different (and being existing users). This is what this block checks, and the change in logic above is incorrect.","commit_id":"12b854149091a4f26df92975481430288acd10ee"}]}