This appears to be a valid bug -- we were concerned with v2-v3
token interop when v3 auth merged, but I thought we had ironed out the
kinks (we have several related tests in tests/test_v3_auth.py for this
reason). I targeted the bug at RC1 as we need to have this fixed for v3 to
be useful in grizzl
[Openstack] Possible keystone/common/controller.py Token Bug
So I've filed a bug on launchpad[1] about the issue discussed in the
thread[2] with this subject (sorry, I subscribed after the message went
out, so this message isn't properly threaded).
Is it really legit? The discussion sto
So I've filed a bug on launchpad[1] about the issue discussed in the
thread[2] with this subject (sorry, I subscribed after the message went
out, so this message isn't properly threaded).
Is it really legit? The discussion stopped abruptly. It seems like a
pretty major bug; I can't do much wit
asking
about compatibility.
Mark
From: Dolph Mathews [mailto:dolph.math...@gmail.com]
Sent: Friday, March 01, 2013 4:46 PM
To: Miller, Mark M (EB SW Cloud - R&D - Corvallis)
Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net); Yee, Guang
Subject: Re: [Openstack] Possible keys
Looks like a valid bug to me -- this code just merged a week ago.
How did you create the token? I'm guessing it was generated by v2 and
utilized here on v3?
-Dolph
On Fri, Mar 1, 2013 at 5:03 PM, Miller, Mark M (EB SW Cloud - R&D -
Corvallis) wrote:
> Hello,
>
> ** **
>
> In trying to u
5 matches
Mail list logo
