You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sanjeev N (JIRA)" <ji...@apache.org> on 2014/05/19 13:06:38 UTC
[jira] [Updated] (CLOUDSTACK-6707) [SDN] OVS bridge/tunnel ports
are not getting deleted from Host even though there are no vms in the
network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjeev N updated CLOUDSTACK-6707:
----------------------------------
Attachment: ovstunnel-host14.log
ovstunnel-host13.log
management-server.rar
Attached MS log file and ovstunnel logs from both the hosts.
> [SDN] OVS bridge/tunnel ports are not getting deleted from Host even though there are no vms in the network
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6707
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6707
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server, Network Controller
> Affects Versions: 4.4.0
> Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072
> Reporter: Sanjeev N
> Priority: Critical
> Fix For: 4.4.0
>
> Attachments: management-server.rar, ovstunnel-host13.log, ovstunnel-host14.log
>
>
> [SDN] OVS bridge/tunnel ports are not getting deleted from Host even though there are no vms in the network
> Steps to Reproduce:
> ================
> 1.Bring up CS in advanced zone with two hosts in a cluster
> 2.Create physical network with GRE isolation
> 3.Create network with Connectivity service and OVS as the provider
> 4.Deploy couple of vms in the above network.
> 5.Migrate vms to one host and make sure that all the vms (including vr) are running only on one host
> 6.Verify tunnel ports on the host where there are no vms running
> Expected Result:
> ==============
> Tunnel ports and ovs bridge shall be deleted from the host where no vms are running
> Actual result:
> ===========
> OVS bridge and tunnel ports are still present even after migrating all the vms to another host in the cluster
> Observations:
> ============
> Following bridge info is from the host on with all system vms and guest vms are running
> [root@xen-host-13 ~]# ovs-vsctl list-br
> xapi0
> xapi1
> xapi2
> xenbr0
> xenbr1
> On the host where only guest vms are running
> [root@xen-host-14 ~]# ovs-vsctl list-br
> xapi2
> xenbr0
> xenbr1
> Before migration:
> ==============
> [root@xen-host-13 ~]# ovs-vsctl list-ports xapi2
> t997-1-2
> vif12.0
> vif13.0
> [root@xen-host-14 ~]# ovs-vsctl list-ports xapi2
> t997-2-1
> vif7.0
> After migration:
> =============
> [root@xen-host-13 ~]# ovs-vsctl list-ports xapi2
> t997-1-2
> vif12.0
> vif13.0
> vif15.0
> [root@xen-host-13 ~]#
> Following is the target host on which no vms are running:
> [root@xen-host-14 ~]# ovs-vsctl list-br
> xapi2
> xenbr0
> xenbr1
> [root@xen-host-14 ~]# ovs-vsctl list-ports xapi2
> t997-2-1
--
This message was sent by Atlassian JIRA
(v6.2#6252)