Public bug reported:
The PCI API support was enabled for v3 but never for V2. However V2.1 is
built on v3 and it includes everything in v3. So we are disabling pci
support in v3. and then will renable in the v2 microversions as one of
the early microversion changes.
This bug is to keep track of
Public bug reported:
There have been reports that the api sample tests for v2.1 are taking
significantly longer to run that the v2 versions. This needs to be
investigated and fixed. Eg. is it setup time (stevedore?), is it
jsonschema input validation? Or something else
** Affects: nova
** Changed in: nova
Status: New = Confirmed
** 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 OpenStack Compute (nova).
This is already implemented in Juno as secgroup-delete-group-rule
** Changed in: nova
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/1375564
This doesn't appear to be reproducible anymore and we now handle utf8
host names correctly
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
It's an admin api so I don't think we need to quota restrict it.
** Changed in: nova
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
As mentioned above, this is an async call so we have already returned
from the API before we know the migration failed. The tasks API will
address this in the future (you'll need to poll but you will be able to
find out what happened).
** Changed in: nova
Status: Confirmed = Invalid
--
** Changed in: nova
Status: Confirmed = 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/1208743
Title:
network uuid hasn't been checked in create server
Public bug reported:
Glance currently 500's when passed an image name with a 4-byte utf-8
character in the name. This is because the mysql utf-8 type only handles
up to 3-byte utf-8 characters:
See http://stackoverflow.com/questions/10957238/incorrect-string-value-
It turns out that both the JSON and XML deserializers in nova will
detect invalid utf8 sequences so this bug is invalid. The only issue is
on the tempest test side
** Changed in: nova
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Backport patch for this was merged actually merged afew days ago.
https://review.openstack.org/#/c/106674/
Sorry should have linked to it earlier.
** Changed in: nova
Status: Won't Fix = Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering
This is a novaclient bug not a nova bug (it never reaches Nova). But
regardless I'm not convinced we should fix this. Its stock standard unix
command line syntax that something starting with '-' would be
interpreted as an option rather than an argument unless specially
quoted.
** Also affects:
Public bug reported:
When secgroup-create is passed a name or description which is an empty
string the error message does not specify which field is invalid. We
should fix this.
** Affects: nova
Importance: Undecided
Assignee: Christopher Yeoh (cyeoh-0)
Status: In Progress
Public bug reported:
The quota delete rest api should have better input validation as bad
input data can currently silently fail
** Affects: nova
Importance: Undecided
Assignee: Christopher Yeoh (cyeoh-0)
Status: New
** Tags: api
--
You received this bug notification
Agreed, looks like this is already implemented
** Changed in: nova
Status: New = Fix Released
** Changed in: python-novaclient
Status: New = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
** No longer affects: 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/1352950
Title:
os-interface create API docs are wrong
Status in OpenStack API documentation
for ram: Requested 51137, but already used 128 of 51200 ram
2014-08-04 05:27:04.305 12275 TRACE nova.api.openstack
** Affects: nova
Importance: Low
Assignee: Christopher Yeoh (cyeoh-0)
Status: New
** Tags: api
--
You received this bug notification because you are a member of Yahoo
/a278802/logs/screen-n-api.txt
** Affects: nova
Importance: Medium
Assignee: Christopher Yeoh (cyeoh-0)
Status: New
** Tags: api
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https
-31 07:14:07.574 28614 TRACE nova.api.openstack
http://logs.openstack.org/72/109872/1/check/check-tempest-dsvm-neutron-
full/7e11304/logs/screen-n-api.txt.gz?
** Affects: nova
Importance: Low
Assignee: Christopher Yeoh (cyeoh-0)
Status: New
** Tags: api
--
You received
So in the end I don't think this is a Nova bug. The first line of the
request to the Nova API server looks like this:
DELETE /v2/f9cea8784d7245e5a8022a259bb92d90/os-server-
groups/{u'policies': [u'affinity'], u'name': u'server-group-1646113520',
u'id': u'b5316a4a-f6eb-4a7f-8b24-028b799bf6a9',
Public bug reported:
We should fix the remaining API cases where the 413 status code is used
instead of 403 when the failure is due to running out of quota
** Affects: nova
Importance: Low
Assignee: Christopher Yeoh (cyeoh-0)
Status: New
** Tags: api
--
You received
The resize call is asynchronous - eg the API returns the 202 to the
client possibly before the actual resize attempt is made. 202 just means
that the request has been accepted, not that it has been accepted. In
order to determine if the resize has succeded you need to poll
** Changed in: nova
The resize call (and many others) are asynchronous. 202 just means that
the request has been accepted, not that it has succeeded. The API
returns to the client before the resize is attempted - it doesn't know
if it is going to succeed or not.
In order to determine if the resize succeeded you need
I don't see how this is a Nova bug?
** Changed in: nova
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/1283214
Title:
Need documentation
Sorry doesn't appear to be fixable atm
** Changed in: nova
Status: Confirmed = Won't Fix
--
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/918238
Title:
wrong
The first thing we do is log the exception. This happens before we
attempt to return any information to the client or do any other
processing. So I don't think we need any other fallback. Unless you have
a testcase which demonstrates this is necessary.
** Changed in: nova
Status: In
This is a python-novaclient bug, not a nova bug
** Also affects: python-novaclient
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Marking this as WontFix only because I think its a feature request, not
a bug and we don't need to keep track of it in the bugs database. Please
submit this as a proposal to nova-specs and blueprint
** Changed in: nova
Status: New = Won't Fix
--
You received this bug notification because
This is a novaclient feature, not a nova one
** Also affects: python-novaclient
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Invalid
** Changed in: python-novaclient
Importance: Undecided = Wishlist
--
You received this bug notification because you
Public bug reported:
The V3 API multinic extension is missing the expected errors decorator.
This means that unexpected exceptions from Nova internals are not
properly caught.
** Affects: nova
Importance: Undecided
Assignee: Christopher Yeoh (cyeoh-0)
Status: New
** Tags
The URL supplied is invalid if /tenant_id/servers/{server_id} does not
exist because server_id is not a valid server id. So 404 is the
appropriate response code.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Thanks Mike - any chance you could attach the output from keystone
service-list and endpoint-list ?
Adding python-cinderclient as I'm guessing the problem might be in there
somewhere.
** Also affects: python-cinderclient
Importance: Undecided
Status: New
--
You received this bug
** Changed in: nova
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/1246987
Title:
check_policy does not work correctly
Status in
This is getting handled as part of the process of bubbling up all of the
policy checks to the API level - although targetted for the V3 API it
will also affect the V2 API.
https://blueprints.launchpad.net/nova/+spec/v3-api-policy
So I'm closing this bug as it will be tracked through the
Since this is being handled by the v3-api-policy blueprint and being
tracked by that blueprint, I'm closing this bug report
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
XML support is going away so closing this bug
** Changed in: nova
Status: Confirmed = 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/1245764
Title:
The
headed in other places in the API).
** Affects: nova
Importance: High
Assignee: Christopher Yeoh (cyeoh-0)
Status: New
** Tags: api
** Changed in: nova
Importance: Undecided = High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
We can't fix this in Nova V2 as it is a backwards incompatible change,
so the only place we can fix it is the docs. Sorry.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Changed in: nova
Status: In Progress = Invalid
** Tags added: api
--
You received
Public bug reported:
The v2 API sample for os-assisted volume snapshot is wrong and given it
is used for documentation misleading to users of the API
** Affects: nova
Importance: Undecided
Assignee: Christopher Yeoh (cyeoh-0)
Status: New
** Tags: api
** Tags added: api
So rather than multiple bug reports documenting bits missing in the
proxying of neutron information in Nova I think instead we should do
this as a single blueprint which covers all of the different areas where
we need better neutron support.
Though note that the long term goal is to remove
So rather than multiple bug reports documenting bits missing in the
proxying of neutron information in Nova I think instead we should do
this as a single blueprint which covers all of the different areas where
we need better neutron support.
Though note that the long term goal is to remove
Public bug reported:
Sometimes servers fail to startup - intermittent gate/check bug
Example error:
2014-01-28 02:14:36.309 ERROR nova.scheduler.filter_scheduler
[req-a617cb8a-4f34-42f9-a4a7-e951cf538219
InstanceActionsTestJSON-tempest-857832860-user
Public bug reported:
The V2 API instance_actions extension (addFloatingIp) does not catch
InstanceNotFound exceptions which causes a traceback in the nova api log
** Affects: nova
Importance: Undecided
Assignee: Christopher Yeoh (cyeoh-0)
Status: In Progress
--
You received
*** This bug is a duplicate of bug 1262432 ***
https://bugs.launchpad.net/bugs/1262432
** This bug has been marked a duplicate of bug 1262432
tempest volume transfer test can race against other tenants
--
You received this bug notification because you are a member of Yahoo!
Engineering
Used limits will be removed in icehouse as will most if not of all of
limits (there are a couple of changesets already in the queue doing
this).
** Changed in: nova
Status: New = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
From the logs it looks like you have some authentication issues with
your setup which probably explains the very long timeout.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
The return code is 202 and is returned before its known if the operation
has succeeded or not.
Defintion for 202 is The request has been accepted for processing, but
the processing has not been completed. The request may or may not
eventually be acted upon, as it may be disallowed when
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1182883
Title:
List servers matching a regex fails with Quantum
Status in OpenStack
** Changed in: nova
Status: New = Won't Fix
--
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/1196255
Title:
Cannot filter 'soft-deletd' instances via nova api
Looks like this has been fixed in the doco
** Changed in: nova
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/1205841
Title:
API
I think the problem seen in http://logs.openstack.org/22765/4/check
/gate-tempest-devstack-vm-full/6460/ should be fixed by
https://review.openstack.org/#/c/23067/3 which ups the timeout to 60
secs.
There's two timeout's we see here: One in RemoteClient's __init__ making
the initial connection
51 matches
Mail list logo
