Nova raises exception about existing libvirt filter

Bug #1384235 reported by Vitalii
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Unassigned
neutron
Invalid
Undecided
Unassigned

Bug Description

Sometimes, when I start instance, nova raises exception, that
filter like nova-instance-instance-0000000b-52540039740a already exists.

So I have to execute `virsh nwfilter-undefine` and try to boot instance again:

In libvirt logs I can see the following:

2014-10-22 12:20:13.816+0000: 4693: error : virNWFilterObjAssignDef:3068 : operation failed: filter 'nova-instance-instance-0000000b-52540039740a' already exists with uuid af47118d-1934-4ca7-8a71-c6ae9a6499aa
2014-10-22 12:20:13.930+0000: 4688: error : virNetSocketReadWire:1523 : End of file while reading data: Input/output error

I use libvirt 1.2.8-3 ( Debian )

I have the following services defined:

service_plugins = neutron.services.l3_router.l3_router_plugin.L3RouterPlugin,neutron.services.firewall.fwaas_plugin.FirewallPlugin

I use Icehouse.

Tags: libvirt
Vitalii (vb-d)
description: updated
affects: nova → neutron
Revision history for this message
Numan Siddique (numansiddique) wrote :

Why do you think its a neutron bug?

Vitalii (vb-d)
description: updated
Revision history for this message
Vitalii (vb-d) wrote :

I think this is neutron bug, since Firewall is a neutron plugin. And it is firewall that adds those filters.

Revision history for this message
Cristian Klein (cristiklein) wrote :

It seems that this bug is caused by a more strict behaviour on libvirt's side. libvirt developers recommend fixing OpenStack.

https://www.redhat.com/archives/libvir-list/2014-December/msg00158.html

Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Neutron firewall plugin has nothing to do with filters under discussion

Changed in neutron:
status: New → Incomplete
Joe Gordon (jogo)
tags: added: libvirt
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

Looks like this was already fixed?

https://review.openstack.org/#/c/122721/1

Changed in nova:
status: New → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → kilo-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: kilo-2 → 2015.1.0
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 365 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.