In this case it is reproduced with 'tox -e func-target focal-ussuri' but can likely be reproduced on (m)any releases.
Info from Chris M. He says this can be resolved by going back from master to the released version (as a workaround). The problem is the admin user we get doesn't have system scope. It is probably the case that we can resolve it by updating how we get our overcloud admin credentials
setUpClass (octavia_tempest_plugin.tests.scenario.v2.test_traffic_ops.TrafficOperationsScenarioTest)
----------------------------------------------------------------------------------------------------
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/tmp/charmed-openstack-tester/.tox/func-target/lib/python3.8/site-packages/tempest/test.py", line 181, in setUpClass
raise value.with_traceback(trace)
File "/tmp/charmed-openstack-tester/.tox/func-target/lib/python3.8/site-packages/tempest/test.py", line 166, in setUpClass
cls.setup_credentials()
File "/tmp/charmed-openstack-tester/.tox/func-target/lib/python3.8/site-packages/octavia_tempest_plugin/tests/test_base.py", line 149, in setup_credentials
roles = cls.os_admin.role_assignments_client.list_role_assignments(
File "/tmp/charmed-openstack-tester/.tox/func-target/lib/python3.8/site-packages/tempest/lib/services/identity/v3/role_assignments_client.py", line 46, in list_role_assignments
resp, body = self.get(url)
File "/tmp/charmed-openstack-tester/.tox/func-target/lib/python3.8/site-packages/tempest/lib/common/rest_client.py", line 314, in get
return self.request('GET', url, extra_headers, headers)
File "/tmp/charmed-openstack-tester/.tox/func-target/lib/python3.8/site-packages/tempest/lib/common/rest_client.py", line 703, in request
self._error_checker(resp, resp_body)
File "/tmp/charmed-openstack-tester/.tox/func-target/lib/python3.8/site-packages/tempest/lib/common/rest_client.py", line 804, in _error_checker raise exceptions.Forbidden(resp_body, resp=resp)
tempest.lib.exceptions.Forbidden: Forbidden
Details: {'code': 403, 'message': 'You are not authorized to perform the requested action: identity:list_role_assignments.', 'title': 'Forbidden'}
In this case it is reproduced with 'tox -e func-target focal-ussuri' but can likely be reproduced on (m)any releases.
Info from Chris M. He says this can be resolved by going back from master to the released version (as a workaround). The problem is the admin user we get doesn't have system scope. It is probably the case that we can resolve it by updating how we get our overcloud admin credentials