Description of problem:
Tempest tests checking os_inherits are failing due to that extension being disabled in keystone.conf:
[os_inherit] # # From keystone # # role-assignment inheritance to projects from owning domain or from projects # higher in the hierarchy can be optionally enabled. (boolean value) #enabled = false
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy an openstack installation with packstack
2. Run tempest keystone v3 admin tests
Actual results: v3 identity os-inherit related tests are failing
Expected results: for them to pass
Fix: Setting the os_inherit enabled to true and restarting keystone serves as a workaround.
can i have acks for this bug?
Testing attached workaround
AFAICT upstream default is false and you say we should have it enabled by default?
@ayoung Are there any downsides? If not, we could make it distro default in keystone-dist.conf
IN this case, Tempest is at fault, not Keystone. The Branchless Tempest is testing against the Liberty branch, but assuming a default from Mitaka.
Leave the default as is, and , if you want to make the Tempest test pass, explicitly set the option to be enabled prior to running the test.
Hi Adam, I was debugging the issue with your comment in mind and this issue is fixed by performing the service discovery on the identity service as well, so it would be skipped if such option is not available.
The attached patch in the api_discovery library for the tempest config tool should make this pass, therefore I'm switching this bug from keystone to tempest.
If in keystone.conf is section os_inherit set to false:
enabled = false
it's needed to edit tempest.conf - in [identity-feature-enabled] section must be OS-INHERIT removed from api_extensions list, then tempest will skip tests related to it and they will pass.