there is no obvious bug here, if it is a refactor, simply propose the
patch
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.laun
sounds like this was user error in the way auth_version was being passed
in, doesn't affect keystone
** 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 Identity (keyston
this was fixed by the patch in #6
** Changed in: keystone
Status: In Progress => Fix Released
--
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/1387379
Title:
marking keystone as invalid since we have a duplicate bug here: 1519580
and we now use JSON schema validation for our v3 calls
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribe
*** This bug is a duplicate of bug 1332666 ***
https://bugs.launchpad.net/bugs/1332666
** This bug has been marked a duplicate of bug 1332666
Poor performance on delete_tokens due to missing indexes
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
`*requirements` target name is wrong, isn't it?.
```
$ make pip-test-requirements
make: Nothing to be done for 'pip-test-requirements'.
$ make pip-test-requirements
Installing cloud-init test dependencies...
pip install -r "pip-test-requirements.txt" -q
Could not open requir
this is covered by revocation events and audit ids that have been around
for a few releases
** Changed in: keystone
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keyst
this should be reproposed as a blueprint/spec, and since it's been ~2
years with no comments, i'm going to assume it's OK to mark this as
won't fix since no one wants to pick up the work
** Changed in: keystone
Status: Triaged => Won't Fix
--
You received this bug notification because you
we no longer have images in our docs
** Changed in: keystone
Status: Confirmed => Invalid
--
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/1121648
Title:
conv
this is a blueprint/spec
** Changed in: keystone
Status: Triaged => Invalid
--
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/1070637
Title:
create tokens scop
sorry dolph, as you have told me many times, the admin token itself
carries no authorization. if you disagree open a bug against
openstackclient to have this as a client specific feature, keystone
server shouldn't change the way it's handled
** Changed in: keystone
Status: Confirmed => Won'
Public bug reported:
I have a setup with 2 Network nodes, with bridge_mappings of l2 agents as
follows.
Network Node 1 : bridge_mappings: provider:10:1000
Network Node 2 : bridge_mappings: physnet1:1000:1500
Now, I create a provider network.
neutron net-create net1 --provider:network_type vlan
it seems like nova has removed the mechanism to register and unregister
models, as have other projects, like congress:
https://github.com/openstack/congress/commit/63976719d6cfdc8d5518c7378d52d30c739b8ebd
by the looks of it, only glance supports it:
http://hound.openstack.org/?q=register_model&i=n
lots of back and forth on this one, i think we agreed that it's fine on
specs.openstack.org/keystone
** 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
the patches associated with this bug are abandoned and as written in #2,
install_venv.py is gone from master
** 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 I
use openstackclient for this, the use of `keystone' has been deprecated,
i'm surprised you are not receiving error/deprecation warnings when
using that command.
in openstackclient, it would be `openstack user create xyz123` with
--enable and --disable being FLAGS and not options like in
keystonecl
role assignments in ldap has been deprecated for at least one release,
this will not be fixed
** 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 OpenStack Identity (keystone
Public bug reported:
If I launch a stack via the dashboard and provide an environments file I
expected that the values specified in the parameters section of the
environment file would be the selected parameter values in the Launch
Stack dialogue. On our Liberty installation this doesn't appear to
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1264261
Ti
write support for the identity ldap backend is being deprecated
** 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).
https://bugs.launchpad.ne
im marking keystone as invalid for now since this seems like it's fuel
related, update if i'm incorrect
** 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 Identity (keys
we'll be deprecating all LDAP backends that aren't identity
** Changed in: keystone
Status: Incomplete => Won't Fix
--
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/b
Public bug reported:
We have just upgraded from Juno to Liberty.
A heat template (that used to work in Juno) declares the following parameter:
instance_type:
type: string
description: The flavour the webserver is to run on
default: m2.xsmall
constraints:
- allowed_values:
we will be deprecating support for user and group create/delete/update
in mitaka, marking this as won't fix as it is not a security issue and
does not align with project plans
** Changed in: keystone
Status: In Progress => Won't Fix
--
You received this bug notification because you are a
we are going to deprecate support for create/update/delete for users and
groups in LDAP since it is a very uncommon use case. marking as won't
fix.
** Changed in: keystone
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
the json schema should address this now, as it's a required field:
https://github.com/openstack/keystone/blob/master/keystone/catalog/schema.py
** Changed in: keystone
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
i think the testing here is sufficient
https://github.com/openstack/keystone/blob/5de11025f45ca10d2b02b70234c1305fae91766c/keystone/tests/unit/test_backend.py#L1101-L1148
and covers a lot of what was in the abandoned patch
** Changed in: keystone
Status: In Progress => Invalid
--
You rece
we don't use WADLs for v3, we settled on RST and publish here:
http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-
api-v3.html
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, w
init scripts are not keystone's responsibility, simply because they will
be different for each deployment. this is a configuration management
issue and folks should use tools they want and prefer rather than
something the keystone team bakes up.
** Changed in: keystone
Status: Triaged => Wo
This is clearly not something we can support in LDAP. We aren't looking
to store the tokens etc (we've deprecated/removed a number of ldap
backends).
** Changed in: keystone
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
In some select filters (I found three pages, see screenshots) several
texts of this filters, lack the equals symbol "=" like the rest of
options of the same filter.
** Affects: horizon
Importance: Undecided
Assignee: Floren (florenllanos)
Status: New
** T
** No longer affects: python-glanceclient
--
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/1520937
Title:
Nova strips the path from glance servers specificed in
[glance]
It looks like glanceclient may make it exceedingly difficult to add in a
path-prefix in the way nova is consuming it.
** Also affects: python-glanceclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
Nova strips out the path from the URL for any glance server in the
"api_servers" configuration option. This prevents the use of
/image as part of the location for glance to be specified.
the code in "nova.image.glance" for "get_api_servers" silently drops the
path on the floo
The issue here is cause that in model is used with_variant type [1] So,
compare_type method see [2] and seems that it compares them as equal.
This is the only case in Neutron, so there are no other places to fix
this. I will propose patch for oslo.db, not sure that there is something
that should be
35 matches
Mail list logo
