cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-3250) PVLAN - When host is put in maintenance mode , the rules for the router and the user Vms that get migrated out of this host are not getting cleared from this host.
Date Tue, 23 Jul 2013 06:06:58 GMT


Animesh Chaturvedi updated CLOUDSTACK-3250:

This blocker/ critcal was created before July please review and resolve, we are approaching
4.2 code freeze in 7 days 
> PVLAN - When host is put in maintenance mode , the rules for the router and the user
Vms that get migrated out of this host are not getting cleared from this host. 
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3250
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Build from master
>            Reporter: Sangeetha Hariharan
>            Assignee: Sheng Yang
>            Priority: Critical
>             Fix For: 4.2.0
>         Attachments: management-server.log
> 1. Advance zone  cluster with 2 hosts. 
> 2. Create  Shared NW1  scope zone  <pVLAN1, sVLAN1>. 
> 3. Deploy few Vms in this network. 
> 4. In my case:
> host1 - had SSVM,CPVM and 1 user vm
> host2 - had 1 router and 2 user Vms.
> Put host2 in maintenance mode.
> All the vms running in host2 got migrated to host1.
> As part of this migration , we see all the rules relating to the router and user Vms
that got migrated being reprogrammed in host1. 
> But the rules that existed for these Vms in host2 continue to be present in the host.
> Expected Behavior:
> The rules relating to the Vms that migrated out of this host needs to be cleared from
this host.
> root@xenserver-sangee2 ~]# ovs-ofctl dump-flows xenbr0
> NXST_FLOW reply (xid=0x4):
>  cookie=0x0, duration=352.296s, table=0, n_packets=2, n_bytes=96, priority=60,dl_vlan=997,dl_src=06:a5:26:00:00:11
>  cookie=0x0, duration=361.825s, table=0, n_packets=76, n_bytes=9304, priority=60,dl_vlan=997,dl_src=06:3d:cc:00:00:10
>  cookie=0x0, duration=6082.819s, table=0, n_packets=2635, n_bytes=199830, priority=60,dl_vlan=997,dl_src=06:64:5e:00:00:0e
>  cookie=0x0, duration=352.302s, table=0, n_packets=2, n_bytes=96, priority=50,vlan_tci=0x0000,dl_src=06:a5:26:00:00:11
>  cookie=0x0, duration=6082.824s, table=0, n_packets=2717, n_bytes=207263, priority=50,vlan_tci=0x0000,dl_src=06:64:5e:00:00:0e
>  cookie=0x0, duration=361.829s, table=0, n_packets=83, n_bytes=9838, priority=50,vlan_tci=0x0000,dl_src=06:3d:cc:00:00:10
>  cookie=0x0, duration=343.987s, table=0, n_packets=0, n_bytes=0, priority=100,udp,dl_vlan=997,nw_dst=,tp_dst=67
>  cookie=0x0, duration=343.995s, table=0, n_packets=4, n_bytes=168, priority=200,arp,dl_vlan=997,nw_dst=
>  cookie=0x0, duration=8241.736s, table=0, n_packets=19016430, n_bytes=24109319550, priority=0
>  cookie=0x0, duration=343.991s, table=0, n_packets=7, n_bytes=646, priority=150,dl_vlan=997,dl_dst=06:ba:9c:00:00:0f
> [root@xenserver-sangee1 ~]# ovs-ofctl dump-flows xenbr0
> NXST_FLOW reply (xid=0x4):
>  cookie=0x0, duration=734.85s, table=0, n_packets=54, n_bytes=6732, priority=60,dl_vlan=997,dl_src=06:3d:cc:00:00:10
>  cookie=0x0, duration=597.648s, table=0, n_packets=158, n_bytes=19572, priority=60,dl_vlan=997,dl_src=06:a5:26:00:00:11
>  cookie=0x0, duration=597.653s, table=0, n_packets=182, n_bytes=22797, priority=50,vlan_tci=0x0000,dl_src=06:a5:26:00:00:11
>  cookie=0x0, duration=734.854s, table=0, n_packets=64, n_bytes=7884, priority=50,vlan_tci=0x0000,dl_src=06:3d:cc:00:00:10
>  cookie=0x0, duration=1032.129s, table=0, n_packets=6, n_bytes=2052, priority=100,udp,dl_vlan=997,nw_dst=,tp_dst=67
>  cookie=0x0, duration=1032.137s, table=0, n_packets=13, n_bytes=656, priority=200,arp,dl_vlan=997,nw_dst=
>  cookie=0x0, duration=8231.759s, table=0, n_packets=2165619, n_bytes=2671820347, priority=0
>  cookie=0x0, duration=1032.133s, table=0, n_packets=42, n_bytes=3685, priority=150,dl_vlan=997,dl_dst=06:ba:9c:00:00:0f
> root@r-4-VM:~# cat /etc/dhcphosts.txt 
> 06:64:5e:00:00:0e,set:10_223_161_140,,test-123,infinite
> 06:3d:cc:00:00:10,set:10_223_161_142,,test345,infinite
> 06:a5:26:00:00:11,set:10_223_161_143,,yuyu,infinite
> root@r-4-VM:~# 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message