please update pip/pbr/setuptools and reopen this bug if needed
** Changed in: nova
Status: Incomplete = Won't Fix
** Changed in: nova
Assignee: (unassigned) = Davanum Srinivas (DIMS) (dims-v)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
This has shown no heartbeat for ages...we'll probably end up getting rid
of the entire plugin from Mitaka.
** Changed in: neutron
Milestone: liberty-3 = None
** Changed in: neutron
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
The FWaaS REST interface is not checking string lengths, so a name
greater than 255 characters or a description greater than 1024 will
cause creations to fail with a 500 INTERNAL SERVER error due to a Data
too long for column DB error internally.
$ neutron firewall-create
Public bug reported:
When I want to filter list of artifacts by tag I get a 500 error:
http://localhost:9292/v3/artifacts/myartifact/v2.0/drafts?tag=hyhyhy
html
head
title500 Internal Server Error/title
/head
body
h1500 Internal Server Error/h1
The server has either erred or is
A fix was released in Havana as per this patch -
https://review.openstack.org/#/c/117037/3
A fix was merged into master as per this patch -
https://review.openstack.org/#/c/70668/
Neutron currently uses testtools=1.4.0 (as per test-requirements.txt)
** Changed in: neutron
Status:
** Changed in: oslo.db
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1467008
Title:
Unit tests fail with sqlalchemy 1.0+
Status in Glance:
Fix
Cinder was fixed back in Juno: https://review.openstack.org/#/c/96512/
** Changed in: cinder
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
When there are changes in the local config (/etc/keystone/keystone.conf) some
tests fail.
For example,
keystone.tests.unit.test_backend_ldap.MultiLDAPandSQLIdentityDomainConfigsInSQL.test_update_user_enable_fails,
fails.
The tests should not be affected by the local
** Changed in: nova
Status: In Progress = Confirmed
** Changed in: nova
Assignee: (unassigned) = Davanum Srinivas (DIMS) (dims-v)
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
** 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/1461750
Title:
two unit test cases not pass for kilo version
Public bug reported:
Our LDAP lookup users in group logic assumes that the member attribute
contains the user DN.
https://github.com/openstack/keystone/blob/master/keystone/identity/backends/ldap.py#L168
However, this is not the case for posixGroup (RFC 2307) where the
memberUid is really the
Public bug reported:
Distributed DHCP implementation in the reference implementation is based
on an abandoned spec and approved bug, the description of the feature
and its limitations needs to be organised and well documented
implementation: https://review.openstack.org/#/c/184423/
** Affects:
Public bug reported:
Create IPSec site connection with IPSec policy that specifies AH-ESP
protocol leads to the following error:
2015-08-26 13:29:10.976 ERROR neutron.agent.linux.utils
[req-7b4a7ccc-286e-4267-9d50-d84afa5b5663 demo
99b8d178a6784d749920414ac08bce66]
Command: ['ip', 'netns',
Public bug reported:
In kilo or icehouse release: multiple deletes in firewall tempest case:
test_create_show_delete_firewall cause l3-agent throws unexpected
exception: FirewallNotFound.
I am running tempest against kilo release, after running the neutron
case: test_create_show_delete_firewall,
Public bug reported:
keystone token validation operations are much slower than uuid
operations. The performance is up to 4x slower which makes other
openstack API calls slower too.
Numbers from Dolph:
Token validation performance
Response time Requests per second
UUID18.8 ms (baseline)
Public bug reported:
In my environment where there is a compute node and a controller node.
On the compute node the L3-agent mode is 'dvr'.
On the controller node the L3-agent mode is 'dvr-snat'.
Nova-compute is only running on the compute node.
Start: the compute node has no VMs running, there
Public bug reported:
Logstash query:
message:oslo_db.exception.CantStartEngineError: No sql_connection
parameter is established AND build_name:gate-neutron-python34
Seems to have started 8/26
Logstash results:
** Changed in: nova
Status: Invalid = In Progress
** Changed in: nova
Assignee: (unassigned) = Feodor Tersin (ftersin)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
*** This bug is a duplicate of bug 1484194 ***
https://bugs.launchpad.net/bugs/1484194
There was no nova fix committed here, marked nova as invalid since it
was fixed in cinder.
** Changed in: nova
Status: Fix Committed = Invalid
** This bug has been marked a duplicate of bug 1484194
Public bug reported:
The same as ovs or lb agents do, sr-iov should have ml2 and agent
configuration options split into pieces.
** Affects: neutron
Importance: Undecided
Assignee: Ihar Hrachyshka (ihar-hrachyshka)
Status: In Progress
--
You received this bug notification
Public bug reported:
Some of the path name calls from the neutronclient use underscores
(bandwidth_limit_rules), and some use a hypen/dash (rbac-policies, for
example). They need to be made consistent
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug
The LDAP assignment is deprecated as of Kilo so I don't see any reason
to allow implementers to use it more.
** Changed in: keystone
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
I'm assuming this was fixed by the last patch. In the future, please use
Closes-Bug on the final patch in your patch sequence -- not just
Partial-Bug on all of them (which leaves the bug open).
** Changed in: keystone
Status: In Progress = Fix Committed
** Changed in: keystone
fixed by - https://review.openstack.org/#/c/104066/
** Changed in: keystone
Milestone: None = 2015.1.0
** Changed in: keystone
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
*** This bug is a duplicate of bug 1484194 ***
https://bugs.launchpad.net/bugs/1484194
** This bug is no longer a duplicate of bug 1476806
Unable to delete instance with attached volumes which failed to boot
** This bug has been marked a duplicate of bug 1484194
Cinder shouldn't fail a
** Also affects: oslo.vmware
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/1479066
Title:
DeprecationWarning:
** Changed in: heat
Status: In Progress = 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/1236116
Title:
attaching all devstack quantum networks to a nova
mriedem@ubuntu:~/git/nova$ pip show pbr pip setuptools virtualenv
/usr/local/lib/python2.7/dist-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90:
InsecurePlatformWarning: A true SSLContext object is not available. This
prevents urllib3 from configuring SSL appropriately and may
Works for me:
mriedem@ubuntu:~/git/nova$ tox -r -e genconfig
genconfig create: /home/mriedem/git/nova/.tox/genconfig
genconfig installdeps: -r/home/mriedem/git/nova/requirements.txt,
-r/home/mriedem/git/nova/test-requirements.txt
genconfig develop-inst: /home/mriedem/git/nova
genconfig
Public bug reported:
In my environment where there is a compute node and a controller node.
On the compute node the L3-agent mode is 'dvr' on the controller node
the L3-agent mode is 'dvr-snat'. Nova-compute is only running on the
compute node.
Start: the compute node has no VMs running, there
Public bug reported:
In my environment where there is a compute node and a controller node.
On the compute node the L3-agent mode is 'dvr' on the controller node
the L3-agent mode is 'dvr-snat'. Nova-compute is only running on the
compute node.
Start: the compute node has no VMs running, there
Public bug reported:
http://logs.openstack.org/80/148980/28/check/gate-nova-
python27/f7cb9dd/console.html#_2015-08-25_22_14_53_647
{3}
nova.tests.unit.virt.ironic.test_driver.IronicDriverTestCase.test__unprovision_fail_max_retries
[] ... inprogress
This seems to be new(ish). Someone I work
No longer valid.
** Changed in: neutron
Status: In Progress = Won't Fix
** Changed in: neutron
Milestone: liberty-3 = None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Barbican client requires endpoint for barbican service, but currently it isn't
set.
So cert manager couldn't connect to correct endpoint.
Below is error message.
Traceback (most recent call last):
File .tox/test-cert.py, line 19, in module
certificate_secret.store()
Public bug reported:
When SR-IOV introduce in Juno Agent supported only link state change
Some Intel cards don't support setting link state, so to
resolve it the SR-IOV mech driver supports agent and agent less mode.
From Liberty the SR-IOV agent brings more functionality like
qos and port
Public bug reported:
neutron.tests.unit.services.qos.test_qos_plugin.TestQosPlugin.test_delete_policy_rule
-
Captured pythonlogging:
~~~
2015-08-26 17:13:10,783 WARNING [oslo_config.cfg]
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Assignee: (unassigned) = Rajesh Tailor (rajesh-tailor)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
we can choose a device use cmd:
nova volume-attach server volume [device]
to attach a volume to a server. But we can not choose device in
dashboard.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Public bug reported:
while running tests on kilo:
Port
cleanup failed for these port-ids (063cf7f3-ded1-4297-bc4c-31eae876cc91).
Traceback (most recent call last):
File
Public bug reported:
We currently assume that a single colon in the unknown-245 dhclient key
indicates we are dealing with hex; this is not necessarily true. If any
part of the IP address is '58', then a colon will be included in the
packed values.
We should have more robust determination of if
Public bug reported:
For example, a line of
option unknown-245 dH\l;
in dhclient.eth0.leases should yield an IP address of 100.72.34.108 but
instead causes an exception:
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py,
line 249,
Thanks Long Quan Sha,
I added python-glanceclient into the bug and assigned that to you as
that's where your patch is directed to, not glance.
I see two problems here, first you're correct and our client should be
able to handle that situation, but foremost our server should not allow
Public bug reported:
Non default configuration sections [glance], [neutron] ignored for
nova.conf then installed from UCA packages:
How to reproduce:
1) Install and configure OpenStack Juno Nova with Neutron at compute node using
UCA (http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Public bug reported:
In
https://github.com/openstack/keystone/blob/master/doc/source/mapping_schema.rst;,
link attached to Json schema is wrong and also heading violation.
Explanation: for heading 2 the underline should be '~'
** Affects: keystone
Importance: Undecided
Assignee:
Public bug reported:
This issue occurs on a fresh OpenStack Kilo installation (Ubuntu 14.04
LTS) with a single non-HA network node:
In general public access via floating IPs works, I can ping, ssh and so
on my instances.
But if I associate a new floating IP to a new instance, all floating IPs
Public bug reported:
Issue: the option --tenant-id is not mentioned in the usage for
`neutron security-group-list`. This can lead to confusion on how to
provide a tenant per List security groups that belong to a given
tenant.
# neutron help security-group-list
usage: neutron security-group-list
You have been subscribed to a public bug:
Issue: the option --tenant-id is not mentioned in the usage for
`neutron security-group-list`. This can lead to confusion on how to
provide a tenant per List security groups that belong to a given
tenant.
# neutron help security-group-list
usage:
Public bug reported:
In https://github.com/openstack/glance/blob/master/doc/source/metadefs-
concepts.rst the link given for one example is
https://github.com/openstack/nova-specs/blob/master/specs/juno/virt-
driver-vcpu-topology.rst. After clicking this error: page not found
Solution: The
Public bug reported:
Noticed below message in logs in Data Processing panels:
WARNING:py.warnings:RemovedInDjango18Warning: In Django 1.8, widget
attribute placeholder=True will be rendered as 'placeholder'. To
preserve current behavior, use the string 'True' instead of the boolean
value.
**
Public bug reported:
If a port is deleted right before calling _bind_devices ,
get_ports_attributes will throw an exception because the row is not
found
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
If a port is deleted right before calling _bind_devices ,
get_ports_attributes will throw an exception because the row is not
found
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
** Changed in: cirros
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).
https://bugs.launchpad.net/bugs/1312199
Title:
cirros 0.3.1 fails to boot
Status in CirrOS:
We haven't seen this in a long time so marking it as fixed (since Kilo).
** 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).
** Also affects: cinder/kilo
Importance: Undecided
Status: New
** Tags removed: volumes
** Tags added: fibre-channel ibm
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
If a port is deleted right before calling _bind_devices ,
get_ports_attributes will throw an exception because the row is not
found
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
The orignal description in manual is as follows:
Lists the IP addresses assigned to an instance or show details for a specified
IP address.
It should be shows details insteadof show details.
The referrence link is:
http://developer.openstack.org/api-ref-compute-v2.1.html
Public bug reported:
When live migrating an instance with volume attached the volume gets
attached to the destination during the process. If after that there is a
failure, the volume is left attachd to the destination, and then gets
attached to the source.
Source cleanup is explicit, however, we
not related to nova
** Project changed: nova = horizon
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1488840
Title:
nova volume attach in dashboard can not be
I think it might be invalid, because RDO needs Alembic upgade.
I'll close it, and re-open in case of I still have the issue.
** Changed in: neutron
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
not sure why this wasn't marked fix-released by 0.7.7~bzr1138-0ubuntu1 ,
but it should be fixed now.
** Changed in: cloud-init
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
Public bug reported:
My ml2 configuration file contains the following:
[ml2]
extension_drivers = port_security,qos
mechanism_drivers = openvswitch,l2population
However, when trying to get a list of available rule types, the neutron-server
logs this to the log file:
WARNING
Public bug reported:
a) nova compute service updates info of compute-node by run
update_available_resource every CONF.update_resources_interval(60s by default).
b) for every scheduler request:
1. select_destinations is called and get all HostStates(if compute-node is
newer that local hoststate
Public bug reported:
When creating an instance backed by a cinder volume, the disk device /dev/vda
is used regardless of image settings. I am using the following image metadata
to set virtio-scsi driver on my instances:
hw_disk_bus=scsi
hw_scsi_model=virtio-scsi
When I boot instances using a
Public bug reported:
The neutron v2 base.py auto populates a 'tenant_id' attribute on calls
if the attribute is not passed, pulling from the context.
This causes a POST to create a flavor service binding to fail when verifying
attributes, as currently the tenant_id is not
part of the expected
Public bug reported:
Summary: 40 VMs are created and then deleted on the same host. At the end of
this, I find that iptables rules for some ports are not cleaned up, and remain
as garbage. This garbage keeps piling up, as more VMs are created and deleted.
Topology:
Actually the root cause for the failure I did observe was different.
This appears to be a genuine nova error where a server is deleted by
another test while the list operation is in progress. It is also
interesting that nova fails with a 404 here - this appears to really be
a bug.
In support of
Public bug reported:
Reproduce:
1.Click System - Metadata Definitions
2.Set 'Public' or 'Protected' to False in any section.
3.Set them to True. But it can't work and still be False.
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: neutron
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/1487323
Title:
Grammar misses in manual “Networking API v2.0 (CURRENT)”
Status in
Public bug reported:
When authenticated via admin token, trusts details are not available.
Trusts can be listed:
---
# openstack trust list -f csv
ID,Expires At,Impersonation,Project ID,Trustee User ID,Trustor User
ID
** Also affects: tempest
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1427015
Title:
too many subnet-create cause q-dhcp failure
Status in
Public bug reported:
VPNaaS unit tests for DVR are failing with below error
AttributeError: 'DvrEdgeRouter' object has no attribute
'create_snat_namespace'
Captured traceback:
~~~
Traceback (most recent call last):
File
Public bug reported:
nova and horizon dashboard should support that specify the block devices(e.g.
/dev/sd*) to attach to an instance. Users can type the block devices(e.g.
/dev/sd*) to attach to the instance and the instance can map the block
devices(e.g. /dev/sd*) with a symlink(e.g.
Public bug reported:
Dashboard (Horizon) also should support that the same with nova bug:
https://bugs.launchpad.net/nova/+bug/1489226
nova and horizon dashboard should support that specify the block devices(e.g.
/dev/sd*) to attach to an instance. Users can type the block devices(e.g.
Public bug reported:
The required fields in the workflow if not filled should prompt the user for
input.
The error message is no doubt displayed , but the box that accepts the
contents, shifts to the right. (Ideally it should be in the same place with the
message This field is required printed
** Project changed: horizon = openstack-api-site
** Tags added: api low-hanging-fruit
** Changed in: openstack-api-site
Status: New = Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
Public bug reported:
The original description is:
Clears the encrypted copy of the password from the metadata server after the
client gets the password and determines that it no longer needs it in the
metadata server.
that it no longer needs it above should be that it is no longer
needed
The
76 matches
Mail list logo
