)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":21129,"name":"Alan Bishop","email":"abishopsweng@gmail.com","username":"ASBishop","status":"ex Red Hat"},"change_message_id":"2bc523ae755b7f53758e6156a9eede927edb305c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b9c6b2e5_c170b8fd","updated":"2022-09-09 15:52:22.000000000","message":"-2 if I could :-/\n\nFirst of all, Ia3f414c4b9b0829f60 only adds the creator role to the cinder service. It does not add the role to the users that tempest uses when running tests.\n\nThere is a patch that tells tempest to include the create role, and that\u0027s I2023df6ce212bd9c455fa04a43419c6760e22267. You can see that here [1]\n\n[1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_728/855272/1/check/cinder-tempest-plugin-lvm-lio-barbican/72821f7/controller/logs/tempest_conf.txt\n\nBut, notice auth/tempest_roles *only* lists creator, and it doesn\u0027t include the member role. This causes lots of stuff the fail, and it looks to be the source of the 403 error thrown by swift in the c-bak log [2].\n\n[2] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_728/855272/1/check/cinder-tempest-plugin-lvm-lio-barbican/72821f7/controller/logs/screen-c-bak.txt\n\nLooking at tempest itself, it seems if auth/tempest_roles is configured then it assumes *all* the roles are listed. You don\u0027t get the member role for free unless auth/tempest_roles is left blank.\n\nMy conclusion is that [1] may be well intended, but it ends up limiting tempest to only the creator role, and that doesn\u0027t work because tempest also needs the member role. That\u0027s why this .zuul.yaml had to override the setting, to ensure both roles are present.","commit_id":"0386f0042a962fcfed248a82c81086ce3372f841"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"569a6239689c32851fad8c91b3da9ba5aaa46d4d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c24d659b_06fc5de5","updated":"2022-09-01 12:45:39.000000000","message":"Looks like my theory here is incorrect.","commit_id":"0386f0042a962fcfed248a82c81086ce3372f841"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"2d2d334bde214385545fb707ec21652cf96001bd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7317eacd_ddcafe83","updated":"2022-08-31 14:17:14.000000000","message":"recheck cinder-tempest-plugin-lvm-lio-barbican - don\u0027t think it\u0027s caused by this patch, the failures are a bunch of backup tests, the tests that use barbican to handle encryption keys are passing","commit_id":"0386f0042a962fcfed248a82c81086ce3372f841"},{"author":{"_account_id":21129,"name":"Alan Bishop","email":"abishopsweng@gmail.com","username":"ASBishop","status":"ex Red Hat"},"change_message_id":"eb63df7303af11e5b48276579a289796a9727aed","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7107f7d3_b5cb1223","in_reply_to":"b9c6b2e5_c170b8fd","updated":"2022-09-23 13:08:24.000000000","message":"Sorry, meant to say I2023df6ce212bd9c455fa04a43419c6760e22267 is well intended.\n\nhttps://review.opendev.org/c/openinfra/python-tempestconf/+/706646/12/.zuul.yaml#170","commit_id":"0386f0042a962fcfed248a82c81086ce3372f841"}]}