Public bug reported:
Associating Floating IP with neutron takes too long to show up in VM's
details ('nova show' or 'compute_client.servers.get()') and even longer
when there's more than 1 VM involved.
when launching 2 VMs with floating IP you can see in the log that it passes
once:
"unchecked f
Public bug reported:
The bigswitch plugin fails to use the admin context to update the floating IPs
on the backend controller.
When one tenant assigns a floating IP, the update to the controller doesn't
contain the floating IPs of the other tenants so the controller thinks they
have been remov
Public bug reported:
Most of the Nova Public API Controllers inherit from wsgi.Controller,
but still some Nova Public APIs controllers directly inherit from
object. So it's necessary to unify all the Nova Public API Controllers
inherit from wsgi.Controller.
** Affects: nova
Importance: Undec
Public bug reported:
Seems like when py2rpm builds networkx -> rpm (for that taskflow
project) the rpm has doc examples that are getting left out of
packaging, likely we need to remove those or include those to avoid
these errors.
** Affects: anvil
Importance: Critical
Assignee: Joshua
Public bug reported:
Midonet does not currently support the "enable_snat" option in its
plugin. This bug is fix the plugin to support that option.
** Affects: neutron
Importance: Undecided
Assignee: Joe Mills (joe-6)
Status: New
** Tags: havana-backport-potential midonet
**
Public bug reported:
this bug is similar to https://bugs.launchpad.net/nova/+bug/1158897
but this bug is cause by _reserve_quota_delta() method, which will need to
access DB if quota delta is not empty,
the trace log is:
2013-12-19 01:39:40.879 ERROR nova.compute [-] No db access allowed in
nova
Public bug reported:
Nova should update VNC listen address in libvirt.xml to the destination
node's vncserver_listen setting on completing migration. Without that,
the only way to make VMs accessible over VNC after migration is to set
vncserver_listen to 0.0.0.0 as recommended in:
http://docs.ope
I took a look at the Ironic PXE driver's handling of this sort of
situation, and while I think it's OK and not affected by the precise
circumstances described in this bug, I think there may be some similar
difficulty in determining why a deploy failed part-way through.
I've tagged the bug as also-
Public bug reported:
Due to a recent policy change in HACKING
(http://docs.openstack.org/developer/hacking/#openstack-licensing),
empty files should no longer contain copyright notices.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: low-hanging-fruit
** Tags added
Ignore the bug. The problem was with image used.
** 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/1261430
Title:
Port opening in secur
Public bug reported:
Navigate to Instances: Launch Instance. The Launch Instance dialog will
appear. Choose Instance Boot Source -> Boot from Image. Assuming you
have some images to choose from, click the Image Name drop-down and
you'll notice that the list is in reverse order that the images were
OSSA 2013-037
** Changed in: ossa
Status: Fix Committed => Fix Released
** Summary changed:
- DoS attack via setting os_type in snapshots (CVE-2013-6437)
+ [OSSA 2013-037] DoS attack via setting os_type in snapshots (CVE-2013-6437)
--
You received this bug notification because you are a
Public bug reported:
I tried a use case where I
1. Have list of users (in the LDAP) in the default domain
2. Create domain
3. Add member role to user for the new domain
4. Remove role
5. Try do delete domain
And there I got the problem
{"domain": {"enabled": false, "id": "5bc213efd70e4ec197c8a
Public bug reported:
If the heat template from a file source does not have the right syntax, the
error displayed in horizon is
"An unknown problem occurred validating the template."
Heat engine is returning an error with an error message but that message is not
propagated to the end user.
This
Public bug reported:
We need a suite of unit tests that iterate through each available rule
in policy.json, converts them all into admin-only actions, and asserts
if a valid policy exception is raised when those actions are performed
by a non-admin.
Currently there are tests that validate if poli
Ming Lei, that is an issue with the ubuntu packaging of nova not of nova
itself. it looks like you are having a dependency issue with WebOb.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is sub
** 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/1262176
Title:
EC2: 'io1' type volume should also retu
Public bug reported:
This started showing up recently in the nova unit tests:
Exception nova.virt.vmwareapi.error_util.VimFaultException: VimFaultException()
in > ignored
Exception nova.virt.vmwareapi.error_util.VimFaultException: VimFaultException()
in > ignored
Exception nova.virt.vmwareapi.e
Public bug reported:
When the quota limit is reached, the image location is not cleaned
up[0]. Notice that at this point *just* the locaiton should be deleted
since the image data upload didn't succeed and the store should have
already cleaned up the partially uploaded data.
https://github.com/op
Public bug reported:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L142
if api.nova.extension_supported("BlockDeviceMappingV2Boot",
request):
source_type_c
Public bug reported:
Any errors after the XenServer migrate command completes currently can
cause the users VM to be deleted.
While there should be some cleanup performed, deleting the VM does not
make sense for the XenAPI driver.
** Affects: nova
Importance: Medium
Assignee: John Garb
Public bug reported:
This patch https://review.openstack.org/#/c/61041 exposes volume type in
the EC2 API. Amazon's API documentation says that if the volume type is
'io1', that is, if the volume has guaranteed IOPS set for it, a
'DescribeVolumes' call should return the IOPS for such volumes. We n
I think we need do this to fix this defect, i verified it in my dev
local.
http://paste.openstack.org/show/55299/
** Changed in: glance
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
h
Public bug reported:
This has been found while running automated testing:
71441:2013-12-17 08:33:57.127 DEBUG neutron.db.db_base_plugin_v2
[req-ba712d02-26ac-4e31-8613-de1a4558b028 None None] Recycle 169.254.169.254
from (pid=29594) _recycle_ip
/opt/stack/neutron/neutron/db/db_base_plugin_v2.p
Public bug reported:
in neutron/l3_db.py _update_fip_assoc is executed from within a database
transaction.
The same routine for the nvp plugin executes backend operations such as
updating the nat rules and ip addresses on the nvp platform, thus
potentially triggering the deadlock with another mys
Public bug reported:
Tempest console
=
2013-12-18 10:32:34.092 |
==
2013-12-18 10:32:34.094 | FAIL:
tempest.api.compute.servers.test_server_metadata.ServerMetadataTestJSON.test_update_server_metadata[gate]
2013-12-1
Public bug reported:
When using the latest config generator from oslo-incubator, see
https://review.openstack.org/62815, and trying to generate the
nova.conf.sample by using the following commands:
NOVA_CONFIG_GENERATOR_EXTRA_MODULES=keystoneclient.middleware.auth_token
tools/config/generate_samp
Public bug reported:
http://logs.openstack.org/03/60203/2/check/check-tempest-dsvm-neutron-
pg/f4433f2/
FAIL:
tempest.api.network.admin.test_agent_management.AgentManagementTestXML.test_list_agent[gate,smoke]
2013-12-18 06:25:32.632 |
tempest.api.network.admin.test_agent_management.AgentManagem
Public bug reported:
The update of the floatingip_db was happening before the disassociation, so the
disassociation happened on new data. The old data was required to identify the
router_id. This fix changes the order of the disassociation and the
floatingip_db
update. This fix has the side aff
I tested it with my local env and can't reproduce it. And after reviewed
the code, I don't think the 'killed' image size will be counted. See
https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/api.py#L716
In other words, the size will multiply the number of locations. However,
th
Public bug reported:
After adding state reporting to metadata agent following tracebacks
appeared in py26 unit test console logs:
2013-11-22 15:08:33.914 | ERROR:neutron.agent.metadata.agent:Failed reporting
state!
2013-11-22 15:08:33.914 | Traceback (most recent call last):
2013-11-22 15:08:33.
31 matches
Mail list logo
