Re: [openstack-dev] [Keystone][Tempest] OS-INHERIT APIs were skipped by Jenkins because "os_inherit" in keystone.conf was disable.

Hi Henry, When adding this extension on https://review.openstack.org/#/c/35986/ , the extension is disabled as the default setting. Now can we enable this os_inherit extension on Keystone side like keystone/common/config.py 'os_inherit': [ - cfg.BoolOpt('enabled', default=False, +

Re: [openstack-dev] [Keystone][Tempest] OS-INHERIT APIs were skipped by Jenkins because "os_inherit" in keystone.conf was disable.

A devstack patch is https://review.openstack.org/#/c/257085/ for enabling os_inherit extension. 2015-12-14 10:43 GMT+09:00 Ken'ichi Ohmichi : > Hi Henry, > > When adding this extension on https://review.openstack.org/#/c/35986/ > , the extension is disabled as the default

Re: [openstack-dev] [Keystone][Tempest] OS-INHERIT APIs were skipped by Jenkins because "os_inherit" in keystone.conf was disable.

Hi Maho, So in the keystone unit tests, we flip the os_inherit flag back and forth during tests to make sure it is honored correctly. For the tempest case, I don’t think you need to do that level of testing. Setting the os_inherit flag to true will have no effect if you have not created any

[openstack-dev] [Keystone][Tempest] OS-INHERIT APIs were skipped by Jenkins because "os_inherit" in keystone.conf was disable.

Hi all, I pushed the patch set of OS-INHERIT API tempest (keystone v3). https://review.openstack.org/#/c/250795/ But, all API tests in patch set was skipped, because "os_inherit" in keystone.conf of Jenkins jobs was disable. So, it couldn't be confirmed. Reference information :