Tempest test fails due to keystone policy, tempest.lib.exceptions.Forbidden: Forbidden
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Keystone Charm |
Fix Released
|
High
|
Bas de Bruijne |
Bug Description
This tempest test, when used from the upstream plugin fails due to keystone policy:
octavia_
-------
Traceback (most recent call last):
File "/home/
raise value.with_
File "/home/
cls.
File "/snap/
**params)
File "/home/
resp, body = self.get(url)
File "/home/
return self.request('GET', url, extra_headers, headers)
File "/home/
self.
File "/home/
raise exceptions.
tempest.
Details: {'code': 403, 'message': 'You are not authorized to perform the requested action: identity:
-------
Snippets of keystone policy for this action:
-------
"admin_
"cloud_admin": "rule:admin_
"admin_
"admin_
"admin_
"identity:
-------
Tempest definitely gets the Admin role, I'm not sure why it fails the other rules. It might be a bug or wrong setting in tempest. Commands from the CLI have no problems.
Tempest might be asking for a token from one domain and attempting to list role assignments from another domain, but I can't find proof of this in the logs.
I am wondering if the keystone policy is too strict for the tempest test.
tags: | added: cdo-tempest |
Changed in charm-keystone: | |
importance: | Undecided → High |
Changed in charm-keystone: | |
status: | Fix Committed → Fix Released |
assignee: | Alex Kavanagh (ajkavanagh) → Bas de Bruijne (basdbruijne) |
Possibly duplicate of https:/ /bugs.launchpad .net/charm- keystone/ +bug/1830076
1830076 has overlapping keystone policy rule:cloud_admin