Hi Alex,

Manually creating a loadbalancer (when policy.json is in its place) worked as expected.

The problem lays in the tempest plugin config you used:
Looking at the traceback you posted in comment #9, it shows that the issue it is failing at is on is with the setUpClass and specifically at setup_credentials()[1]. This is using the default credentials list[2] for the setup process.

Those defaults assume values that fit Octavia RBAC[3] which we currently don't use[4]. Thus, you should configure the roles tempest will use to match the policy.json[5] file we use.

This should look as follows:

[load_balancer]
member_role = _member_
admin_role = admin

/Nir

[1] https://github.com/openstack/octavia-tempest-plugin/blob/008dbec2ad45c6c68ae278a3f433cea1c754eece/octavia_tempest_plugin/tests/test_base.py#L85
[2] https://github.com/openstack/octavia-tempest-plugin/blob/008dbec2ad45c6c68ae278a3f433cea1c754eece/octavia_tempest_plugin/tests/test_base.py#L46
[3] https://docs.openstack.org/octavia/latest/configuration/policy.html
[4] https://review.rdoproject.org/r/#/c/13767/
[5] https://github.com/openstack/octavia/blob/master/etc/policy/admin_or_owner-policy.json

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2086