Open Stack

On Mon, May 15, 2017 at 2:51 PM Hemanth N <mail2hemanth.n at gmail.com> wrote:

> Hi
>
> I have written new Tempest functional test cases for Identity OAUTH API.
> https://review.openstack.org/#/c/463240/
>
>
> This patch have dependency on a keystone fix that is still under
> review and I have mentioned this patch as Depends-On for above one.
> (https://review.openstack.org/#/c/464577/)
>
> The gates with stable releases are failing but on master it is successful
> gate-tempest-dsvm-neutron-full-ubuntu-xenial-ocata
> gate-tempest-dsvm-neutron-full-ubuntu-xenial-newton
>
> I am assuming the stable releases will cherry-pick the Depends-On
> patches and then builds/verifies the environment.
> Is my understanding correct?
>

Your change is for keystone master, and it won't be automatically
cherry-picked.


> If not, how should I proceed in such scenarios.
>

Your change make it possible to use the oath API in deployments where TLS
is terminated in front of the API server. I would use a feature flag on
Tempest side
to indicate whether this keystone feature is available. Default to false,
 set to true in Pike
in devstack, skip the tests if the feature is not available.

Even if your change was back ported, merging this would immediately enforce
the new behaviour on all Netwton+ clouds, to I think having a feature flag
would be
useful anyways.

andrea


> Thanks in Advance.
>
> Best Regards,
> Hemanth
>
> __________________________________________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170515/bc81d2e7/attachment.html>