Public bug reported:
We have a lot of filters are pattern match.
There is list for exact match
https://github.com/openstack/nova/blob/df2fd4a252cecc1e1ef471c071e57526ddf65499/nova/db/sqlalchemy/api.py#L2221
Out of that list will be pattern match
Public bug reported:
In "Quota sets (os-quota-sets)" API in the Compute API Reference,
the parameter type of 'quota_set' should be 'object' instead of 'string'.
And there is a missing response description in DELETE method.
http://developer.openstack.org/api-ref/compute/#quota-sets-os-quota-sets
Public bug reported:
http://developer.openstack.org/api-ref/compute/#hosts-os-hosts
There are some parameters that should be fixed.
* Show Host Details
- parameters in 'resource' object should be 'resource.{parameter name}'
instead of 'host.{parameter name}'
- cpu, memory_mb and disk_gb
Public bug reported:
The qos negative test fails [1] on top of Newton release with following
error:
"Request Failed: internal server error while processing your request.
Neutron server returns request_ids:
['req-c8fadf15-dce8-4c2f-943a-3cedc67f']"
Instead of "Bad Request" error.
[1]
Public bug reported:
The excessive calls to 'ip link show' can consume significant amounts of
CPU cycles on every scan_devices iteration on densely packed SR-IOV
systems.
Snip from https://bugs.launchpad.net/mos/+bug/1653131 :
On a node with SR-IOV interfaces neutron-sriov-agent seems to call
Reviewed: https://review.openstack.org/415377
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=1278b1fe44ab43cd5c766dd669e324404034a67a
Submitter: Jenkins
Branch:master
commit 1278b1fe44ab43cd5c766dd669e324404034a67a
Author: Takashi NATSUME
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
Public bug reported:
I see these errors quite a bit in the n-cpu logs for hyperv CI runs:
2017-01-03 23:15:08.141 10848 80822320 MainThread ERROR nova.virt.driver
[req-050d06ec-3636-4a5d-8b73-0531ef62055a - - - - -] Exception
dispatching event Stopped>:
** Also affects: networking-midonet
Importance: Undecided
Status: New
** Changed in: networking-midonet
Assignee: (unassigned) => YAMAMOTO Takashi (yamamoto)
** Changed in: networking-midonet
Milestone: None => 4.0.0
--
You received this bug notification because you are a
Reviewed: https://review.openstack.org/416267
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=663865dfecb483f0ef6aa48749c0712779033dd7
Submitter: Jenkins
Branch:master
commit 663865dfecb483f0ef6aa48749c0712779033dd7
Author: Lance Bragstad
Date:
This bug was fixed in the package python-oslo.privsep -
1.13.0-0ubuntu1.1
---
python-oslo.privsep (1.13.0-0ubuntu1.1) yakkety; urgency=medium
* d/p/deal-with-conf-config-dir.patch: Cherry pick patch from upstream
stable/newton branch to properly handle CONF.config_dir (LP:
** Changed in: nova
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/1633734
Title:
ValueError: Field `instance_uuid' cannot be
Public bug reported:
Whenever any change is made to a DHCP agent port, a refresh of all
security group filters for all ports on that network is triggered. This
is unnecessary as all instance ports automatically get a blanket allow
rule for DHCP port numbers. So changes to DHCP ports in no way
Public bug reported:
OpenStack Version: v14 (Newton)
NIC: Mellanox ConnectX-3 Pro
While testing an SR-IOV implementation, we found that
pci_passthrough_whitelist in nova.conf is involved in the population of
the pci_devices table in the Nova DB. Making changes to the
device/interface in the
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => Jay Pipes (jaypipes)
** Changed in: ironic
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
With commit
https://github.com/openstack/horizon/commit/90f43f3356a889a54464a6ddad81a1ca2b9f6290
the handling of single rules was broken and was always returning True.
This resulted in the admin dashboard showing up incorrectly as well as
panels showing up inappropriately.
Reviewed: https://review.openstack.org/412007
Committed:
https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=b6f79567e23709b87e538ac75f7be20a306f7438
Submitter: Jenkins
Branch:master
commit b6f79567e23709b87e538ac75f7be20a306f7438
Author: Alex Schultz
Public bug reported:
We have defined some custom types in neutron/object/common_types
to better control and validate the input, but use of common_types in
objects/quota.py will lead to cyclic import like this
neutron.api.v2.base -> neutron.quota -> neutron.db.quota.api ->
neutron.objects.quota
Public bug reported:
https://review.openstack.org/414315 introduced an incorrect policy check
to the network-topology panel. My comment there:
"I'm not sure how where this call is actually made and why it would be
applicable to this particular panel, see
Reviewed: https://review.openstack.org/350072
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=7e150b2c0cb50f5fdd89644eb7334acca3c4ee92
Submitter: Jenkins
Branch:master
commit 7e150b2c0cb50f5fdd89644eb7334acca3c4ee92
Author: liaozd
Date: Sun Dec
https://review.openstack.org/#/c/413878/ didn't fix the problem. The
timestamps in the v3 token issue response still doesn't match the spec
as described in the bug description.
** Changed in: keystone
Status: Fix Released => New
** Changed in: keystone
Milestone: ocata-3 => None
--
** Also affects: nova/newton
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova/newton
Importance: Undecided => Medium
** Changed in: nova/newton
Status: New => Confirmed
--
You received this bug notification
Public bug reported:
As discussed in https://review.openstack.org/#/c/409967/, support-
matrix.ini is missing CLI commands for the different operations
described in the file. These should be added in the interest of
completeness.
** Affects: nova
Importance: Undecided
Assignee:
Yes, I'd be tempted to say that the long term fix should be in
devstack's nova setup.
** Changed in: neutron
Assignee: Kevin Benton (kevinbenton) => (unassigned)
** Changed in: neutron
Importance: Low => Undecided
** Changed in: neutron
Status: Confirmed => Invalid
--
You
Yeah, mixed-version controllers isn't supported. We've made some
progress towards being able to support it in master, but it's definitely
not going to work in mitaka/newton.
You have to upgrade your controllers simultaneously (well, most
critically, your conductor services), and then you can have
Public bug reported:
During live-migration if the process goes in a unpredictable situation
for example if QEMU suffers an issue Nova could still consider the
migration has succeeded even if not.
The VM on source node can be still registered even if stopped. In the
worst scenario, the operator
Public bug reported:
Description
===
Nova does not allow to use FQDN in the configuration.
Steps to reproduce
==
Configure following setup with FQDN in /etc/nova/nova.conf
[vnc]
novncproxy_base_url = http://controller01.example.com:6080/vnc_auto.html
[neutron]
url =
Reviewed: https://review.openstack.org/397545
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=fb3b2d9eaf8317cec62e52a99f17946610b8cdca
Submitter: Jenkins
Branch:master
commit fb3b2d9eaf8317cec62e52a99f17946610b8cdca
Author: Kevin_Zheng
Date:
Public bug reported:
With neutron and FWaas master branch and in DVR mode, I create a VM with
floatingIP, it works ok, but when i restart the related l3-agent, i
can't reach the VM via FloatingIP, then check the NAT rules in router
namespace, i found the NAT rules did not be restored.
reproduce
29 matches
Mail list logo