** Also affects: nova-powervm
Importance: Undecided
Status: New
--
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/1771538
Title:
PowerVM config drive path is not
Public bug reported:
An optional (defaults to None) host argument was added to the
get_device_details RPC method a long time ago [1] but a recent change
[2] to the master branch has made that no longer really optional, at
least for the pvm_sea agent from openstack/networking-powervm, since not
Public bug reported:
In a stable/queens devstack environment with multiple PowerVM compute
nodes, everytime I see this in devstack@n-cond-cell1.service logs:
Jul 11 15:48:57 myhostname nova-conductor[3796]: DEBUG
nova.conductor.manager [None req-af22375c-f920-4747-bd2f-0de80ee69465
admin admin]
** Changed in: pypowervm
Status: In Progress => Fix Released
--
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/1766692
Title:
instance.uuid no longer being a str
Public bug reported:
keystone was not able to find any users while the LDAP user name
attribute was configured to "samaccountname", but could find users when
reconfigured to use "sAMAccountName". LDAP is not supposed to be case-
sensitive, so either should work.
This appears to be a result of
** Also affects: rpm-packaging
Importance: Undecided
Status: New
** No longer affects: rpm-packaging
** Project changed: nova => rpm-packaging
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Project changed: nova-powervm => 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/1605098
Title:
Nova usage not showing server real uptime
Status in OpenStack
Public bug reported:
The keystone v2 API has been removed, yet we still define the
member_role_id and member_role_name conf options that say they are for
v2. It appears that they may be used in some v3 code. That should either
be modified so that these can be removed, or the help and docs for
Public bug reported:
keystone returns HTTP 404 if you try to create a trust with a role that
you don't have. This is not an appropriate error code for that case. It
should be HTTP 400 (Bad Request).
Found in Pike
** Affects: keystone
Importance: Undecided
Status: New
--
You
Public bug reported:
https://github.com/openstack/keystone/commit/51d5597df729158d15b71e2ba80ab103df5d55f8
#diff-271e091a68fb7b6526431423e4efe6e5 attempts to clear the default
project_id for users if/when the project to which that ID belongs is
deleted. However it only calls the identity driver
Yeah, those instructions were followed, but the problem here was that
some users didn't have a value set in the property that was used for
name. More specifically, the customer used a field that holds the email
address as the name, and some users didn't have an email address. But
even beyond that,
Found the problem and proposing a fix...
** Changed in: keystone
Status: Expired => Confirmed
** Changed in: keystone
Assignee: (unassigned) => Matthew Edmonds (edmondsw)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subs
uot; rule. That rule is not defined, so what
actually gets checked is the default rule. We must fix this before
shipping Pike to avoid breaking backward compatibility.
** Affects: keystone
Importance: Undecided
Assignee: Matthew Edmonds (edmondsw)
Status: New
** Changed in: ke
that the default rule can't be
used like that anymore because it won't be checked just because you
didn't define another rule in policy.json.
** Affects: keystone
Importance: Undecided
Assignee: Matthew Edmonds (edmondsw)
Status: In Progress
** Changed in: keystone
Assignee: (unassigned
Public bug reported:
identity:get_identity_providers should be identity:get_identity_provider
(singular) since a GET is targeted on a single provider.
found in master (pike)
** Affects: keystone
Importance: Undecided
Assignee: Matthew Edmonds (edmondsw)
Status: In Progress
Public bug reported:
I had to root cause a very odd problem today, where a user complained
that they had a token that worked with neutron but didn't work with
keystone. E.g. they could list networks, but couldn't list projects. I
thought there must be some mistake, but I was finally able to
Public bug reported:
As seen with the following curl command, neutron accepts float values
for quotas that should require ints. It coverts them to an int, but it
should have returned HTTP 400 instead. The conversion it's doing may or
may not have the same results in python3 as it does here in
I don't think this is totally invalid. It's right to return a 500, but I
think we could improve the error message that goes with that. I.e., add
code to raise LDAPServerConnectionError once the bug Breton opened in
comment 6 is addressed.
** Changed in: keystone
Status: Invalid => New
--
That I would agree with.
** Changed in: keystone
Status: Invalid => 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/1684994
Title:
POST v3/auth/tokens
Public bug reported:
The "network:attach_external_network" policy is being checked in nova-
compute rather than in nova-api.
1) Only the api process should be doing policy checks.
2) Someone who wants to override policy for this would have to put a
policy.json file on each host, which is
*** This bug is a duplicate of bug 1636157 ***
https://bugs.launchpad.net/bugs/1636157
** This bug has been marked a duplicate of bug 1636157
os-server-groups uses same policy.json rule for all CRUD operations
--
You received this bug notification because you are a member of Yahoo!
b85d6c6c-e385-4601-aa47-5c580f893c9b] Neutron server returns request_ids:
['req-682b2d6b-768f-413d-862c-32490cad5589']
2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance:
b85d6c6c-e385-4601-aa47-5c580f893c9b]
found in newton
** Affects: nova
Importance: Undecided
Public bug reported:
nova.api.openstack.compute.server_groups.ServerGroupController uses the
same policy check (os_compute_api:os-server-groups) for show, delete,
index, and create, instead of separating these into separate checks
(e.g. os_compute_api:os-server-groups:delete). This makes it
Public bug reported:
the API documentation is missing any mention of what query parameters
are allowed for various APIs and how they work. E.g., it should mention
the "scope.project.id" query parameter for v3/role_assignments, as used
by `openstack user list --project `.
** Affects: keystone
same issue found in nova as well as cinder
** Also affects: nova
Importance: Undecided
Status: New
** Description changed:
I don't quite understand what a quota class set is, since there is no
- documentation (see https://bugs.launchpad.net/cinder/+bug/1415214), but
+ documentation
Public bug reported:
http://developer.openstack.org/api-ref does not document the os-quota-
class-sets APIs for either nova or cinder.
** Affects: cinder
Importance: Undecided
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Tags: api-ref
** Also
Public bug reported:
When an LDAP user is deleted, keystone removes it from groups that match
the group_filter conf setting, but fails to remove it from any other
groups. It should remove it from all groups.
** Affects: keystone
Importance: Undecided
Status: New
--
You received
Public bug reported:
The same problem reported and fixed for users as
https://bugs.launchpad.net/keystone/+bug/1577804 also exists for groups.
** Affects: keystone
Importance: Undecided
Status: New
** Tags: mitaka-backport-potential
** Tags added: mitaka-backport-potential
--
Public bug reported:
HTTP 500 being returned when the request body for POST /v3/auth/tokens
has an empty string in place of one of the dicts that should be passed
in. This shows that the code is not doing proper input validation. It
should detect the user error and return an HTTP 400. Here's an
Public bug reported:
using the LDAP driver with user_filter, a GET /v3/users?name=
returns users that do not match the filter.
e.g.:
user_filter = (|(uid=arc1_admin)(uid=arc1_stgmgr))
# openstack user list
++-+
| ID
Public bug reported:
When a user attempts to rename a project via the PATCH
v3/projects/{project_id} API, and the new name is already in-use, rather
than return a nice error explaining that the name is in use, keystone
blows up and returns an HTTP 500:
# curl -k -1 -i -X PATCH
Public bug reported:
openstack project set accepts invalid properties, and even somehow sets
their values
# openstack project set ABC --property xyz=pqr
# openstack project show ABC
+-+--+
| Field | Value|
Public bug reported:
keystone-manage bootstrap creates a role assignment for the specified
user on the specified project. That is one way someone might want to do
bootstrapping, but there are good reasons a user may need/prefer:
1) user-domain role assignment... e.g. Switching identity drivers
Public bug reported:
keystone-manage bootstrap attempts to create the specified user and then
handles a Conflict error as notice that the user already exists. This
works for the default SQL identity driver, but does not work for drivers
that do not support creating users. In order to work for all
looks like this was removed by
https://github.com/openstack/keystoneauth/commit/473b70566a88ce84967654e5fc2dd87e04538fb9
The assumption there is that nobody would ever go to the ServiceCatalog
directly, but unfortunately nova does. This issue was found when we were
looking at
Public bug reported:
keystone's requirements.txt includes several things that are really
optional dependencies, only needed if you are using certain features.
These should be moved out of requirements.txt and handled as extras in
setup.cfg. A few of these that I've noticed are:
passlib (only
Public bug reported:
The following deprecation warning appears to be logged in all cases,
regardless of neutron or other configuration.
2015-09-18 10:59:40.472 20552 WARNING neutron.quota [-] Deprecated:
Registering resources to apply quota limits to using the quota_items
option is deprecated as
Public bug reported:
nova.network.neutronv2.api.neutron_opts almost all say in their help
that they are deprecated, but that's not the correct way to deprecate
things. Because deprecated_for_removal was not used, usage of these
options is not resulting in appropriate log warnings.
Found on
Public bug reported:
olso_vmware is not referenced in glance python code, yet
requirements.txt includes it. This should either be removed from
requirements entirely, or moved to test-requirements.
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug
** Project changed: nova = python-cinderclient
** Changed in: python-cinderclient
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Also affects: ceilometer
Importance: Undecided
Status: New
** No longer affects: ceilometer
** Project changed: keystone = ceilometer
** Changed in: ceilometer
Status: Incomplete = New
--
You received this bug notification because you are a member of Yahoo!
Engineering
** 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 Compute (nova).
https://bugs.launchpad.net/bugs/1421863
Title:
Can not find policy directory:
Public bug reported:
The keystone.common.controller._get_domain_id_for_list_request comment says the
below:
Get the domain_id for a v3 list call.
If we running with multiple domain drivers, then the caller must
specify a domain_id either as a filter or as part of the
This was not an unscoped token. Requested as follows:
curl -k -i -X POST https://127.0.0.1:5000/v3/auth/tokens -H Accept:
application/json -H Content-Type: application/json -d '{auth:
{scope: {project: {name: ibm-default, domain: {name:
Default}}}, identity: {methods: [password], password: {user:
'get_domain_by_name'
** Affects: keystone
Importance: Undecided
Assignee: Matthew Edmonds (edmondsw)
Status: New
** Changed in: keystone
Assignee: (unassigned) = Matthew Edmonds (edmondsw)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Connection: close
Content-Type: application/json
{error: {message: KS-BAC2700 KS-6C5716A Invalid input for field
'url'. The value is
'https://[fd55:faaf:e1ab:3ea:9:114:251:134]:8777/v2'., code: 400,
title: Bad Request}}
** Affects: keystone
Importance: Undecided
Assignee: Matthew Edmonds
,
2014-07-23 04:31:08.206 4449 TRACE keystone.common.wsgi KeyError: 'group_id'
It appears that the dictionary format was changed and the error path
code was not updated to expect the new format.
** Affects: keystone
Importance: Undecided
Assignee: Matthew Edmonds (edmondsw)
Status
Public bug reported:
We've found that while with Icehouse we were able to specify extra_specs
values as ints or floats, in Juno the command fails unless we make these
values strings by quoting them. This breaks backward compatibility.
compare Icehouse:
curl -k -i -X POST
Public bug reported:
HTTP 413 is supposed to mean (per RFC2616) that the request entity was
too large. E.g., if you send an enormous body with the request. That is
not at all how it is being used in the server resize request example
below. The nova/api/openstack/compute/servers.py is coded to
*** This bug is a duplicate of bug 1244842 ***
https://bugs.launchpad.net/bugs/1244842
I was using havana, apparently pre-backport. Marked this as a dup. Thank
you.
** This bug has been marked a duplicate of bug 1244842
NoopQuotaDriver returns usages incorrect format
--
You received
Public bug reported:
when quota_driver=nova.quota.NoopQuotaDriver in nova.conf, a GET
v2/{tenant_id}/limits request fails with HTTP 400 and api.log shows the
following stacktrace:
2014-03-03 04:16:31.468 3182 TRACE nova.api.openstack.wsgi Traceback (most
recent call last):
2014-03-03
51 matches
Mail list logo
