** 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/1472503
Title:
python-ldap 2.4.20 causing install issues
Status in OpenStack
*** This bug is a duplicate of bug 1454968 ***
https://bugs.launchpad.net/bugs/1454968
** This bug has been marked a duplicate of bug 1454968
hard to understand the uri printed in the log
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is s
*** This bug is a duplicate of bug 1017606 ***
https://bugs.launchpad.net/bugs/1017606
** This bug has been marked a duplicate of bug 1017606
Mixing references to 'Tenants' and 'Projects' is confusing
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
** Changed in: keystone
Importance: Undecided => Wishlist
** Changed in: keystone
Status: In Progress => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1467780
Title:
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
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
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
** 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
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
*** 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
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:
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
>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
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
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
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
** 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
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
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
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
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
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/
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)
--
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
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
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
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
** 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.
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
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.
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
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
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
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
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
** 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
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
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 _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
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
** 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
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
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
** 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
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
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
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
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
"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
** 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
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
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
** 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
*** 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
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
trust-ext.rst#list-trusts
- Paragraphs not being wrapped at 79 characters (only visible in source)
** Affects: keystone
Importance: Medium
Assignee: Dolph Mathews (dolph)
Status: Triaged
** Tags: documentation
** Tags added: documentation
** Changed in: keystone
Ass
I believe this was by design, but I don't know of any deployments that
actually deploy multiple services of the same type in the same cloud
(and multiple branded services to do it, instead of regions). As a "bug"
this strikes me as super low priority, and obviously has the potential
to break anyone
Added keystone to this bug - is there any reason why keystone should
accept a fasley password for a user password update?
** Changed in: python-keystoneclient
Importance: Undecided => Medium
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
S
I'd rather see support for this come out of oslo.config, automatically.
I believe there was a related mailing list discussion recently as well.
** Also affects: oslo.config
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Incomplete
--
You received this
The UX issue is that the error message *implies* that both the
referenced user ID and the referenced tenant ID are valid, and that it
is the relationship between the two that is invalid.
"User 83af9fd423b94b53bf3ed36a3823236d is unauthorized for tenant
demo"
In this case, "demo" is not a tenant
** 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/1383924
Title:
keyston
The token lifespan is already configurable in keystone.conf [token]
revocation=3600 (defined in seconds).
** 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
Swami: thanks for the follow up! This one was a little befuddling :)
** 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/1378270
T
It's also completely misdefined as an "xsd:string" (also in /v3/users).
I'd strongly recommend referring to the source of truth for the API,
which is currently here:
https://github.com/openstack/identity-api/blob/master/v3/src/markdown
/identity-api-v3.md
Although that document will soon be mo
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: keystone
Importance: Undecided => Medium
** Tags added: federation
** Tags added: documentation
** Changed in: python-keystoneclient
Importance: Undecided => Wishlist
** Changed in: python-k
** Project changed: keystone => python-memcached
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1380670
Title:
python-memcached misses working backend
Status in Memcached for python:
++ I should have referenced this bug in the commit message, and tracked
this against openstack-api-site.
** 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:/
** 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/1366905
Title:
Migration from havana to icehouse takes forever if large subse
This is unfortunately true, but we can't change date formats as it would
be considered an API backwards incompatibility. Hopefully we've made v3
very consistent!
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engin
no
Assignee: (unassigned) => Dolph Mathews (dolph)
** Changed in: keystone/juno
Importance: Undecided => Medium
** Changed in: keystone/juno
Status: New => In Progress
** Tags removed: db
** Tags added: sql
--
You received this bug notification because you are a member of Yahoo
** Also affects: keystone/juno
Importance: Undecided
Status: New
** Changed in: keystone/juno
Milestone: None => juno-rc2
** Changed in: keystone/juno
Assignee: (unassigned) => Dolph Mathews (dolph)
** Changed in: keystone/juno
Importance: Undecided => Medium
*
** Also affects: keystone/juno
Importance: Undecided
Status: New
** Changed in: keystone/juno
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
This is actually a documentation bug, as we previously both mis-
specified and mis-implemented the behavior for HEAD requests. Keystone's
new behavior is correct, but unfortunately it looks like we did not
update the documentation.
** Project changed: keystone => openstack-api-site
** Tags remove
** Tags removed: glance
** Changed in: horizon
Status: New => Invalid
** Changed in: glance
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/13680
; High
** Changed in: keystone/icehouse
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/1315556
Title:
Disabling a domain does not di
*** This bug is a duplicate of bug 1355489 ***
https://bugs.launchpad.net/bugs/1355489
Agree, and the fix has been backported to stable/icehouse and should be
included in 2014.1.3
** This bug has been marked a duplicate of bug 1355489
authenticate ldap binary fields fail when converting fi
** Also affects: horizon
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/1361758
Title:
Keystone should bootstrap CONF.member_role_name
Statu
This migration is no longer supported.
** 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/1131590
Title:
migration 17: user_proj
As Lance said, there's definitely work going on in this direction
(although, there are a several separate feature requests above!), but
it's not really within scope for Keystone, as the other services own
their own default policies (and thus, default role definitions). I
completely agree though, it
Anyone running into this should still discuss the issue here, but this
is now beyond our support lifecycle.
** 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.
ht
Awesome! Good to hear.
** 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/1362181
Title:
Multi-domain has problems with domain
As described above, this is by design. Granting authorization in v3 is
more explicit than in v2.
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launch
** 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/1219036
Title:
publish revocation events
Status in OpenStack Identity (Keysto
*** This bug is a duplicate of bug 1347318 ***
https://bugs.launchpad.net/bugs/1347318
** This bug is no longer a duplicate of bug 1351026
IdentityError in TokensV3TestJSON.test_rescope_token
** This bug has been marked a duplicate of bug 1347318
Revocation events don't handle scoped tok
*** This bug is a duplicate of bug 1347318 ***
https://bugs.launchpad.net/bugs/1347318
** This bug has been marked a duplicate of bug 1347318
Revocation events don't handle scoped tokens correctly
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, w
*** This bug is a duplicate of bug 1361378 ***
https://bugs.launchpad.net/bugs/1361378
** This bug has been marked a duplicate of bug 1361378
"MySQL server has gone away" again
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed t
Not all deployments utilize a member_role, which is just a workaround to
support default tenancy assignments in v2. So, the "member" role should
be created on-demand, and only if necessary. In the case of a read-only
LDAP backend for assignments (which again, the community generally
doesn't have mu
I'm forced into assuming this has been fixed without being tracked,
since there's no actual spelling errors cited here to confirm that
assumption against.
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engine
** 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/1360446
Title:
client connection leak to memcached under ev
** 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/1332058
Title:
keystone behavior when one memcache backend
** 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
** 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: 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: 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/1357652
Title:
Keystone fails to start: "CRITICAL log lo
** 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
*** 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: 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 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
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.
101 - 200 of 619 matches
Mail list logo
