** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Status: New => In Progress
** Changed in: keystone/kilo
Importance: Undecided => High
** Changed in: keystone/kilo
Assignee: (unassigned) => Dolph Mathews (dolph)
stable/kilo https://review.openstack.org/#/c/205351/
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keystone
Status: New => Triaged
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Status: New => Tri
*** This bug is a duplicate of bug 1420104 ***
https://bugs.launchpad.net/bugs/1420104
** No longer affects: keystone
** This bug has been marked a duplicate of bug 1420104
quota set failed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which i
** Changed in: keystone
Status: Incomplete => 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/1420104
Title:
quota set failed
Status in Keystone:
Invali
Although this is absolutely working as originally designed, it's
effectively broken. This bug report may also be a dupe?
Anyway, I think we (unfortunately) need to make a best guess to collapse
multiple interface-specific, completely independent v3 endpoints into v2
endpoints (where at least a pub
*** This bug is a duplicate of bug 1451402 ***
https://bugs.launchpad.net/bugs/1451402
Pagination has not been implemented. To do so, it must be entirely
controlled by the server (not the API client) due to the requirement to
support multiple backends (SQL vs LDAP, for example). The page &
per
As mentioned in comment #2, the page and per_page parameters should be
removed from http://developer.openstack.org/api-ref-identity-v3.html as
they are not, and have never been, supported by keystone.
** Also affects: openstack-api-site
Importance: Undecided
Status: New
--
You received
*** This bug is a duplicate of bug 1451402 ***
https://bugs.launchpad.net/bugs/1451402
** This bug has been marked a duplicate of bug 1451402
v3 - pagination in GET services does not work
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is s
** Tags added: kilo-backport-potential
** Also affects: keystone/kilo
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/1459790
Title:
With fer
Public bug reported:
Keystone's tox.ini contains an "ignore" entry for H405. All violations
of H405 should be fixed so that H405 can be removed from the ignore
list.
** Affects: keystone
Importance: Low
Assignee: Dolph Mathews (dolph)
Status: In Progress
** Ta
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1
Closing because all the cited violations have been fixed.
Henry: when you have a bug fix that consists of multiple patches, use
Partial-Bug on all but the last patch in the sequence. On the last
patch, use Closes-Bug so that the bug will be automatically closed when
that patch merges.
** Changed
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
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/1471
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
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/1452
It wasn't a backwards incompatible change so much as resolving an
apparent regression. v2 clients are not domain aware as there are no
domain references in v2, so the potential for namespace collisions (bug
1475762) would be severe.
** Changed in: keystone
Status: New => Incomplete
** Also
The complexities of re-inventing a first class identity provider in
keystone are not in our best interests. Use a real identity provider
(via either LDAP or federation) that supports these features if you need
them, not the SQL backend.
** Changed in: keystone
Status: Triaged => Won't Fix
Cool, that's expected behavior then.
** 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/1484451
Title:
Project cannot be enable
I thought this was backportable since it's only adding translation
strings to stable/kilo (not modifying things that may have already been
translated).
** Changed in: keystone/kilo
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engi
This is truly by design. But by disallowing it today, we've given
ourselves the option to allow it in the future (we can't do the
opposite: take an API feature away). The consequences of a mutable
hierarchy are complicated and affect the rest of OpenStack (think
quotas, for example), and the risk o
** Tags removed: kilo-backport-potential
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keystone/kilo
Importance: Undecided => Medium
--
You received this bug notification because you are a
LDAP dependencies are optional and are defined here:
https://github.com/openstack/keystone/blob/master/setup.cfg#L25-L27
This takes advantage of setuptools extras:
https://pythonhosted.org/setuptools/setuptools.html#declaring-extras-
optional-features-with-their-own-dependencies
Use the fol
See my comment on a related bug:
https://bugs.launchpad.net/keystone/+bug/1487728/comments/2
** 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.launc
Fixed by https://review.openstack.org/#/c/208069/
** Changed in: keystone
Importance: Undecided => High
** Changed in: keystone
Status: New => Fix Committed
** Changed in: keystone
Assignee: (unassigned) => Dolph Mathews (dolph)
** Also affects: keystone/kilo
I
).
The test failure in https://review.openstack.org/#/c/216236/ illustrates
this issue:
http://logs.openstack.org/36/216236/1/check/gate-keystone-
python27/3f44af1/
** Affects: keystone
Importance: Medium
Assignee: Dolph Mathews (dolph)
Status: In Progress
--
You received
A related conversation is occurring on the mailing list [1]. It sounds
like this is a regression with the introduction of auth plugins to
keystonemiddleware (Jamie, correct me if I'm wrong), so you might want
to try using an older version of keystonemiddleware as a workaround.
[1]: http://lists.op
I'm assuming this was fixed by the last patch. In the future, please use
Closes-Bug on the final patch in your patch sequence -- not just
Partial-Bug on all of them (which leaves the bug open).
** Changed in: keystone
Status: In Progress => Fix Committed
** Changed in: keystone
Milesto
Based on today's keystone meeting and the above comments, I've reduced
the priority of this to Medium across the board and marked this as Won't
Fix in Keystone.
Although this is working as intended, we acknowledge that that intended
behavior is poorly documented, and it seems an OSSN is the best r
devstack:
- https://review.openstack.org/#/c/208584/
- https://review.openstack.org/#/c/208153/
** Tags added: ldap
** Changed in: keystone
Importance: Undecided => Low
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: devstack
Status: New => In Pro
According to Morgan, we're 40 days from dropping support for eventlet
completely, so adding a new configuration option wouldn't provide much
benefit.
In addition, the length of PKI tokens is a widely known issue that has
gone largely unaddressed (besides the introduction of PKIZ as a
compressed al
Leaving this as Incomplete unless someone can reproduce.
** Also affects: hacking
Importance: Undecided
Status: New
** Changed in: hacking
Status: New => Incomplete
** Changed in: keystone
Status: New => Incomplete
--
You received this bug notification because you are a
Moved this to oslo.i18n, but it sounds like openstack/requirements for
stable/juno just need to be fixed to reflect the reality (that
oslo.utils 1.4.0 requires oslo.i18n>=1.3.0).
** Project changed: keystone => oslo.i18n
--
You received this bug notification because you are a member of Yahoo!
En
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Tags removed: kilo-backport-potential
** Changed in: keystone/kilo
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to K
It sounds like the user experience issue here was fixed for both
stable/kilo and master, then. I'm sure further refactoring could be
done, but that doesn't need to be tracked in a bug.
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Importance: Undecided => Medium
** Tags removed: kilo-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to K
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Tags removed: kilo-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/1484237
Title:
token
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/147
This is neither a bug in keystone nor there a fix In Progress in
keystone.
** Project changed: keystone => pbr
** Changed in: pbr
Status: In Progress => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https:/
** Also affects: pbr
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/1496222
Title:
Requirements update breaks keystone install on 3'rd party
Apache will refuse connections that it cannot assign to threads once
MaxClients is exhausted, and if you're only running 10 threads, then I'm
also guessing that your MaxClients is set to be less than the number of
concurrent connections you're throwing at it.
I'm closing this because this is just
I've run into this myself.
This is the result of using outdated WSGI startup scripts. As part of
your upgrade process, you must switch to the ones from the release
you're trying to deploy.
This is because keystone has refactored some responsibilities out of
those WSGI scripts, so your scripts are
Your mapping is unconditionally resulting in this behavior. See the
mapping documentation:
http://docs.openstack.org/developer/keystone/mapping_combinations.html
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engi
This seems like a missing use case in openstackclient? If you give it an
existing token, why is it trying to rescope it? What is it trying to
rescope the token to?
** Also affects: python-openstackclient
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Inc
The example catalog for a domain scoped token looks correct to me: those
are endpoints that do not presume tenancy in the URL.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to O
Public bug reported:
As a result of the Fernet work session at the Newton design summit in
Austin:
Prior to making Fernet the default token provider, keystone should fail
on startup if fernet_setup has not been run when fernet is also the
configured token provider. Today, keystone will instead re
I think I understand why the manual specifies that the deployer should
"create the _member_" role using "keystone role-create --name _member_"
(to support the explicit assignment in the following step), but I'd
recommend removing that instruction as a starting point to addressing
this issue. I'm no
*** This bug is a duplicate of bug 1406536 ***
https://bugs.launchpad.net/bugs/1406536
** This bug has been marked a duplicate of bug 1406536
unrecognized service on Keystone install
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
** Also affects: keystone/juno
Importance: Undecided
Status: New
** Changed in: keystone/juno
Importance: Undecided => High
** Changed in: keystone/juno
Assignee: (unassigned) => Steve Martinelli (stevemar)
** Changed in: keystone/juno
Status: New => In Progress
--
You
master patch https://review.openstack.org/#/c/154915/
** Also affects: keystone/juno
Importance: Undecided
Status: New
** Changed in: keystone/juno
Assignee: (unassigned) => Alexander Makarov (amakarov)
** Changed in: keystone/juno
Status: New => In Progress
--
You receiv
Before we backport this to stable/juno, are there any legitimate use
cases where people would be depending on the old behavior? Just want to
ensure there's no risk to backporting.
** Also affects: keystone/juno
Importance: Undecided
Status: New
** Changed in: keystone/juno
Status
** Also affects: keystone/juno
Importance: Undecided
Status: New
** Changed in: keystone/juno
Assignee: (unassigned) => wanghong (w-wanghong)
** Changed in: keystone/juno
Status: New => In Progress
** Changed in: keystone/juno
Importance: Undecided => Low
--
You receiv
"F00" / "F01") can be dropped, as long as Keystone
can still validate the tokens it's issuing.
** Affects: keystone
Importance: Medium
Assignee: Dolph Mathews (dolph)
Status: New
** Tags: fernet
** Tags added: fernet
** Summary changed:
- Fernet token
Public bug reported:
Keystone has three formal documentation sites (that I'm aware of):
http://docs.openstack.org/developer/keystone/
http://docs.openstack.org/developer/keystonemiddleware/
http://docs.openstack.org/developer/python-keystoneclient/
But none of these are cross-linked with e
ty considerations, rather than
the cost of performance.
** Affects: keystone
Importance: Wishlist
Assignee: Dolph Mathews (dolph)
Status: New
** Tags: fernet
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
requires some bitwise operations,
but this library demonstrates how easy the timestamp is to extract
without having the Fernet encryption key:
https://pypi.python.org/pypi/keyless_fernet
** Affects: keystone
Importance: Medium
Assignee: Dolph Mathews (dolph)
Status: New
** Tags
support doesn't really exist yet,
and the current behavior will only work if the hierarchical multitenancy
effort successfully migrates domains to be projects.
** Affects: keystone
Importance: High
Assignee: Dolph Mathews (dolph)
Status: Triaged
** Tags: fernet
--
You rec
** 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/1428708
Title:
Fernet token expiration is redundant with key rotation
Statu
As it turns out, the output of base64.urlsafe_b64encode() is not
actually URL-safe if the result includes padding. The padding character
is '=' which must be percent-encoded.
The result is that "valid" tokens are being made URL-friendly by some
defensive code in keystonemiddleware, and are thus ma
A fix landed for this without citing this bug:
https://github.com/openstack/keystone/commit/a077a875dd50974b66895f7d1ac39097d208e33a
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subsc
** Project changed: keystone => keystone (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1433595
Title:
Keystone writes "Access denied" for DB-Connection to its configured
log
The assertion being made by OP is that the domain which owns the scoped
project should become the domain upon which the action is performed, but
I would consider that behavior to be a privilege escalation
vulnerability. The user is presenting explicit domain-level
authorization on a domain-level re
The _member_ role is a handicap for the v2 API to provide an explicit
means of expressing default tenancy. The existing behavior satisfies
that behavior just fine.
There's really no reason you should be creating the "_member_" role
manually as a deployer. Use another role name instead, such as "Me
Removed this from keystone since argparse does not appear as an explicit
dep of keystone in any requirements file.
** Changed in: keystone
Status: New => Invalid
** Changed in: python-openstackclient
Assignee: (unassigned) => Dolph Mathews (dolph)
** Also affects:
The same applies to openstackclient.
** Also affects: oslo.config
Importance: Undecided
Status: New
** Changed in: oslo.config
Assignee: (unassigned) => Dolph Mathews (dolph)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
** Also affects: pysaml2
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/1441083
Title:
pkg_resources.DistributionNotFound: The 'argparse' dis
Abandoning this as invalid since pip 6.1.1 handles argparse correctly
now.
** Changed in: oslo.config
Status: In Progress => Invalid
** Changed in: python-keystoneclient
Status: In Progress => Invalid
** Changed in: pysaml2
Status: New => Invalid
--
You received this bug n
https://review.openstack.org/#/c/173034/
** Changed in: keystone
Importance: Undecided => High
** Tags added: juno-backport-potential
** Tags added: icehouse-backport-potential kilo-backport-potential
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
** Also aff
Closing based on feedback in comment #2
** Tags removed: keystone specific
** 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/1442663
T
Docs:
http://docs.openstack.org/admin-guide-cloud/content/flushing-expired-
tokens-from-token-database-table.html
In addition, Fernet tokens, introduced in Kilo, do not need to be
persisted to the database, and will leave your token table completely
empty:
http://docs.openstack.org/developer
The internal URL is not intended to be obscured from users, but rather
is intended to provide a public API interface on a faster / more
efficient network interface (depending on the deployment). If users can
reach the internal endpoint (such as for glance), then they can likely
save bandwidth charg
In master of keystone, the version response looks like this:
{
"version": {,
"status": "stable",
"updated": "2014-04-17T00:00:00Z",
"media-types": [
{
"base": "application/json",
"type": "application/vnd.openstack.identity-v2.
Public bug reported:
The following API documentation pages contain sample XML responses, even
though Keystone deprecated XML support several releases ago, and removed
support altogether in Kilo:
http://developer.openstack.org/api-ref-identity-v2.html
http://developer.openstack.org/api-ref-ide
** Project changed: keystone => openstack-api-site
** Summary changed:
- Identity API docs contain advertise support for XML
+ Identity API docs advertise support for XML
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
I don't see any reason for this to be a "Medium" bug - there's
absolutely no negative impact described here. In fact, the documented
behavior is as-designed. To quote myself from the code review above:
The most obvious conflicting use case I can think of is having two
services of the same type i
Does this affect juno?
** Tags added: kilo-backport-potential
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
Public bug reported:
The logging in keystone.common.wsgi is unable to handle unicode query
strings. The simplest example would be:
$ curl http://localhost:35357/?Ϡ
This will fail with a backtrace similar to:
2015-04-24 19:57:45.860 22255 TRACE keystone.common.wsgi File
".../keystone/keys
Marked as incomplete for keystonemiddleware because this looks like an
issue between devstack and pip.
** Project changed: keystone => keystonemiddleware
** Also affects: devstack
Importance: Undecided
Status: New
** Summary changed:
- Keystone Middleware Installation
+ Can't find pa
Implemented as part of:
https://blueprints.launchpad.net/keystone/+spec/rescoping
** Changed in: keystone
Milestone: None => 2015.1.0
** Changed in: keystone
Status: Triaged => Fix Released
** Changed in: keystone
Assignee: Priti Desai (priti-desai) => Adam Young (ayoung)
--
Public bug reported:
The fernet keys are stored (by default) in /etc/keystone/fernet-keys/ in
individual key files. All keys are read from disk on every request, so
you end up with log spam like:
keystone.token.providers.fernet.utils [-] Loaded 2 encryption keys
from: /etc/keystone/fernet-keys/
I completely agree, the current design directly results in the fragility
you described (I pushed for naming domain-specific configuration files
using their immutable, system-defined domain IDs instead, but lost that
argument... I think on the basis of deployer experience? I'll let Henry
Nash commen
Ready for the punt return? :)
Because ?id=default is not a query parameter documented or supported in
any collection API, the client is not actually making a valid API
request. And because 'id' is also a documented API convention, I'd
suggest that to provide the expected user experience, the clien
That's crazy. Don't try to start the eventlet server if you're already
running it in Apache on the same port. More generally, don't try to run
any two things on the same port, as the error message already indicates.
** Changed in: keystone
Status: Incomplete => Won't Fix
--
You received t
Keystone switched to UUID by default in Juno due to longstanding issues
with PKI that will likely never be resolved. At least in the stable/juno
or stable/kilo install guides, there is no token setup to do beyond
scheduling a cron job to run keystone-manage token_flush.
Setting the keystone token
** Project changed: keystone => python-openstackclient
** Summary changed:
- Deleting nonexistent end-point gives incorrect error message
+ Deleting nonexistent endpoint gives incorrect error message
** Tags removed: error-messge
** Tags added: error-message user-experience
--
You received thi
Public bug reported:
Similar to token_flush, we need an operation to purge old revocation
events from the database, else they'll eventually consume excessive disk
space. The operation should be very similar in implementation and usage
to token_flush.
Filing this as Medium priority because it does
This is a critical Red Hat packaging issue that has been verified by
multiple users.
I've verified the solution in comment #10 works.
** Changed in: glance
Status: Incomplete => Invalid
** Changed in: keystone
Status: Incomplete => Invalid
** Changed in: nova
Status: Incomp
https://review.openstack.org/#/c/173123/ has merged.
** Changed in: glance
Status: New => Invalid
** Changed in: keystonemiddleware
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
http
>From Ken Chen in https://bugs.launchpad.net/python-
keystoneclient/+bug/1457279
--
In keystoneclient/session.py file, _http_log_request method, we have below
codes:
if data:
string_parts.append("-d '%s'" % data)
logger.debug(' '.join(string_parts))
However, if d
Why was this marked invalid?
** Changed in: keystone
Importance: Undecided => Low
** Changed in: keystone
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad
If this can be reproduced against 2014.1 icehouse, I would consider it
to be a critical issue for our core use case (default SSL configuration
w/ apache httpd).
** Changed in: keystone
Importance: Undecided => Critical
** Also affects: keystone/icehouse
Importance: Undecided
Status:
*** 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
Added oslo to this bug for unacceptably impacting at least keystone and
heat, by not providing a viable alternative capable of maintaining
backward compatibility with existing public APIs.
Keystone's solution is to stop using oslo.timeutils in this instance,
and instead move the deprecated timeuti
** Project changed: nova-project => nova
--
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/1461847
Title:
Stacking controller fails due to error: 'wsgiref' is not in global
token_cache_time is part of keystonemiddleware.auth_token's
configuration. It defaults to 5 minutes if you haven't set it in your
deployment:
https://github.com/openstack/keystonemiddleware/blob/57d389da8aaef3f955d7f0b086803d98b6531a2e/keystonemiddleware/auth_token/__init__.py#L278-L283
It sounds
Closing because there's a similar OpenStack-wide discussion to
accomplish the same thing.
** 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
This is by design on the keystone side. As a consequence of a reducing a
user's current authorization, relevant tokens are revoked and the user
must subsequently re-authenticate.
If horizon stored an unscoped token along with the active scoped token,
it could re-authenticate for another scoped tok
** 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 lo
** 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
Statu
** 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 Das
** Changed in: keystone
Status: In Progress => Won't Fix
** Changed in: openstack-api-site
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/1362
** Changed in: keystonemiddleware
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 i
301 - 400 of 619 matches
Mail list logo
