cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjeev N (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-6779) [OVS] Expunging VM (deleting vif) deletes all the rules from ovs bridge flow table
Date Tue, 27 May 2014 11:52:04 GMT


Sanjeev N updated CLOUDSTACK-6779:

    Attachment: ovstunnel.log_host14

Attached log files from MS, ovstunnel files from both the hosts inside the cluster.

> [OVS] Expunging VM (deleting vif) deletes all the rules from ovs bridge flow table
> ----------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-6779
>                 URL:
>             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 with commit d130530bd3e1cd6d8249d5045e00e4e4e2201521
>            Reporter: Sanjeev N
>            Assignee: Murali Reddy
>            Priority: Blocker
>              Labels: ovs
>             Fix For: 4.4.0
>         Attachments: management-server.rar, ovstunnel.log_host13, ovstunnel.log_host14
> [OVS] Expunging VM (deleting vif) deletes all the rules from ovs bridge flow table
> Steps to reproduce:
> ================
> 1.Bring up CS in advanced zone with min of 2 xen hosts in a cluster
> 2.Add physical network with GRE isolation
> 3.Create network offering with connectivity service and OVS as the provider
> 4.Create an isolated network with above offering and deploy few vms (4-5) in that network
and make sure that vms are spanned across both the hosts
> 5.After this verify flow table rules on the ovs bridge
> 6.Expunge one of the vms created at step4
> 7.Again verify flow table rules on the host from where vm was deleted
> Result:
> =====
> All the flow table rules were deleted from the OVS bridge. Only default flow rule is
> Attaching management server log file and ovstunnel log files from both the hosts. 
> Please look for xapi5 and xapi7 in ovstunnel log files.
> Flow table rules before destroy the vm:
> [root@Rack1Pod1Host13 ~]# ovs-ofctl dump-flows xapi5
> NXST_FLOW reply (xid=0x4):
>  cookie=0x0, duration=374.111s, table=0, n_packets=4, n_bytes=768, priority=1100,dl_dst=ff:ff:ff:ff:ff:ff
>  cookie=0x0, duration=300.162s, table=0, n_packets=0, n_bytes=0, priority=1000,ip,in_port=6,nw_dst=
>  cookie=0x0, duration=374.122s, table=0, n_packets=0, n_bytes=0, priority=1200,ip,in_port=5,nw_dst=
>  cookie=0x0, duration=5350.811s, table=0, n_packets=0, n_bytes=0, priority=1200,ip,in_port=4,nw_dst=
>  cookie=0x0, duration=6016.913s, table=0, n_packets=0, n_bytes=0, priority=1200,ip,in_port=3,nw_dst=
>  cookie=0x0, duration=6753.464s, table=0, n_packets=0, n_bytes=0, priority=1200,ip,in_port=2,nw_dst=
>  cookie=0x0, duration=6890.423s, table=0, n_packets=7594, n_bytes=6858309, priority=0
>  cookie=0x0, duration=374.1s, table=0, n_packets=0, n_bytes=0, priority=1100,ip,nw_dst=
>  cookie=0x0, duration=374.132s, table=0, n_packets=5, n_bytes=810, priority=1200,in_port=5,dl_dst=ff:ff:ff:ff:ff:ff
>  cookie=0x0, duration=5350.823s, table=0, n_packets=8, n_bytes=1236, priority=1200,in_port=4,dl_dst=ff:ff:ff:ff:ff:ff
>  cookie=0x0, duration=300.173s, table=0, n_packets=0, n_bytes=0, priority=1000,in_port=6,dl_dst=ff:ff:ff:ff:ff:ff
>  cookie=0x0, duration=6016.924s, table=0, n_packets=8, n_bytes=1236, priority=1200,in_port=3,dl_dst=ff:ff:ff:ff:ff:ff
>  cookie=0x0, duration=6753.474s, table=0, n_packets=6, n_bytes=852, priority=1200,in_port=2,dl_dst=ff:ff:ff:ff:ff:ff
> After destroying the vm:
> [root@Rack1Pod1Host13 ~]# ovs-ofctl dump-flows xapi5
> NXST_FLOW reply (xid=0x4):
>  cookie=0x0, duration=877.901s, table=0, n_packets=46, n_bytes=9748, priority=0 actions=NORMAL
> [root@Rack1Pod1Host13 ~]#

This message was sent by Atlassian JIRA

View raw message