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
** 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
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`
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
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
** 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 not
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
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.net/bugs
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!
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
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 bug
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
Missed the documentation requirement in the last paragraph. 100% agree!
** Changed in: keystone
Status: Won't Fix = 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/1253482
This has been previously discussed, and 404 is the preferred status code
for an invalid subject token, which must be distinguished from an
invalid X-Auth-Token. An invalid/revoked/expired X-Subject-Token CANNOT
be considered similar to providing incorrect username or password --
the requestor is
keystone isn't capable of returning 503's itself... it also looks like
this is a failed request to swift.
** Also affects: swift
Importance: Undecided
Status: New
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of
Unfortunately, we currently only support 0.7.x and are currently working
on supporting =0.8.x in icehouse:
https://github.com/openstack/requirements/blob/a0acd133f3a005c81e555eadde9ad0a7f0236c0e
/global-requirements.txt#L94
If you have pip available, you might be able to upgrade with:
pip
Unfortunately, this slipped through the havana release without seeing a
fix, so it's now considered stable API and can't be removed. I can't
find it at the moment, but there is an effort being tracked in either a
bug or bp to start testing against additional attributes from leaking
into API
The above fix has not been released yet.
** Changed in: keystone
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1247142
Title:
Live LDAP
Reverting the above patch as it caused subsequent issues when combined
with patchset 16 of https://review.openstack.org/#/c/50491/
After discussing the issue further, this bug report patch doesn't
address the underlying issue which is that we're raising 400's based on
typeerrors in the first
This is, as you noted, out of scope for keystoneclient to fix.. unless
we were going to switch from argparse which is unlikely. This shortcut
behavior is by design in argparse; related discussion here:
http://bugs.python.org/issue14910
** Changed in: keystone
Status: New = Invalid
**
Public bug reported:
The 'valid' index on the token table in the SQL driver doesn't appear to
be used. The 'expires' index is used, and the 'expires + valid' index is
used, but we never query on valid alone.
** Affects: keystone
Importance: Low
Status: New
--
You received this
Isn't this exposed on v3 but not documented... again?
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Changed in: keystone
Importance: Undecided = Wishlist
** Changed in: python-keystoneclient
Importance: Undecided = Wishlist
--
You received this bug
Sorry for the delayed response, but I believe this specific issue has
been fixed as part of one of the related bugs (correct me if I'm
mistaken):
https://bugs.launchpad.net/keystone/+bug/1221808
https://bugs.launchpad.net/keystone/+bug/1215192
Ongoing work is still being tracked in the
** 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/1065614
Title:
Document APIs for PKI tokens
Status in OpenStack API documentation
** Changed in: keystone
Status: New = Invalid
** Tags removed: grizzly-backport-potential havana-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1240170
Title:
** No longer affects: keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1208286
Title:
V3 Identity API: expired tokens are not documented as invalid
Status in OpenStack API
Was going to mark this as invalid, but the above configuration should
definitely be documented.
** Changed in: keystone
Status: Incomplete = Invalid
** Changed in: keystone
Status: Invalid = Confirmed
** Changed in: keystone
Importance: Undecided = Medium
--
You received this
Public bug reported:
The new gate check against unexpected ERRORs appearing in logs
actually caught the string ERROR in a PKI token in the second jenkins
run of the first patchset in:
https://review.openstack.org/#/c/61419/
If you search the log output, you'll find the string ERROR buried in
Keystone does not yet support multiple workers. There's a patch from
late in the havana cycle to introduce it, however.
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Yep! It looks like the move to six resolved this.
** 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/1239956
Title:
Remove obsolete
The admin_token does not represent a user and carries no explicit
authorization that can be delegated. It's just a magical hack for
bootstrapping keystone and should be removed from the wsgi pipeline
after that.
** Changed in: keystone
Status: Confirmed = Invalid
--
You received this bug
If the migration can't be applied, then it should exit cleanly without
making changes (an inconsistent state is a terrible place to be!).
I think the migration should wait for manual intervention to correct
unexpected data (duplicate service names). Adding devstack to this bug
because it sounds
** 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/1261572
Title:
Keystoneclient import fails in python3
Status in OpenStack Identity
** Changed in: keystone
Importance: Undecided = Medium
** Changed in: keystone
Status: New = Confirmed
** Project changed: keystone = openstack-api-site
** Tags added: identity-api
** Summary changed:
- Keystone v3 documentation is lacking w.r.t. Domain Token authentication
+
The warning line is just that - a warning. You must have a token and
endpoint in your environment (there are deprecated environment variables
names that are still supported that could be in use). However, in the
case of token-get, using a token endpoint is actually the cause of
'NoneType' object
As of icehouse, this is now by design. We're working to increase the
separation between the assignments and identity backends, and as a
result, have opted to not validate entities from the identity backend
(users, groups) in the assignment backend, and vice versa.
This issue described here is an
** Changed in: keystone
Status: Fix Released = In Progress
** Changed in: keystone
Assignee: David Stanek (dstanek) = Ilya Pekelny (i159)
** Changed in: keystone
Milestone: icehouse-2 = None
--
You received this bug notification because you are a member of Yahoo!
Engineering
The XML here appears to be as specified by https://github.com/openstack
/identity-api/blob/master/openstack-identity-
api/v2.0/src/docbkx/xsd/token.xsd
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
As of keystone stable/havana 2013.2.2 (commit
0d83e7eee20a50a75863a9d3c75aee7030518229), this doesn't appear to be an
issue. I attempted to reproduce with:
$ python -c import json; print
json.dumps(json.loads(open('etc/policy.v3cloudsample.json').read()),
indent=2)
But got pretty-printed JSON as
Public bug reported:
policy.json and policy.v3cloudsample.json are both missing entries for
the new /v3/regions operations.
** Affects: keystone
Importance: Medium
Assignee: Dolph Mathews (dolph)
Status: New
--
You received this bug notification because you are a member
/v3/regions/{region_id}
** Affects: keystone
Importance: Medium
Assignee: Dolph Mathews (dolph)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs
I'm not sure what you're expecting here? You intentionally put garbage
data into keystone's configuration and it's appropriately reporting an
error against that data. You can bypass the authentication process by
using keystone.conf [DEFAULT] admin_token instead of trying to use
credentials and
The internal URL isn't intended to be secret or privileged. It's
intended to be a public endpoint on an internal (unmetered) network
interface.
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
** Changed in: keystone/havana
Status: Invalid = New
** Changed in: keystone/havana
Importance: Undecided = Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1267215
Title:
Given that this only applies to the v2.0 API and the solution would be a
non-trivial effort at this point, marking as Won't Fix. Happy to re-open
if anyone has a simple solution.
** Changed in: keystone
Status: In Progress = Won't Fix
--
You received this bug notification because you are
** Also affects: devstack
Importance: Undecided
Status: New
** No longer affects: keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1257617
Title:
Nova is unable to
identityv3 is not a recognized or supported service type. The correct
approach to this is to use unversioned endpoints in the catalog, which
python-keystoneclient doesn't fully support yet.
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you
OpenStack has never actually supported these attributes - I suggest that
the examples in documentation be updated to remove them. AFAIK, they
don't even appear in the v2 WADL/XSD specification anywhere (?).
** Also affects: openstack-api-site
Importance: Undecided
Status: New
**
Mathews (dolph)
** Changed in: openstack-api-site
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.net/bugs/1273831
Title:
Keystone v2.0
The difference in messages is very much by design. Authentication can
fail for any number of reasons, and those reasons are suppressed outside
of debug mode.
** Changed in: keystone
Status: In Progress = Won't Fix
** Changed in: keystone
Status: Won't Fix = Confirmed
** Changed
** 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/1257301
Title:
Bump hacking to 0.8
Status in OpenStack
** 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/1218190
Title:
Use assertEqual instead of assertEquals
** 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/1236648
Title:
__metaclass__ is incompatible for python 3
** 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/1255876
Title:
need to ignore swap files from getting
** 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/1268480
Title:
assertTrue(isinstance()) in tests should
: Dolph Mathews (dolph)
Status: 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/1276325
Title:
Testing openstack-hudson; please ignore
Status in OpenStack Identity
Turns out openstack-hudson is broken due to https://bugs.launchpad.net
/openstack-ci/+bug/1276180
** Changed in: keystone
Status: New = Invalid
** Summary changed:
- Test bug, please ignore
+ Testing openstack-hudson; please ignore
--
You received this bug notification because you are
Unassigning due to inactivity.
** Changed in: keystone
Assignee: Adam Young (ayoung) = (unassigned)
** 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:
Traceback (most recent call last):
File tempest/api/compute/servers/test_server_actions.py, line 419, in
test_lock_unlock_server
self.servers_client.wait_for_server_status(self.server_id, 'ACTIVE')
File tempest/services/compute/xml/servers_client.py, line 371, in
** Changed in: keystone
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1273862
Title:
Keystone manage man page errors
Status in OpenStack
Fix Released indicates that the change has been released in a
milestone, whereas Fix Committed simply indicates the patch has been
merged to the relevant branch (master, in this case).
** Changed in: keystone
Status: Fix Released = Fix Committed
--
You received this bug notification
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Status: New = Triaged
** Changed in: python-keystoneclient
Importance: Undecided = Wishlist
** Changed in: keystone
Status: Confirmed = Invalid
--
You
So, this has nothing to do with passlib... passlib just happens to be
the first-to-be-imported of many pypi packages that are not installed
due to:
From a successful job: http://logs.openstack.org/36/62036/7/gate/gate-
tempest-dsvm-full/3549a1d/console.html
2014-02-07 03:20:01.340 | 2014-02-07
Correct- it's v3-only.
** 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/1275744
Title:
v3/projects
https://blueprints.launchpad.net/keystone/+spec/revert-multiple-ldap-
servers
** Changed in: keystone
Status: In Progress = Won't Fix
** Changed in: keystone
Milestone: next = None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
No need to file this as a bug until it's valid against the current
codebase.
** 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/1277753
If there's something reproducible as a bug here, please comment.
** 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/1277724
Title:
All
** Project changed: keystone = devstack
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1260723
Title:
Invalid OpenStack Nova credentials.
Status in devstack - openstack dev
On the keystone side, this is specifically addressed by
https://blueprints.launchpad.net/keystone/+spec/list-limiting
On the horizon side, horizon should issue queries to keystone with as
many filters as reasonably possible to avoid hitting the truncation
behavior implemented above.
** Changed
*** This bug is a duplicate of bug 1277507 ***
https://bugs.launchpad.net/bugs/1277507
** This bug has been marked a duplicate of bug 1277507
ImportError: No module named passlib.hash; HTTP error 403 while getting
ipaddr from googledrive.com
--
You received this bug notification because
Public bug reported:
It seems that something is happening out of order here - there's a GET
for a resource which raises a traceback, and then there's a PUT to the
same resource?
2014-02-12 22:11:29.795 | FAIL: setUpClass
Public bug reported:
traceback-1: {{{
Traceback (most recent call last):
File tempest/services/compute/xml/servers_client.py, line 481, in rebuild
str(Document(rebuild)), self.headers)
File tempest/common/rest_client.py, line 184, in post
return self.request('POST', url, headers,
Added hacking, as I'm already seeing regressions for this that should be
automatically gated.
** Also affects: hacking
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Thanks Victor! This was probably fixed when HACKING was rewritten to
mostly point to http://docs.openstack.org/developer/hacking/
** Changed in: keystone
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** 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)
** 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
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
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-cinderclient
** 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
Assignee
** 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
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
** 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
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.
*** 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
** 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
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!
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
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
** 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
*** 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
** 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/1357652
Title:
Keystone fails to start: CRITICAL log
** 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/1328067
Title:
Token with placeholder ID issued
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 Keystone.
https://bugs.launchpad.net/bugs/1004114
Title:
Password logging
Status in OpenStack
1 - 100 of 528 matches
Mail list logo
