Importance: Low
Assignee: Dolph Mathews (dolph)
Status: Triaged
** Tags: documentation upgrades
** Changed in: keystone
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenSta
** Project changed: openstack-manuals => keystone
** Changed in: keystone
Milestone: ocata => None
** Changed in: keystone
Assignee: Alexandra Settle (alexandra-settle) => Dolph Mathews (dolph)
--
You received this bug notification because you are a member of Yahoo!
Enginee
Marking this as Medium in mitaka since we didn't support zero-downtime
upgrades then, but this is still an unexpected behavior of bootstrap
that would potentially affect an upgrade process.
** Also affects: keystone/mitaka
Importance: Undecided
Status: New
** Changed in:
Marking this as High because the consequence is perceivable downtime
during a zero-downtime upgrade.
** Also affects: keystone/newton
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** Also affects: keystone/newton
Importance: Undecided
Status: New
** Changed in: keystone/newton
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
Public bug reported:
There are three scenarios during a rolling upgrade process where we
could prevent operators from doing the "wrong thing" (doing things out
of order):
1) Operators running code from the next release before `keystone-manage
db_sync --expand` has been run: If you run the next
Public bug reported:
Now that we have rolling upgrades in place, we should have a unit test
in place to ensure that developers (and reviewers) do not land
additional patches to the legacy migration repository and expect
everything to continue working, as that would be akin to rewriting our
Public bug reported:
In the legacy migration repository, we've traditionally allowed any sort
of database manipulation, including tables to be created, data to be
migrated, columns to be dropped, etc. Recently, we introduced a
constraint on those upgrades to prevent non-additive operations from
Public bug reported:
To ensure that each of the 3 new migration repositories contain the same
number of steps, we should introduce a test to catch developers
attempting to introduce a new step to any one of the new repos, without
introducing no-op steps to all of them.
Upon failure, the test
Public bug reported:
Currently, keystone does nothing to prevent an operator from running
each step of the rolling migration process out of order. Theoretically,
most migrations will fail if the table they're looking to drop does not
exist, etc, but that might not always be the case.
The
Moved this to oslo.cache, since
keystone.common.cache.backends.mongo:MongoCacheBackend moved to
oslo_cache.backends.mongo:MongoCacheBackend. I'm guessing we need to add
a third case to that method to attempt to pickle complex objects?
** Changed in: keystone
Importance: Undecided => Medium
**
The 503 is coming from an intermediary proxy (likely whatever you're
using to implement HTTPS), not keystone (keystone is not capable of
returning a 503).
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
Our stable branch policy dictates that we don't backport features, and
an API-impacting one would be the first to be denied in review.
Sadly, it looks like a significant oversight in the original
implementation, though.
** Changed in: keystone
Status: New => Invalid
--
You received this
Is there a patch up for this? It was filed under the "wrong" project, so
the bots would not have been able to link a patch.
** Project changed: keystone => python-keystoneclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** Also affects: keystone/mitaka
Importance: Undecided
Status: New
** Changed in: keystone/mitaka
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
** Also affects: keystone/mitaka
Importance: Undecided
Status: New
** Changed in: keystone/mitaka
Status: New => In Progress
** Changed in: keystone/mitaka
Importance: Undecided => Medium
** Changed in: keystone/mitaka
Assignee: (unassigned) => Matthew Edmonds
Public bug reported:
In 0.06% of my test runs, test_v3_auth.TestAuthTOTP fails with either:
Traceback (most recent call last):
File "/root/keystone/keystone/tests/unit/test_v3_auth.py", line 4904, in
test_with_multiple_credential$
self.v3_create_token(auth_data,
I imagine this will be addressed by (or nearly addressed by) having
concrete role assignments for federated users in keystone:
https://review.openstack.org/#/c/284943/
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Assignee: (unassigned) => Ron
** Also affects: keystone/mitaka
Importance: Undecided
Status: New
** Changed in: keystone/mitaka
Status: New => In Progress
** Changed in: keystone/mitaka
Assignee: (unassigned) => Dolph Mathews (dolph)
** Changed in: keystone
Importance: Undecided =&g
'll change an admin's password if you specify something different
[Fri 09:31] dolphm so the options are, I guess, to delete the
admin account in the db or to use the auth_token middleware?
** Affects: keystone
Importance: Undecided
Assignee: Dolph Mathews (dolph)
Status: I
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
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
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 =>
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!
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
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
Closing this because bearer tokens, etc, are a well known weakness.
** 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 OpenStack Identity (keystone).
Closing this since we're moving in the opposite direction at this point.
** 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 OpenStack Identity (keystone).
** Also affects: keystone/liberty
Importance: Undecided
Status: New
** Changed in: keystone/liberty
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
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:
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
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
** 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.
** 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:
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:
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,
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
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
** 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
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.
** 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.
** 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 => Medium
** Tags removed: kilo-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
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
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!
** 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
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
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
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
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
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
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]:
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
Importance
).
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
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.
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
** 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
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
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!
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
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.
** 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.
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
** Tags: low-hanging
** 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
*** 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
*** 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
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
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
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Status: New = In Progress
** Changed in: keystone/kilo
Importance: Undecided = Low
** Changed in: keystone/kilo
Assignee: (unassigned) = Dolph Mathews (dolph)
--
You received
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 =
** 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:
*** 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
** 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)
** Tags removed
** 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/1479377
Title:
Eror while installing keystone
Status in keystone package in Ubuntu:
*** This bug is a duplicate of bug 1478504 ***
https://bugs.launchpad.net/bugs/1478504
** This bug has been marked a duplicate of bug 1478504
test_admin_version_v3 actually tests public app
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Was something else already running on port 5000, perhaps?
** Project changed: keystone = packstack
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1478466
Title:
Apache2 fail to start
This is proposing an API impacting solution to a deprecated API, and
completely glossing over the problem being addressed.
If they default domain changes, the tokens will not be properly
converted.
What does this mean?
** Changed in: keystone
Status: New = Invalid
--
You received this
Public bug reported:
v3 tokens contain the issued_at and expires_at timestamps for each
token. If a token is created on the v2 API and then validated on the v3
API, this timezone information is missing (the 'Z' at the end of the
timestamp), and thus cannot be validated as ISO 8601 extended format
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Tags removed: kilo-backport-potential
** Changed in: keystone/kilo
Status: New = Triaged
** Changed in: keystone/kilo
Importance: Undecided = High
--
You received this bug notification because you are a
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Importance: Undecided = High
** Changed in: keystone/kilo
Assignee: (unassigned) = Dolph Mathews (dolph)
--
You received this bug notification because you are a member of Yahoo
Public bug reported:
While investigating bug 1474069, I discovered this test fails when run
in isolation as well.
$ tox -e py27 keystone.tests.unit.test_config
running=
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} \
Ah, then we need to backport the fix for bug 1448286 (which is already
tagged for backporting), along with the fix for bug 1454968 (which my
fix for the first bug triggered).
Closing this bug as we need to track against the bugs merged to master.
** Changed in: keystone
Status: Incomplete
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Also affects: keystone/juno
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
** Also affects: keystone/juno
Importance: Undecided
Status: New
** Changed in: keystone/juno
Status: New = In Progress
** Changed in: keystone/juno
Importance: Undecided = Medium
** Changed in: keystone/juno
Assignee: (unassigned) = Dolph Mathews (dolph)
--
You
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Assignee: (unassigned) = Dolph Mathews (dolph)
** Changed in: keystone/kilo
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Yahoo
: (unassigned) = Dolph Mathews (dolph)
** 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/1448286
Title:
unicode query string raises
*** This bug is a duplicate of bug 1448286 ***
https://bugs.launchpad.net/bugs/1448286
For reference, here's a direct link to the stable/kilo backport of both
issues: https://review.openstack.org/#/c/201708/
** This bug has been marked a duplicate of bug 1448286
unicode query string
Public bug reported:
While investigating bug 1474069, I discovered this test fails when run
in isolation as well.
$ tox -e py27
keystone.tests.unit.common.test_notifications.NotificationsTestCase
running=
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
** Project changed: keystone = python-openstackclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1473298
Title:
Cannot create keystone trust with python-openstackclient using
** 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
** Tags added: federation
** Changed in: keystone
Status: New = 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/1472060
Title:
websso callback is in the wrong place
** Tags added: federation
** Project changed: keystone = python-keystoneclient
** Changed in: python-keystoneclient
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
apt-get install python-dev
** 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/1470898
Title:
keystoneclient client doesn't install
*** 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
*** 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
** 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
1 - 100 of 528 matches
Mail list logo
