Public bug reported:
There are 3 primary places where client can be configured to reference
domains. The actual parameter names vary based on the configuration
interface (a function's arguments, the env, CLI arguments, etc), but
I'll use environment variables here for the sake of general familiari
The keystoneclient session is trying to work with a null URL. Adding
Jamie.
** Project changed: keystone => python-keystoneclient
** Changed in: python-keystoneclient
Importance: Undecided => Medium
** Changed in: python-keystoneclient
Status: New => Triaged
--
You received this bug
I'm going to assume you're on a stable/kilo or older release of
Keystone, but I'll refer to master's setup.cfg as well. If you got that
configuration value from documentation somewhere, then we need to re-
open this as a doc bug.
Basically, you've set the trust driver to be a revocation driver, wh
We can use this ticket (I've added openstack-manuals to it), but I don't
see anywhere on that page that it says to configure [trust] driver?
[revoke] driver is mentioned, but it's value is correct.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Changed in: opens
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Also affects: keystone/liberty
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Status: New => Triaged
** Changed in: keystone/kilo
Importance: Undecided => High
** Changed in: keysto
** Also affects: keystoneauth
Importance: Undecided
Status: New
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.la
Added cinder.
** Also affects: cinder
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1509683
Title:
sometimes the sheep
https://review.openstack.org/#/c/158720/ (merged) closes bug 1425113.
https://review.openstack.org/#/c/158731/ closes this bug, but was
abandoned in favor of merging that patch into
https://review.openstack.org/#/c/158372/ which has not merged.
** Changed in: keystone
Status: Fix Released
yanyao: What did the keystone logs say to indicate a relationship to
Fernet?
** Also affects: keystone
Importance: Undecided
Status: New
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Invalid
** Changed in: keys
** Also affects: keystone/havana
Importance: Undecided
Status: New
** Tags removed: activedirectory havana-backport-potential
** Tags added: ldap
** Changed in: keystone/havana
Status: New => In Progress
** Changed in: keystone/havana
Assignee: (unassigned) => Adam Young (a
as compared to what we're producing today:
{"key":"value"}
... as compared to all unnecessary whitespace removed:
{"key":"value"}
This optimization would save us a few bytes in both PKI and PKIZ tokens.
** Affects: keystone
Importance: Wish
** Changed in: python-keystoneclient
Milestone: None => 0.10.1
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.
** Project changed: keystone => openstack-api-site
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1346210
Title:
keystone v2.0 API docs reported with invalid information
Status in Open
fault token provider for Juno.
** Affects: keystone
Importance: Wishlist
Assignee: Dolph Mathews (dolph)
Status: Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/13
** No longer affects: keystone
** Changed in: keystonemiddleware
Importance: Undecided => Wishlist
** Changed in: keystonemiddleware
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https
I'm not sure if Keystone or Horizon is at fault here, so I've added both
as Incomplete.
The user may have been created successfully, but keystone will also
attempt to assign the _member_ role to the user in the user's default
tenant (the user.tenant_id attribute in v2, or user.default_project_id
i
I'd say this is Won't Fix for v2.0. You can use custom logging levels in
eventlet.wsgi.server to suppress this class of logs altogether, but our
solution to the "tokens in URLs" problem was solved by introducing v3
which does not do that - we can't change the v2 API, and I'm not sure
it's a good id
This must have been fixed elsewhere.
** Changed in: devstack
Status: New => Invalid
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchp
https://review.openstack.org/#/c/108406/
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Triaged
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keystone
Status: Triaged => Fix Committed
** Cha
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1349792
Title:
nova-client return Unauthorized (HTTP 401) when provider is
This looks like it's an issue between devstack and openstackclient. This
was filed months ago though, is it still an issue?
** Project changed: keystone => devstack
** Changed in: devstack
Status: New => Incomplete
** Also affects: python-openstackclient
Importance: Undecided
St
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
** Changed in: keystone/icehouse
Status: New => In Progress
** Changed in: keystone/icehouse
Importance: Undecided => Medium
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keyston
There's not a single ERROR level log there from Keystone - this looks to
be coming from apache's log config in devstack?
** Project changed: keystone => devstack
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bu
Actually, I totally overlooked that the request was in the logs, to POST
/v2.0/tokens. There should not be an X-Auth-Token in a request to POST
/v2.0/tokens anyway, so that's completely normal. The rest of the logs
in the problem description are also completely normal, so far as I can
tell.
Withou
I'm going to ignore the mentions of "firstname" and "lastname", since
the patch above ignores them as well.
Up until now, a user's email address has been considered metadata on the
user that Keystone itself makes no guarantees or assumptions about. If
email is to be a first class attribute, I'd li
Comparing just the method difference with curl, I'm not able to
reproduce this. Further, this behavior matches our understanding of
HEAD. The non-zero Content-Length basically indicates to the client how
large the response body would be in a normal GET request.
$ curl http://localhost:35357/v3/gro
The functional tests here exercise the SQL backend, which is the only
backend we have:
https://github.com/openstack/keystone/blob/master/keystone/tests/test_v3_credential.py
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Y
*** This bug is a duplicate of bug 967832 ***
https://bugs.launchpad.net/bugs/967832
** This bug has been marked a duplicate of bug 967832
Resources owned by a project/tenant are not cleaned up after that project is
deleted from keystone
--
You received this bug notification because you
+1 for documenting the behavior, along with pretty much everything else
in keystoneclient.common.cms
** Project changed: keystone => python-keystoneclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.laun
I agree, the documentation should be fixed for this.
** Tags added: identity-api
** Project changed: keystone => openstack-api-site
** Changed in: openstack-api-site
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
** Changed in: keystone/icehouse
Importance: Undecided => Medium
** Also affects: keystone/grizzly
Importance: Undecided
Status: New
** Changed in: keystone/grizzly
Status: New => Fix Committed
** Changed in: keystone/grizzly
Importance: Undecided => Medium
** Changed in:
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Tags added: identity-api
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1334368
Title:
HEAD and GET i
Closing this because it's not a bug (there's nothing to reproduce), but
subscribing Marek and Steve who should be able to help you out.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
Leaving this as Opinion for the moment, because this was actually by
design (although, I personally disagree with the behavior illustrated
above). Going to mention this at the Keystone meeting today.
** Changed in: keystone
Status: New => Opinion
--
You received this bug notification beca
In one request, you're referencing a role by name ("member", which is
valid), and in another request, you're trying to get a role by ID - and
there's certainly no role with id=member (id's are generally UUIDs).
GET /v3/roles?name=member should allow you to find the role ID by name.
** Changed in:
Adding keystone here then, so we can switch from the shell version
(which does not work on OS X) to the python version (which does work on
OS X).
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Triaged
** Changed in: keystone
This is certainly expected behavior - Henry's explanation looks spot on,
and (2) explains the justification for the current behavior.
** Changed in: keystone
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
*** This bug is a duplicate of bug 871822 ***
https://bugs.launchpad.net/bugs/871822
This almost looks like a bug in Eventlet, or perhaps just poor feedback
from eventlet about the state of the machine it's running on? In
Keystone's case, you could avoid this by deploying to Apache httpd
inste
*** This bug is a duplicate of bug 871822 ***
https://bugs.launchpad.net/bugs/871822
This is identical to bug 871822, regardless of the project consuming
eventlet.
** This bug has been marked a duplicate of bug 871822
nova-api crashed with input/output error
--
You received this bug noti
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1347891
Title:
mis-use of XML canonicalization in keystone
Public bug reported:
This is a regression of an old issue, which I thought was resolved by
the "SELECT 1;" hack, but perhaps recently reintroduced with oslo.db?
[Mon Aug 25 14:30:54.403538 2014] [:error] [pid 25778:tid 139886259214080]
25778 ERROR keystone.common.wsgi [-] (OperationalError) (200
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Assignee: (unassigned) => Sergey Kraynev (skraynev)
** Changed in: python-keystoneclient
Status: New => In Progress
--
You received this bug notification because y
Public bug reported:
Contrary to bug 1285478, requirements files should not be sorted
alphabetically. Given that requirements files can contain comments, I'd
suggest a header in all requirements files along the lines of:
# The order of packages is significant, because pip processes them in the or
See bug 1365061 instead.
** Changed in: blazar
Status: Triaged => Invalid
** Changed in: glance
Status: In Progress => Invalid
** Changed in: keystone
Status: In Progress => Invalid
** Changed in: trove
Status: In Progress => Invalid
** Changed in: python-cinderclie
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Also affects: keystonemiddleware
Importance: Undecided
Status: New
** Changed in: keystone
Assignee: (unassigned) => Dolph Mathews (dolph)
** Changed in: python-keystoneclient
Assig
** Also affects: neutron
Importance: Undecided
Status: New
** Also affects: horizon
Importance: Undecided
Status: New
** Also affects: swift
Importance: Undecided
Status: New
** Changed in: horizon
Status: New => Fix Committed
** No longer affects: horizon
This has been addressed on the Keystone side with the above BP.
** Changed in: keystone
Status: Triaged => Invalid
** Changed in: keystone
Milestone: juno-3 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keyst
Public bug reported:
If a project or endpoint group is deleted, the endpoint grouping
extension should respond by deleting associated data. Instead, stale
data remains in the backend.
** Affects: keystone
Importance: Medium
Assignee: Bob Thyne (bob-thyne)
Status: In Progress
-
This looks like it was a packaging issue. If it's still a problem, I'd
suggest filing it against centos / RDO.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https:/
** Changed in: keystone
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1252341
Title:
Horizon crashes when removing logged user from project
Statu
I stand corrected. Keystone has the fix above in master as of 94efafd6
https://review.openstack.org/#/c/114863/
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
Public bug reported:
Our last sync with openstack/requirements was around the beginning of
August. We haven't been able to sync because we have unit test failures
on the sync job since around August 20th:
https://review.openstack.org/#/c/111620/
Likely, our tests need to be fixed to support wh
*** This bug is a duplicate of bug 1347891 ***
https://bugs.launchpad.net/bugs/1347891
** This bug has been marked a duplicate of bug 1347891
mis-use of XML canonicalization in keystone tests
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
PKI is optional, hence it's an extension. Albeit, they are basically
only used for PKI, so a PKI namespace would have been preferable.
** Changed in: keystone
Status: New => Invalid
** Tags added: pki
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
** Changed in: keystone
Importance: Undecided => Low
** Changed in: keystone
Status: New => Triaged
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Tags added: low-hanging-fruit
--
You received this bug notification because you are a member of Yahoo
*** This bug is a duplicate of bug 1230279 ***
https://bugs.launchpad.net/bugs/1230279
** This bug has been marked a duplicate of bug 1230279
malformed endpoint URLs are destroying the API
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Project changed: keystone => horizon
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1365458
Title:
Keystone auth needs a way to propogate some error message base
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1361378
Title:
"MySQL server has gone away" again
Status in OpenStack Identity (Key
We'd also have to not allow the current user to delete themselves, nor
the user to remove their last role assignment from the current scope,
etc. I'm all in favor of UX, but I also prefer the power to shoot myself
in the foot if I so choose. If we "fixed" this, I guarantee we'd get a
subsequent bug
*** This bug is a duplicate of bug 1312221 ***
https://bugs.launchpad.net/bugs/1312221
** This bug has been marked a duplicate of bug 1312221
Add user objects to mapping rules examples in OS-FEDERATION docs
--
You received this bug notification because you are a member of Yahoo!
Engineeri
This isn't a useful bug report, especially given that there's no useful
information here about the actual typo you're referring to. Happy to see
typos fixed without a bug report.
** Changed in: keystone
Importance: Undecided => Low
** Changed in: keystone
Status: In Progress => Invalid
Fixed in
https://review.openstack.org/#/c/118913/1/keystone/common/base64utils.py
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/b
A fix is gating that's not referencing a bug:
https://review.openstack.org/#/c/117902/
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.
This was already fixed somewhere without being tracked correctly.
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1363319
Tit
** Also affects: ossn
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1331882
Title:
trustor_user_id not available in v2 trust token
Status i
*** This bug is a duplicate of bug 1294994 ***
https://bugs.launchpad.net/bugs/1294994
** This bug has been marked a duplicate of bug 1294994
Managers instantiated multiple times
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1294994
Title:
Managers instantiated multiple times
Status
Unassigning due to inactivity.
** Changed in: keystone
Assignee: Tomasz Paszkowski (ss7pro) => (unassigned)
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
** Changed in: keystone
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1187257
Title:
List project users not implemented in V3 API
Status in
Makes sense! Thanks.
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1101287
Title:
Keystone LDAP does not support v3 Role Gran
This is not reproducible against mysql AFAICT, which leads me to believe
this is somehow the fault of sqlite (or the specific version I'm
using).. not in how we're using it (because we're working with mysql in
the same manner).
$ sqlite3 --version
3.7.12 2012-04-03 19:43:07 86b8481be7e7692
This is not reproducible against mysql AFAICT, which leads me to believe
this is somehow the fault of sqlite (or the specific version I'm
using).. not in how we're using it (because we're working with mysql in
the same manner).
$ sqlite3 --version
3.7.12 2012-04-03 19:43:07 86b8481be7e7692
*** This bug is a duplicate of bug 967832 ***
https://bugs.launchpad.net/bugs/967832
Adding glance to bug 967832 and broadening the scope of that bug as a
result.
** This bug has been marked a duplicate of bug 967832
Instances are still running when a tenant are deleted
--
You received t
Assuming this is now invalid - reopen if I'm mistaken!
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1195019
Title:
GET /role
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1187198
Title:
V3 policy engine does not support domain isolation of roles whi
There's no reason to avoid changing the status of a bug if it's known to
be inaccurate. Discussion can still occur here and the permalink will
work either way.
I assume Adam is correct... you can workaround an old package by simply
installing the latest version of keystoneclient from pypi:
> pi
Opening against master to forward port tests.
** Changed in: keystone
Status: Invalid => Triaged
** Changed in: keystone
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https:
** Changed in: keystone
Status: New => Opinion
** Changed in: keystone
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1224638
Title:
Conside
get_user_by_name() is exposed to the v2.0 API via:
GET /v2.0/users?name={user_name}
(but it doesn't make sense on the v3 API without a domain to provide
context). It sounds like this bug is in keystoneclient to me (it's not
making the correct API call?).
** Changed in: python-keystoneclient
I suspect this is an issue with keystoneclient attempting to incorrectly
"guess" whether you're providing ID or name.
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Importance: Undecided => High
** Changed in: keystone
Re-opening based on the above; I didn't test this behind apache.
** Changed in: keystone
Status: Invalid => New
** Changed in: keystone
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keyst
Thanks for the follow up!
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1235841
Title:
Keystone does not start
Status in OpenSta
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1226374
Title:
misused assertTrue in unit tests
Status
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1182861
Title:
Switch to oslo.config 1.2.0 final
Status
Github's markdown rendering appears to be insufficient. Copied straight
from the markdown:
### Get authorized access token: `GET /users/{user_id}/OS-
OAUTH1/access_tokens/{access_token_id}`
### List roles of an access token: `GET /users/{user_id}/OS-
OAUTH1/access_tokens/{access_token_id}/roles`
Andrew- it sounds like you're describing the issue being fixed here
https://review.openstack.org/#/c/33851/ (for bug 1235252)
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to ne
AFAICT, this doesn't sound like it was ever a bug in neutron
** Changed in: neutron
Status: Incomplete => Invalid
** Changed in: python-keystoneclient
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
This is by design, to avoid unnecessarily leaking security-related
details.
However, if debug is enabled, then error message should be specific
about what caused the 401 -- but it should still be a 401.
** Changed in: keystone
Status: In Progress => Won't Fix
--
You received this bug not
** Changed in: keystone
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1191145
Title:
Endpoint creation accepts "name" attribute, but does n
This doesn't appear to be relevant to nova itself
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1239894
Title:
openst
Agree that this is a doc bug, although keystoneclient doesn't currently
document usage for auth_token at all, beyond help attributes via
oslo.config / argparse (in this case... `cfg.BoolOpt('insecure',
default=False, help='Verify HTTPS connections.')` ). openstack-manuals
does have coverage on this
** Changed in: python-keystoneclient
Status: In Progress => Fix Committed
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bu
Cool, thanks!
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1241198
Title:
Keystone tests determine rootdir relative to p
As of havana, keystone emits notifications on project (tenant) deletion
for exactly this use case :)
BP: https://blueprints.launchpad.net/keystone/+spec/notifications
Docs:
http://docs.openstack.org/developer/keystone/event_notifications.html
** Changed in: keystone
Status: New => Invalid
** Changed in: keystone
Status: Triaged => Fix Released
** Changed in: keystone
Assignee: (unassigned) => Dolph Mathews (dolph)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.ne
Need details of the specific failure to consider this a bug. I suspect
you're seeing a failure in the test framework rather than in the API
layer, though.
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engine
I think the piece you need on the keystone side is already available,
but not currently exposed in keystoneclient.
GET /v3/role_assignments
Can be used to get a list of projects the user has any sort of
authorization to access. Bug 1246310 is tracking the addition of this
call to the python lib
This was fixed in 2879d42d by migration 24, which adds an index to
`token.expires`
** Changed in: keystone
Importance: Medium => High
** Changed in: keystone
Status: Confirmed => Invalid
** Changed in: keystone
Assignee: Adam Young (ayoung) => (unassigned)
--
You received this b
Please close test bugs after creating them, thanks!
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1252934
Title:
abcds_lzk
Statu
per morganfainberg's review in https://review.openstack.org/#/c/56602/
** Changed in: keystone
Status: In Progress => Invalid
** Changed in: keystone
Assignee: Edward Hope-Morley (hopem) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Enginee
1 - 100 of 619 matches
Mail list logo
