** 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/1293312
Title:
create user allows no password
Status in OpenStack Identity (Keyston
This was actually implemented in havana:
GET /v3/role_assignments?user.id={user_id}&project.id={project_id}
Docs:
https://github.com/openstack/identity-api/blob/master/openstack-
identity-api/v3/src/markdown/identity-api-v3.md#list-effective-role-
assignments-get-role_assignments
** Changed
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: openstack-api-site
Assignee: (unassigned) => Dolph Mathews (dolph)
--
You received this bug notification because you are a mem
This looks like a packaging issue - what version of oslo.config is
installed?
** 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/1294215
Tit
As discussed in today's keystone meeting,
keystoneclient.middleware.auth_token can track valid IdPs on GET /v3/OS-
FEDERATION/identity_providers and compare them to tokens to test for
validity.
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: pytho
Public bug reported:
This occurred in a gate run (lost the link for the moment):
FAIL:
keystone.tests.test_v3_os_revoke.OSRevokeTests.test_disabled_project_in_list
tags: worker-1
--
pythonlogging:'': {{{
Adding cache-proxy 'keys
** Changed in: grenade
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/1294971
Title:
gate-grenade-dsvm-partial-ncpu Failure in upgrade-keystone
Status in
** Changed in: keystone
Milestone: None => icehouse-rc1
** Also affects: openstack-api-site
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/
r: 1 != 2
According to keystone.common.environment.__init__, the expected behavior
varies for OS X:
# Optionally enable keepalive on the wsgi socket.
# This option isn't available in the OS X version of eventlet
But the test is written without the same flexibility.
** Affects:
** 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/1243812
Title:
The keystone.catalog.core.Manager class contains a lot of red
** Project changed: python-keystoneclient => 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/1297261
Title:
messages when the module import fails are very misleading
There wouldn't be any impact on keystone itself (nor anything for it to
log), but we might be able to get some better feedback out of requests,
which is what is producing the SSL validation failure.
** Project changed: keystone => python-keystoneclient
** Tags added: user-experience
** Changed i
This looks like an downstream bug for RedHat? If so, I believe it should
be filed here: https://bugzilla.redhat.com/enter_bug.cgi?product=RDO
** Changed in: keystone
Status: New => Invalid
--
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 OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1282089
Title:
keystone client is l
Actually appears to be the offending code in 0.3.2, which has since been
fixed:
https://github.com/openstack/python-
keystoneclient/blob/0.3.2/keystoneclient/middleware/auth_token.py#L1022-L1025
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Milestone: None => 0.7.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
htt
** Changed in: python-keystoneclient
Status: Fix Committed => Fix Released
** Changed in: python-keystoneclient
Milestone: None => 0.7.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.ne
Relevant role assignment operations are documented starting around here:
https://github.com/openstack/identity-api/blob/master/openstack-
identity-api/v3/src/markdown/identity-api-v3.md#list-groups-roles-on-
domain-get-domainsdomain_idgroupsgroup_idroles
** Project changed: keystone => openstac
Valuable changes were made as part of that blueprint, but as documented
in the attached code reviews, we stopped short of actually allowing role
assignments to non-existent users due to a lack of use cases that were
not already solved (by group role assignments, for example). If you have
a use case
** 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/1298624
Title:
dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NotSupported:
This appears to have been fixed in 96be7449 as part of a larger sync
with oslo.db
https://review.openstack.org/#/c/71311/
** Changed in: keystone
Status: In Progress => Invalid
** Changed in: keystone
Assignee: Xurong Yang (idopra) => (unassigned)
--
You received this bug notific
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => In Progress
--
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/1226
** Also affects: keystone
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/1279000
Title:
db migrate script to set charset=utf8 for all tables
Good to hear! FWIW, use of default_project_id is a bit of an anti-
pattern when compared to explicit role assignments on one or more
projects, hence it's ignored by default.
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
Per https://bugs.launchpad.net/keystone/+bug/1300089/comments/8
** 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/1300553
Title:
when
*** This bug is a duplicate of bug 1301036 ***
https://bugs.launchpad.net/bugs/1301036
This is a dupe of bug 1301036, but LP is timing out when I try to "Mark
as duplicate."
** Tags removed: keystone
** Tags added: icehouse-rc-potential
** Changed in: keystone
Status: New => Invalid
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Changed in: keystone (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/b
** 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 neutron.
https://bugs.launchpad.net/bugs/1299349
Title:
upstream-translation-update Jenkins job faili
Unsupported query strings *should* be ignored -- can you point to an web
service that sets a different precedent?
** 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.
http
PKI token ID's are either the base64 encoded token itself (for the
purposes of X-Auth-Token / X-Subject-Token), or an MD5 hash of the
base64 encoded token (for the purposes of HTTP resources) (the hash
method likely becoming configurable in Juno or rendered unnecessary by
token compression).
** Ch
Ah, stripping whitespace. I'm not really a fan of that behavior (nor of
manipulating any user input), but is it really harming anything?
** Changed in: keystone
Importance: Undecided => Wishlist
** Changed in: keystone
Status: Incomplete => Opinion
** Summary changed:
- strip the name
Correct! This was fixed in https://review.openstack.org/#/c/71159/
** Changed in: keystone
Status: Confirmed => Invalid
** Changed in: keystone
Assignee: Pablo Fernando Cargnelutti (pablo-fernando-cargnelutti) => Henry
Nash (henry-nash)
--
You received this bug notification because
General direction is to avoid the proliferation of 'extras' in favor of
explicitly supporting attributes exposed to the API.
** 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 K
Since it's not already mentioned in this bug, the long term solution
here is to simply not persist tokens at all:
https://blueprints.launchpad.net/keystone/+spec/ephemeral-pki-tokens
** Also affects: openstack-manuals
Importance: Undecided
Status: New
--
You received this bug notifi
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** Changed in: openstack-api-site
Status: New => Confirmed
** Tags added: identity-api
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keyston
Public bug reported:
This extension should be documented here:
https://github.com/openstack/identity-api/tree/master/openstack-
identity-api/v3/src/markdown
At least one route is exposed as part of this extension:
GET /v3/auth/tokens/OS-PKI/revoked
By this router:
http://git.openstack.org
Fix Released indicates that the fix has been included as part of a
milestone release, while Fix Committed indicates that the fix has simply
merged to master, which is the case here.
** Changed in: keystone
Importance: Undecided => Medium
** Changed in: keystone
Status: Fix Released => F
it'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)
** 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
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
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, expected_status=http_client
** 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 (edmondsw)
** 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).
https://bu
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 Open
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
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 Te
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
**
Thanks, Henrique!
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1081221
Title:
Keystone POST /tokens response does not contai
openstack-db and openstack-utils appears to be a proprietary Red Hat
thing - I couldn't find a bug database for either project, though.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
** 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/1206345
Title:
V3 Api does not provide a means of gettin
** 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/1306874
Title:
Fix typo of ANS1 to ASN1
Status in Djang
This is partially "Won't Fix" (because `keystone user-get` calls v2
which does not take advantage of etc/policy.json), and partially
"Invalid." (because `openstack user get --identity-api-version=3` can
use v3, and the v3 implementation of this call already utilizes
etc/policy.json, where you can a
This looks a lot like a call we'd *like* to have in v3 (perhaps GET
/v3/catalog + X-Subject-Token), but we don't implement anything like
this in v2.
** Changed in: keystone
Status: New => Triaged
** Changed in: keystone
Importance: Undecided => Medium
** Project changed: keystone => op
It doesn't sound like there's anything to fix in keystone then, if this
is due to dependency version(s) already documented as unsupported.
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
There's neither an XML interface nor a JSON interface to this call.
The only supported content type on this call is "application/x-pem-
file". The content of of the error->message attribute in your example
response should be the entire response body itself, regardless of
whether the client demands
** Project changed: keystone => openstack-api-site
** Changed in: openstack-api-site
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1312221
Title:
** Changed in: python-openstackclient
Status: Invalid => Confirmed
** 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/13066
Can you paste the keystone.conf that results from setting
KEYSTONE_TOKEN_FORMAT=UUID ?
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Incomplete
** Changed in: keystone
Importance: Undecided => High
--
You received this bu
*** This bug is a duplicate of bug 1276221 ***
https://bugs.launchpad.net/bugs/1276221
** This bug has been marked a duplicate of bug 1276221
Keystone returns HTTP 400 as SQLAlchemy raises None exceptions
--
You received this bug notification because you are a member of Yahoo!
Engineerin
** Project changed: keystone => python-keystoneclient
** Changed in: python-keystoneclient
Importance: Undecided => High
** Changed in: python-keystoneclient
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subs
** Project changed: keystone => openstack-api-site
** Tags added: identity-api
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1313505
Title:
Typo in API doc: "provers" should be "provi
Brant: Thanks!
** Changed in: keystone
Status: Incomplete => Invalid
** Changed in: devstack
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/13
It is an undocumented API in v2, and has been superseded by a v3
extension that is much more efficient:
https://github.com/openstack/identity-api/blob/master/openstack-
identity-api/v3/src/markdown/identity-api-v3-os-revoke-ext.md
I moved this to openstack-api-site assuming you were intending t
Nothing here seems relevant to keystoneclient AFAICT, please re-add if
I'm mistaken.
** No longer affects: python-keystoneclient
--
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/
This doesn't appear to be an issue in master (demonstrated below), but
IS reproducible on stable/icehouse. Is this reproducible outside of
tests?
$ nosetests keystone.tests.test_auth
--
** 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/1315188
Title:
No init.d script included in icehouse ubuntu packaging
Status in “keysto
** Also affects: keystone/havana
Importance: Undecided
Status: New
** Changed in: keystone/havana
Status: New => In Progress
** Changed in: keystone/havana
Importance: Undecided => Low
** Changed in: keystone/havana
Assignee: (unassigned) => wanghong (w-wanghong)
--
Yo
** Also affects: keystone/havana
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Invalid
** Changed in: keystone/havana
Status: New => Triaged
** Changed in: keystone/havana
Importance: Undecided => Medium
** Changed in: keystone/havana
A
Eric: Wow, fantastic analysis - thank you! I agree with your path
forward, although I'd be happy with (1) as an easy first step until
someone has time/interest to pursue (2), as the additional flexibility
would provide a better long term solution.
** Tags removed: havana-backport-potential
** Tags
** No longer affects: keystone
--
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/1288230
Title:
A project shouldn't be deleted when there are instances running
Status in O
I do not think it makes sense to default the internal and admin URLs to
an arbitrary value, as not all services necessarily utilize those
interfaces. That said, making them both optional arguments, which they
don't appear to be, seems like a reasonable step.
** Project changed: keystone => python-
Red Hat doesn't track LP so this needs to be filed downstream:
https://bugzilla.redhat.com/buglist.cgi?product=RDO
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
htt
** 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/1319425
Title:
keystone link not created in /etc/init.d
Status in “keystone” package in
avior.
** Affects: keystone
Importance: Low
Assignee: Dolph Mathews (dolph)
Status: Triaged
** Tags: user-experience
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1322187
I believe I saw this issue being discussed as either a tempest or
grenade issue, but I'm unable to find the bug report... filing against
those projects in hopes of seeing this marked as a dupe :) Otherwise,
poke me if I'm mistaken.
** Also affects: tempest
Importance: Undecided
Status: N
Thanks, treinish!
** 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/1321797
Title:
Tempest fails on backports to Icehouse
Sta
Most of the issues described here are resolved by following the dev docs
[1] instead of the "install from source" docs. I think it would be best
to merge these two documents, or just outright nuke the "install from
packaging" [2] page since that should really be documented downstream,
or in opensta
We now have containers for users (domains and external IdPs), which I
think satisfies the requirement for certain users to carry a special
designation (they could be owned by a service domain, for example).
** Changed in: keystone
Importance: Medium => Wishlist
** Changed in: keystone
S
++
** Changed in: keystone
Status: Triaged => 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/1065233
Title:
Roles in XML response of v2 Validate Token Call not inline
IIRC, this was actually being caused by an out-of-tree patch being
carried by Debian. Please re-open if I'm mistaken.
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Key
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
** Changed in: keystone/icehouse
Status: New => Triaged
** Changed in: keystone/icehouse
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
** 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/1312858
Title:
Keystone + Devstack fail when KEYSTONE_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/1250617
Title:
Limited use trusts
Status in OpenStack I
** 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/1174499
Title:
Keystone token hashing is MD5
Status in
** 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/1255321
Title:
v3 token requests result in 500 error whe
Removed python-keystoneclient from this bug due to launchpad issues -
fix released in python-keystoneclient 0.9.0.
** No longer affects: python-keystoneclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.l
** Also affects: keystone/icehouse
Importance: Undecided
Status: New
** Changed in: keystone/icehouse
Importance: Undecided => Medium
** Changed in: keystone/icehouse
Assignee: (unassigned) => Emilien Macchi (emilienm)
** Changed in: keystone/icehouse
Status: New => In P
** Also affects: openstack-manuals
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/1314125
Title:
No errors when creating keystone tables when
Public bug reported:
The v3 API specifies that endpoints appearing in the service catalog
should have an ID [1].
This patch finally introduced v3 support for the KVS and templated
backends, but unfortunately does not address the lack of endpoint IDs.
Even in the case of the KVS and templated impl
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1326811
Title:
Client failing with six =>1.6 error
Status in OpenSt
** Changed in: keystone
Importance: Undecided => Critical
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Yahoo!
Engi
The policy rules you're looking at apply to the v3 API, but the calls to
assert_admin() you've cited are part of the v2 API. The v3 API supports
fairly granular policy enforcement, but the v2 API is generally binary
(you're either "admin" or not, and all that policy does is define what
"admin" mean
That's originally by design, but I agree with the notion that users
should be able to delete their own tokens, even though it's
traditionally an administrative function (I see it as "logging out").
** Changed in: keystone
Importance: Undecided => Wishlist
** Changed in: keystone
Status:
If you find that it's not addressed in 0.9.0, please comment here so we
can re-open this. Thanks!
** 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.
** Project changed: keystone => python-keystoneclient
** Tags added: user-experience
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1328359
Title:
keystone uses incorrect OS_AUTH_URL
** Tags removed: documentation
** Tags added: identity-api
** Project changed: keystone => openstack-api-site
** Changed in: openstack-api-site
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keyst
Is this an issue with PBR or how we're using it?
** Changed in: keystone
Status: New => Incomplete
** Also affects: pbr
Importance: Undecided
Status: New
** Changed in: pbr
Status: New => Incomplete
--
You received this bug notification because you are a member of Yahoo
This shouldn't affect keystone, as we neither specify nor implement this
resource.
The apparently equivalent call that we do implement is:
GET /v3/role_assignments?user.id={user_id}
https://github.com/openstack/identity-api/blob/master/v3/src/markdown
/identity-api-v3.md#list-effective-role-as
** Changed in: keystone
Status: Incomplete => Invalid
** Changed in: pbr
Status: Incomplete => 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/1330771
Title:
pbr as ru
Public bug reported:
In console.html, I got:
Log: n-api-meta not allowed to have ERRORS or TRACES
And in logs/screen-n-api-meta.txt.gz:
2014-06-18 02:51:38.284 DEBUG nova.openstack.common.policy
[req-fe1ab254-c41e-41b0-8070-1b1bcc8ca41f None None] Rule
network:get_fixed_ip_by_address will be
501 - 600 of 619 matches
Mail list logo
