)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"erkin.mussurmankulov@ps.kz","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"a57cf6955e5a82da9bedca53d67999563265e40d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"605c3f99_1ff10379","updated":"2026-10-30 15:42:01.000000000","message":"Hello! Thank you for the contribution and for the well-prepared and robust MR. LGTM and ready to merge.\n\nIt\u0027s a pity that we don\u0027t have Tempest scenarios with federated users involved, and this bug slipped through, but we got what we got, and let\u0027s move on 😅\n\nYou\u0027re right that there is no internal logic using `trove_user_id_*` tags yet. So clouds with federation users enabled will not be able to use these tags because they will not be set. I think that\u0027s not a big problem by itself.","commit_id":"c9851c063522fe6916333f557350ee5643a0bd38"}]}