Public bug reported:
Open the modal from for creating a volume from an image, an error message
appeared : "Unable to retrieve the Absolute Limits".
I saw an error in browser console : "SyntaxError: Unexpected token I in JSON at
position 76".
** Affects: horizon
Importance: Undecided
Public bug reported:
As of now, when user passes 'Accept' header in request other than JSON
and XML using curl command then it returns 200 OK response with json
format data.
In api-ref guide [1] also it's not clearly mentioned about what response
it should return if invalid value for 'Accept'
Public bug reported:
nova master as of 20170831
The _set_allocations method used to write allocations to the placement
API will raise a 400 when a resource class results in a NotFound
exception. We want that 400. The problem is that the message associated
with the error users the resource
Public bug reported:
The legacy API controller would resync and dirty the quotas at
particular intervals that pecan is missing. In particular it would
resync on GET operations[1] and dirty on deletes[2]. The pecan hook is
missing both of these cases.
1.
Public bug reported:
The pecan code is missing the logic to translate some of the
authorization failures into 404s instead of 403's.
https://github.com/openstack/neutron/blob/8d2c1bd88b14eefbea74c72f384cb9952e7ee62e/neutron/api/v2/base.py#L575-L585
Public bug reported:
The delete notifications under the old API controller used to contain
both the ID and the original copy of the resource being deleted. Pecan
broke that by only including the ID.
** Affects: neutron
Importance: High
Status: New
** Changed in: neutron
Public bug reported:
The legacy controller was validating that enabled, native pagination was
only set when the plugin actually supported native sorting. Pecan needs
to do this same thing for parity.
** Affects: neutron
Importance: High
Assignee: Kevin Benton (kevinbenton)
Public bug reported:
When a user passes in duplicate fields and empty fields, the old API
controller would strip these out before passing them to the plugin.
Pecan should do the same thing to preserve parity with the old
controller in case plugins are sensitive to these invalid filters.
**
Public bug reported:
Pecan is missing this logic in the old controller code that adds
'tenant_id' to the filters required by the policy engine when the
'project_id' field is specified:
https://github.com/openstack/neutron/blob/8d2c1bd88b14eefbea74c72f384cb9952e7ee62e/neutron/api/v2/base.py#L96
Public bug reported:
Similar to LP: #1714117, there appears to be a pair of tests that are
escaping and timing out, resulting in extra time that is not required
for the unit tests:
tests.unittests.test_datasource.test_openstack.TestOpenStackDataSource.test_datasource
Public bug reported:
The versioned notification samples in the docs used to be collapsible
and would be hidden by default, but with the new docs theme it looks
like that isn't working, and the show/hide button doesn't do anything
either:
Reviewed: https://review.openstack.org/499754
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=8d2c1bd88b14eefbea74c72f384cb9952e7ee62e
Submitter: Jenkins
Branch:master
commit 8d2c1bd88b14eefbea74c72f384cb9952e7ee62e
Author: Boden R
Date: Thu Aug
Public bug reported:
We are usng CloudStack with XenServer as hypervisor and we are getting
this:
Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-81-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:
It's long fixed.
** Changed in: neutron
Assignee: sudhakar kumar srivastava (sudhakar.srivastava) => (unassigned)
** Changed in: neutron
Status: Confirmed => Won't Fix
** Changed in: neutron
Status: Won't Fix => Fix Released
--
You received this bug notification because you
We currently compile v2.6.1 from sources for fullstack. I consider it's
fixed.
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Pecan is missing the emulated bulk create logic for core plugins that
don't support the bulk methods.
** Affects: neutron
Importance: High
Status: New
** Changed in: neutron
Importance: Undecided => High
--
You received this bug notification because you
Added ovsdbapp to the list of affected projects because I believe this
error comes from the library.
** Changed in: neutron
Milestone: pike-2 => None
** Also affects: ovsdbapp
Importance: Undecided
Status: New
** Changed in: ovsdbapp
Status: New => Confirmed
--
You
No hits in 7 days. I claim it's fixed. If not, reopen.
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1673531
Title:
Public bug reported:
The legacy controller validated the following things that the pecan API
is not.
* delete requests have no body
* the body must contain a resource or resources when POSTing to the
general collection controller
* All POSTed json must be a dict
These gaps were discovered
Based on the latest contents of the config qos guide [1], this has
already been fixed.
[1] https://github.com/openstack/neutron/blob/master/doc/source/admin
/config-qos.rst
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
The evacuate issue was fixed with change
Ic468cd57688b370a18cacfc6e0844a8201eb9ab3 but it's still a problem for
os-migrateLive.
** Changed in: nova
Status: Invalid => Confirmed
** Summary changed:
- evacuate API does not restrict one from trying to evacuate to the source host
+
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1682228
Title:
can't cross address scopes with DVR
Status in neutron:
Today I don't see gateway_external_network_id documented other than a
blank use of it in sample CLI output [1]. That said I don't see any
reason to leave this open as I'm not sure what needs to be documented.
When the deprecated option is removed, that should be marked with a doc
impact tag and
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1683102
Title:
Port data plane status extension implementation
The REST API handler code checks this, I just missed that since I was
expecting to find it in the nova.compute.api.API.evacuate method:
https://github.com/openstack/nova/blob/2a4ca8bd6aa40ccd26300feaef4267aa71f69abf/nova/api/openstack/compute/evacuate.py#L114
** Changed in: nova
Status:
Reviewed: https://review.openstack.org/499684
Committed:
https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=6e715ed580bf0f8ba5ff4c8e79b9ddba45d787c6
Submitter: Jenkins
Branch:master
commit 6e715ed580bf0f8ba5ff4c8e79b9ddba45d787c6
Author: Lucian Petrut
** Changed in: keystone (Ubuntu)
Status: In Progress => Invalid
** Changed in: cloud-archive
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
Agreeing with Tristan et al, and adding the "security" bug tag to
indicate it's a hardening opportunity (C1).
** Tags added: security
** Also affects: ossa
Importance: Undecided
Status: New
** Changed in: ossa
Status: New => Won't Fix
--
You received this bug notification
** Changed in: cloud-archive
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/1694337
Title:
Port information (binding:host_id) not updated for
Reviewed: https://review.openstack.org/490457
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=a58aa26450837bfb84ea3cfbc015a83d8541befd
Submitter: Jenkins
Branch:master
commit a58aa26450837bfb84ea3cfbc015a83d8541befd
Author: Bence Romsics
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-archive/mitaka
Status: New => Triaged
** Changed in: neutron (Ubuntu Xenial)
Status: New =>
Public bug reported:
The stylesheet referenced in
openstack_dashboard/templates/serial_console.html is incorrect, as the
CSS file has been changed to SCSS in
I0d421d931d252d821a7ecf19a750f73b8241c249:
Instead, the template needs to reference the SCSS file and compile it.
** Affects:
*** This bug is a duplicate of bug 1274427 ***
https://bugs.launchpad.net/bugs/1274427
** This bug is no longer a duplicate of bug 1514678
There is no Previous Hyperlink in Horizon when creating 250 instances
** This bug has been marked a duplicate of bug 1274427
Instance list
*** This bug is a duplicate of bug 1274427 ***
https://bugs.launchpad.net/bugs/1274427
** This bug is no longer a duplicate of bug 1514678
There is no Previous Hyperlink in Horizon when creating 250 instances
** This bug has been marked a duplicate of bug 1274427
Instance list
*** This bug is a duplicate of bug 1274427 ***
https://bugs.launchpad.net/bugs/1274427
** This bug is no longer a duplicate of bug 1514678
There is no Previous Hyperlink in Horizon when creating 250 instances
** This bug has been marked a duplicate of bug 1274427
Instance list
*** This bug is a duplicate of bug 1274427 ***
https://bugs.launchpad.net/bugs/1274427
** This bug is no longer a duplicate of bug 1514678
There is no Previous Hyperlink in Horizon when creating 250 instances
** This bug has been marked a duplicate of bug 1274427
Instance list
Meh, since I opened it, might as well use it.
** Changed in: nova
Status: Invalid => New
** Changed in: nova
Assignee: (unassigned) => Eric Fried (efried)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
Public bug reported:
Volume connections as well as vif ports are not cleaned up after a
failed instance spawn.
** Affects: compute-hyperv
Importance: Undecided
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Also affects: compute-hyperv
Sorry, opened the wrong 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/1714283
Title:
Placement API reference:
Public bug reported:
In the Placement API reference, the GET /traits [1] query parameter
'name' says it accepts a key called 'starts_with'. The actual API
accepts 'startswith' (no underscore).
[1] https://developer.openstack.org/api-ref/placement/#list-traits
** Affects: nova
Importance:
Public bug reported:
The Placement API user doc [1] says:
API Reference
A full API reference is forthcoming, but until then ...
That reference has since been published [2].
[1] https://docs.openstack.org/nova/pike/user/placement.html#api-reference
[2]
Public bug reported:
GET /resource_providers returns:
{
"resource_providers": [
{
"generation": 39,
"uuid": "213fd7f8-1e9f-466b-87bf-0902b0b3bc13",
"links": [
{
"href":
"/placement/resource_providers/213fd7f8-1e9f-466b-87bf-0902b0b3bc13",
** Changed in: neutron
Status: In Progress => Invalid
** Changed in: neutron
Assignee: Dongcan Ye (hellochosen) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This is pretty much working as designed. Nova is the owner of that
state, and will drive services to that state.
** 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
Kernel panics in guests are unlikely to be Nova bugs. This is probably
an underlying kvm / libvirt issue.
** Changed in: nova
Status: New => Incomplete
** Also affects: openstack-gate
Importance: Undecided
Status: New
** No longer affects: nova
--
You received this bug
For questions like this, please engage in IRC or the mailing list
** 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/1713466
This is really only a devstack fix
** Changed in: nova
Status: New => Confirmed
** No longer affects: nova
** No longer affects: neutron
** No longer affects: cinder
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
When a router is migrated from DVR to HA, all ports related to DVR
should be removed. But I still see port with device_owner
router_centralized_snat not removed.
** Affects: neutron
Importance: Undecided
Assignee: venkata anil (anil-venkata)
Status: New
Public bug reported:
Description
===
In an environment where there are multiple compute nodes with ironic driver,
when a compute node goes down, another compute node cannot take over ironic
nodes.
Steps to reproduce
==
1. Start multiple compute nodes with ironic driver.
Public bug reported:
When sending a SIGTERM to the main glance-api process,
api.log shows
2017-08-31 13:10:30.996 10618 INFO glance.common.wsgi [-] Removed dead child
10628
2017-08-31 13:10:31.004 10618 INFO glance.common.wsgi [-] Started child 10642
2017-08-31 13:10:31.006 10642 INFO
Public bug reported:
When the nova-compute service cleans up an instance that still exists on
the host although being deleted from the DB, the according network info
is not properly retrieved.
For this reason, vif ports will not be cleaned up.
In this situation there may also be stale volume
We should backport this as it actually leads to deleting things in the
source node...
** Changed in: nova/ocata
Importance: Undecided => High
** Changed in: nova/pike
Importance: Undecided => High
** Changed in: nova
Status: New => Triaged
** Also affects: nova/newton
It looks like the _destroy_evacuated_instances method in the compute
manager has always filtered migrations on the 'accepted' status since
originally this code was just meant to cleanup local resources once an
evacuation from the source host has started, which is fine. The problem
is with removing
Public bug reported:
After deleting a live migration there are allocations on both the source and
the destination hosts.
Reproduction:
- Boot a VM, on host1
- Start live migrating it to host2
- Delete the migration
- The allocations are both on host1 & host2.
This situation doesn't change after
Public bug reported:
This is purely based on code inspection, but the compute API method
'evacuate' does not check if the specified host (if there was one) is
different from instance.host. It checks if the service is up on that
host, which could be down and you can still specify the
Public bug reported:
I have set up OpenStack Pike on Ubuntu 16.04.
Running:
$ su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini --subproject neutron_fwaas
upgrade head" neutron
fails with the following error:
INFO
Public bug reported:
I have set up OpenStack Pike on Ubuntu 16.04 in HA mode (2 controllers,
3 compute node). In the current Pike release, router and network
creation in HA mode fails. Whereas, creating routers in non-HA mode
succeeds.
The neutron-server.log gives me the following:
2017-08-31
Public bug reported:
1.hypervisor is vCenter or kvm
2.the instance status is start in vCenter or kvm
3.the instance status is stop in nova database
this is High-risk operation,beause when instance is started by
vCenter ,it is is running business, but nova task shutdown instance or
delete
Public bug reported:
keystone project can not update or search extra filed
** Affects: keystone
Importance: Undecided
Assignee: 曾永明 (zengyongming)
Status: In Progress
** Changed in: keystone
Assignee: (unassigned) => 曾永明 (zengyongming)
--
You received this bug
Reviewed: https://review.openstack.org/499270
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=10f8a9aa127cfaecab368e26c3b896e203e301bc
Submitter: Jenkins
Branch:master
commit 10f8a9aa127cfaecab368e26c3b896e203e301bc
Author: Chris Dent
Date: Wed
60 matches
Mail list logo