man page is generated in packaging - not part of the upstream keystone
repo
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Changed in: keystone
Status: Triaged = Invalid
** Changed in: keystone
Assignee: Adam Gandelman (gandelman-a) = (unassigned)
man page is generated in packaging - not part of the upstream keystone
repo
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Changed in: keystone
Status: Triaged = Invalid
** Changed in: keystone
Assignee: Adam Gandelman (gandelman-a) = (unassigned)
** Changed in: keystone
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078947
Title:
auth_token failure if signing_dir not specified running under upstart
To manage
also linking to python-keystoneclient project since it's CLI related
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Importance: Undecided = High
** Changed in: python-keystoneclient
Status: New = Triaged
**
also linking to python-keystoneclient project since it's CLI related
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Importance: Undecided = High
** Changed in: python-keystoneclient
Status: New = Triaged
**
russel - description is good, run with it.
** Description changed:
Admin API /v2.0/tenants/{tenant_id}/users/{user_id}/roles doesn't
- validate token
+ validate the authentication token before returning a response.
- we can get the same result without a token in HTTP head.
+ i.e. we can get
Good description, ack.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/988920
Title:
Token authentication for a user in a disabled tenant does not raise
Unauthorized error
To
russel - description is good, run with it.
** Description changed:
Admin API /v2.0/tenants/{tenant_id}/users/{user_id}/roles doesn't
- validate token
+ validate the authentication token before returning a response.
- we can get the same result without a token in HTTP head.
+ i.e. we can get
Good description, ack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988920
Title:
Token authentication for a user in a disabled tenant does not raise
Unauthorized error
To manage notifications
** Changed in: keystone
Milestone: None = folsom-rc1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1035428
Title:
authenticate in ldap backend doesn't return a list of roles
** Changed in: keystone
Milestone: None = folsom-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035428
Title:
authenticate in ldap backend doesn't return a list of roles
To manage
Thanks Lamont,
In the V2 API, you're quite correct. We're aiming to have this resolved
with the V3 API - linking to blueprint
** Changed in: keystone
Status: New = Triaged
** Changed in: keystone
Importance: Undecided = High
--
You received this bug notification because you are a
Thanks Lamont,
In the V2 API, you're quite correct. We're aiming to have this resolved
with the V3 API - linking to blueprint
** Changed in: keystone
Status: New = Triaged
** Changed in: keystone
Importance: Undecided = High
--
You received this bug notification because you are a
** Changed in: keystone
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990162
Title:
armhf version is unusable -- task switches will cause sigsegv's
To manage
** Changed in: keystone
Status: New = Fix Released
** Changed in: keystone
Status: Fix Released = Confirmed
** Changed in: keystone
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: keystone
Status: New = Fix Released
** Changed in: keystone
Status: Fix Released = Confirmed
** Changed in: keystone
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: essex-backport-potential
** Changed in: keystone
Milestone: None = folsom-1
** Changed in: keystone
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
** Tags added: essex-backport-potential
** Changed in: keystone
Milestone: None = folsom-1
** Changed in: keystone
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: keystone
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990162
Title:
armhf version is unusable -- task switches will cause sigsegv's
To manage
** Changed in: keystone
Milestone: None = essex-4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/907518
Title:
swift proxy cannot start when configured to use keystone
To
** Changed in: keystone
Milestone: None = essex-4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907518
Title:
swift proxy cannot start when configured to use keystone
To manage notifications
Adam - is this relevant to keystone itself (i.e something that should be
changed in setup.py?) or specific to packaging? I'm marking as invalid
based on the notes above, as it appears to be packaging specific.
** Changed in: keystone
Status: New = Invalid
--
You received this bug
Adam - is this relevant to keystone itself (i.e something that should be
changed in setup.py?) or specific to packaging? I'm marking as invalid
based on the notes above, as it appears to be packaging specific.
** Changed in: keystone
Status: New = Invalid
--
You received this bug
Mark et al -
I've run into the same bug, and Mark's PPA has a version which is
correctly installing. Thought the additional verification might be
useful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874417
Title:
pip command line fails immediately - can't use
To manage notifications about this bug go to:
Public bug reported:
When invoking pip on the command line, it immediately fails with:
$ pip
Traceback (most recent call last):
File /usr/local/bin/pip, line 5, in module
from pkg_resources import load_entry_point
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2676, in
Thanks Julian - completely missed that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874417
Title:
pip command line fails immediately - can't use
To manage notifications about this bug go to:
This bug surfaced again while testing the diablo-1 milestone against
Ubuntu maverick.
running /etc/init.d/nova-objectstore start right after the install
started the service without issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
This bug surfaced again while testing the diablo-1 milestone against
Ubuntu maverick.
running /etc/init.d/nova-objectstore start right after the install
started the service without issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
29 matches
Mail list logo
