Open Stack

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 role assignments that are inherited - you’ll just get the regular assignments back as normal. So provided there is no test data leakage between tests (i.e. old data lying around from a previous test), I think it should be safe to run tempest with os_inherit switched on.

Henry
> On 9 Dec 2015, at 08:45, koshiya maho <koshiya.maho at po.ntts.co.jp> wrote:
> 
> 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 : 
> http://logs.openstack.org/95/250795/5/check/gate-tempest-dsvm-full/fbde6d2/logs/etc/keystone/keystone.conf.txt.gz
> #L1422
> https://github.com/openstack/keystone/blob/master/keystone/common/config.py#L224
> 
> Default "os_inherit" setting is disable. OS-INHERIT APIs need "os_inherit" setting enable.
> 
> For keystone v3 tempests using OS-INHERIT, we should enable "os_inherit" of the existing keystone.conf called by Jenkins.
> Even if "os_inherit" is enable, I think there have no effects on other tempests.
> 
> Do you have any other ideas?
> 
> Thank you and best regards,
> 
> --
> Maho Koshiya
> NTT Software Corporation
> E-Mail : koshiya.maho at po.ntts.co.jp
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev