Open Stack

There may be some other lingering v2-only auth issues, but my guess is that the nova/neutron one is towards the end of the remaining ones. 

I'm looking at liberty as the release we finish any outstanding work to fully gate on v2 being disabled in a deployment. 

--Morgan 

Sent via mobile

> On Apr 3, 2015, at 15:24, Fox, Kevin M <Kevin.Fox at pnnl.gov> wrote:
> 
> Yeah. I'm curious too.
> 
> Also, are you aware of any other issues in Juno with switching entirely over to v3? We'd like to have all of our service accounts in a non-default domain for kilo. With the nova+neutron bug fixed, thats the only one I know of preventing it.
> 
> Thanks,
> Kevin
> From: Rich Megginson [rmeggins at redhat.com]
> Sent: Friday, April 03, 2015 12:54 PM
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] Problem about Juno Keystone Identity V3
> 
>> On 04/03/2015 12:11 PM, Fox, Kevin M wrote:
>> We've run into issues with nova+neutron and keystone v3 with Juno.
>> 
>> Specifically this one:
>> https://bugs.launchpad.net/nova/+bug/1424462
>> 
>> But there may be others that I don't know about.
> 
> Yes, there are some problems with some components that don't use the keystone_authtoken section in their configs or otherwise can't use the latest python-keystonemiddleware.
> 
> But I would like to know what steps worked to switch Keystone Identity from V2 to V3 in Icehouse that don't work for Juno.
> 
>> 
>> Thanks,
>> Kevin
>> 
>> From: Rich Megginson [rmeggins at redhat.com]
>> Sent: Friday, April 03, 2015 10:52 AM
>> To: openstack-dev at lists.openstack.org
>> Subject: Re: [openstack-dev] Problem about Juno Keystone Identity V3
>> 
>>> On 04/03/2015 09:09 AM, Amy Zhang wrote:
>>> Hi guys,
>>> 
>>> I have done switching Keystone Identity V2 to V3 in Icehouse and it works perfect. However, I use the same way to switch Keystone Identity V2 to V3 in Juno, it doesn't work. It give me the error: "ERROR: openstack Internal Server Error (HTTP 500)".
>> 
>> What steps did you follow?  Links?
>> 
>>> 
>>> I traced back to the code, find the error comes from apache, but it doesn't make any sense that apache has problem, it might be some problem of keystone which lead to error of apache. 
>>> 
>>> Does any one have any idea of it? Thanks!
>>> -- 
>>> Best regards,
>>> Amy (Yun Zhang)
>>> 
>>> 
>>> __________________________________________________________________________
>>> 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
>> 
>> 
>> 
>> __________________________________________________________________________
>> 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
> 
> __________________________________________________________________________
> 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/20150403/b343f417/attachment.html>