Skip to content

[virtual switch test bed]: data plane always transitions from up to down upon syncd WARM shutdown #817

Closed
Closed
[virtual switch test bed]: data plane always transitions from up to down upon syncd WARM shutdown#817
@jipanyang

Description

@jipanyang
jipanyang
opened on Feb 28, 2019

2019-02-28 20:48:14 : Data plane state transition from up to down (0)

root@0deded8dd163:/tmp# tail -F warm-reboot.log 
tail: unrecognized file system type 0x794c7630 for 'warm-reboot.log'. please report this to [email protected]. reverting to polling
2019-02-28 20:45:55 : Test params:
2019-02-28 20:45:55 : DUT ssh: [email protected]
2019-02-28 20:45:55 : DUT reboot limit in seconds: 0:00:00
2019-02-28 20:45:55 : DUT mac address: 52:54:00:f2:93:80
2019-02-28 20:45:55 : From server src addr: 192.168.1.243
2019-02-28 20:45:55 : From server src port: 20
2019-02-28 20:45:55 : From server dst addr: 192.168.229.219
2019-02-28 20:45:55 : From server dst ports: [28, 30, 29, 31]
2019-02-28 20:45:55 : From upper layer number of packets: 500
2019-02-28 20:45:55 : VMs: ['10.250.0.5','10.250.0.4','10.250.0.3','10.250.0.2']
2019-02-28 20:45:55 : Reboot type is warm-reboot
2019-02-28 20:47:19 : 36000 packets are ready after: 0:01:23.397898
2019-02-28 20:47:19 : Enabling arp_responder
2019-02-28 20:47:20 : Converted addresses VMs: ['10.250.0.5', '10.250.0.4', '10.250.0.3', '10.250.0.2']
2019-02-28 20:47:20 : Starting reachability state watch thread...
2019-02-28 20:47:21 : Send   100 Received   100 servers->t1
2019-02-28 20:47:25 : Check that device is alive and pinging
2019-02-28 20:47:28 : Send   500 Received   495 t1->servers
2019-02-28 20:47:28 : Data plane state transition from init to partial (495)
2019-02-28 20:47:28 : Send    10 Received    10 ping DUT
2019-02-28 20:47:28 : Control plane state transition from init to up
2019-02-28 20:47:29 : Send   100 Received   100 servers->t1
2019-02-28 20:47:30 : Send   500 Received   500 t1->servers
2019-02-28 20:47:30 : Data plane state transition from partial to up (500)
2019-02-28 20:47:31 : Send    10 Received    10 ping DUT
2019-02-28 20:47:31 : Send   100 Received   100 servers->t1
2019-02-28 20:47:32 : Send   500 Received   500 t1->servers
2019-02-28 20:47:33 : Send    10 Received    10 ping DUT
2019-02-28 20:47:34 : Send   100 Received   100 servers->t1
2019-02-28 20:47:35 : Send   500 Received   500 t1->servers
2019-02-28 20:47:35 : Send    10 Received    10 ping DUT
2019-02-28 20:47:36 : Send   100 Received   100 servers->t1
2019-02-28 20:47:37 : Send   500 Received   500 t1->servers
2019-02-28 20:47:38 : Send    10 Received    10 ping DUT
2019-02-28 20:47:38 : Send   100 Received   100 servers->t1
2019-02-28 20:47:39 : Send   500 Received   500 t1->servers
2019-02-28 20:47:40 : Send    10 Received    10 ping DUT
2019-02-28 20:47:41 : Send   100 Received   100 servers->t1
2019-02-28 20:47:42 : Send   500 Received   500 t1->servers
2019-02-28 20:47:42 : Send    10 Received    10 ping DUT
2019-02-28 20:47:43 : Send   100 Received   100 servers->t1
2019-02-28 20:47:44 : Send   500 Received   500 t1->servers
2019-02-28 20:47:44 : Send    10 Received    10 ping DUT
2019-02-28 20:47:45 : Schedule to reboot the remote switch in 10 sec
2019-02-28 20:47:45 : Wait until Control plane is down
2019-02-28 20:47:45 : Send   100 Received   100 servers->t1
2019-02-28 20:47:46 : Send   500 Received   500 t1->servers
2019-02-28 20:47:47 : Send    10 Received    10 ping DUT
2019-02-28 20:47:48 : Send   100 Received   100 servers->t1
2019-02-28 20:47:49 : Send   500 Received   500 t1->servers
2019-02-28 20:47:50 : Send    10 Received    10 ping DUT
2019-02-28 20:47:50 : Send   100 Received   100 servers->t1
2019-02-28 20:47:52 : Send   500 Received   500 t1->servers
2019-02-28 20:47:52 : Send    10 Received    10 ping DUT
2019-02-28 20:47:53 : Send   100 Received   100 servers->t1
2019-02-28 20:47:54 : Send   500 Received   500 t1->servers
2019-02-28 20:47:55 : Rebooting remote side
2019-02-28 20:47:55 : Send    10 Received    10 ping DUT
2019-02-28 20:47:56 : Send   100 Received   100 servers->t1
2019-02-28 20:47:57 : Send   500 Received   500 t1->servers
2019-02-28 20:47:58 : Send    10 Received    10 ping DUT
2019-02-28 20:47:59 : Send   100 Received   100 servers->t1
2019-02-28 20:48:01 : Send   500 Received   500 t1->servers
2019-02-28 20:48:01 : Send    10 Received    10 ping DUT
2019-02-28 20:48:02 : Send   100 Received   100 servers->t1
2019-02-28 20:48:04 : Send   500 Received   500 t1->servers
2019-02-28 20:48:04 : Send    10 Received    10 ping DUT
2019-02-28 20:48:05 : Send   100 Received   100 servers->t1
2019-02-28 20:48:06 : Send   500 Received   500 t1->servers
2019-02-28 20:48:07 : Send    10 Received    10 ping DUT
2019-02-28 20:48:08 : Send   100 Received   100 servers->t1
2019-02-28 20:48:09 : Send   500 Received   500 t1->servers
2019-02-28 20:48:10 : Send    10 Received    10 ping DUT
2019-02-28 20:48:10 : Send   100 Received   100 servers->t1
2019-02-28 20:48:12 : Send   500 Received   500 t1->servers
2019-02-28 20:48:13 : Send    10 Received    10 ping DUT
2019-02-28 20:48:13 : Send   100 Received     0 servers->t1
2019-02-28 20:48:14 : Send   500 Received     0 t1->servers
2019-02-28 20:48:14 : Data plane state transition from up to down (0)
2019-02-28 20:48:15 : Send    10 Received     0 ping DUT
2019-02-28 20:48:15 : Control plane state transition from up to down

2019-02-28 20:48:15 : Dut reboots: reboot start 2019-02-28 20:48:15.522182
2019-02-28 20:48:15 : Stopping reachability state watch thread.
2019-02-28 20:48:15 : Send   100 Received     0 servers->t1
2019-02-28 20:48:16 : Send   500 Received     0 t1->servers

syslog:

Feb 28 20:48:10.519359 vlab-01 NOTICE admin: Stopping syncd ...
Feb 28 20:48:10.529625 vlab-01 INFO systemd[1]: Stopping syncd service...
Feb 28 20:48:11.822128 vlab-01 NOTICE syncd#syncd_request_shutdown: :- main:83: requested WARM shutdown
Feb 28 20:48:11.825343 vlab-01 NOTICE syncd#syncd: :- syncd_main:3871: is asic queue empty: 1
Feb 28 20:48:11.825343 vlab-01 NOTICE syncd#syncd: :- syncd_main:3878: drained queue
Feb 28 20:48:11.825343 vlab-01 NOTICE syncd#syncd: :- handleRestartQuery:3461: received WARM switch shutdown event
Feb 28 20:48:11.825365 vlab-01 NOTICE syncd#syncd: :- profile_get_value:1084: SAI_WARM_BOOT_WRITE_FILE: /var/cache/sai_warmboot.bin
Feb 28 20:48:11.825365 vlab-01 NOTICE syncd#syncd: :- syncd_main:3969: using warmBootWriteFile: '/var/cache/sai_warmboot.bin'
Feb 28 20:48:11.825377 vlab-01 NOTICE syncd#syncd: :- syncd_main:3980: Warm Reboot requested, keeping data plane running



Feb 28 20:48:11.825377 vlab-01 NOTICE syncd#syncd: :- syncd_main:3999: Removing the switch gSwitchId=0x2100000000
Feb 28 20:48:11.825760 vlab-01 INFO syncd.sh[10032]: requested WARM shutdown
Feb 28 20:48:11.829940 vlab-01 NOTICE syncd#syncd: :- vs_remove_netlink_message_listener:284: removed netlink thread listener
Feb 28 20:48:11.829940 vlab-01 WARNING syncd#syncd: :- meta_generic_validation_remove:1779: removing switch object 0x2100000000 reference count is 13033, removing all objects from meta DB
Feb 28 20:48:11.859099 vlab-01 NOTICE syncd#syncd: :- vs_generic_remove:140: SAI_SWITCH_ATTR_RESTART_WARM = true
Feb 28 20:48:12.042058 vlab-01 NOTICE syncd#syncd: :- vs_dump_switch_database_for_warm_restart:110: dumped 502 fdb infos
Feb 28 20:48:12.042712 vlab-01 NOTICE syncd#syncd: :- vs_dump_switch_database_for_warm_restart:115: dumped 15056 objects to /var/cache/sai_warmboot.bin
Feb 28 20:48:12.051940 vlab-01 NOTICE syncd#syncd: :- vs_generic_remove:161: removed switch: oid:0x2100000000
Feb 28 20:48:12.053221 vlab-01 NOTICE syncd#syncd: :- uninit_switch_BCM56850:910: remove switch 0x2100000000
Feb 28 20:48:12.053221 vlab-01 NOTICE syncd#syncd: :- syncd_main: remove switch took 0.227098 sec



Feb 28 20:48:12.053221 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.053221 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x10000001f
Feb 28 20:48:12.053221 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.053221 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x10000001f
Feb 28 20:48:12.053221 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.053221 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000020
Feb 28 20:48:12.055412 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.055412 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x10000001f



Feb 28 20:48:12.060841 vlab-01 NOTICE syncd#syncd: :- syncd_main:4047: calling api uninitialize
Feb 28 20:48:12.060841 vlab-01 NOTICE syncd#syncd: :- clear_local_state:467: clearing local state
Feb 28 20:48:12.060841 vlab-01 NOTICE syncd#syncd: :- unittestChannelThreadProc:379: exit VS unittest channel thread
Feb 28 20:48:12.965590 vlab-01 NOTICE syncd#syncd: :- fdbAgingThreadProc:453: ending fdb aging thread
Feb 28 20:48:12.965590 vlab-01 NOTICE syncd#syncd: :- syncd_main:4056: uninitialize finished
Feb 28 20:48:12.965804 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.965804 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x10000001d
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x10000001e
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x10000001e
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000006
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000009
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000009
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x10000000d
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x10000000d
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000011
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000018
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000018
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000019
Feb 28 20:48:12.976416 vlab-01 ERR syncd#syncd: :- internal_vs_generic_get:46: failed to find switch oid:0x2100000000 in switch state map
Feb 28 20:48:12.976416 vlab-01 WARNING syncd#syncd: :- process_packet_for_fdb_event:537: failed to get port vlan id from port oid:0x100000019
Feb 28 20:48:13.046478 vlab-01 INFO kernel: [  405.930461] Bridge: port 24(Ethernet96) entered disabled state
Feb 28 20:48:13.046543 vlab-01 INFO kernel: [  405.932789] device Ethernet96 left promiscuous mode
Feb 28 20:48:13.046550 vlab-01 INFO kernel: [  405.932791] Bridge: port 24(Ethernet96) entered disabled state
Feb 28 20:48:13.133873 vlab-01 INFO kernel: [  406.018948] Bridge: port 23(Ethernet92) entered disabled state
Feb 28 20:48:13.137881 vlab-01 INFO kernel: [  406.022592] device Ethernet92 left promiscuous mode
Feb 28 20:48:13.137895 vlab-01 INFO kernel: [  406.022594] Bridge: port 23(Ethernet92) entered disabled state
Feb 28 20:48:13.189786 vlab-01 INFO kernel: [  406.074196] Bridge: port 22(Ethernet88) entered disabled state
Feb 28 20:48:13.189814 vlab-01 INFO kernel: [  406.075924] device Ethernet88 left promiscuous mode
Feb 28 20:48:13.189818 vlab-01 INFO kernel: [  406.075926] Bridge: port 22(Ethernet88) entered disabled state
Feb 28 20:48:13.245802 vlab-01 INFO kernel: [  406.129795] Bridge: port 20(Ethernet80) entered disabled state
Feb 28 20:48:13.245828 vlab-01 INFO kernel: [  406.131422] device Ethernet80 left promiscuous mode
Feb 28 20:48:13.245832 vlab-01 INFO kernel: [  406.131424] Bridge: port 20(Ethernet80) entered disabled state
Feb 28 20:48:13.305790 vlab-01 INFO kernel: [  406.188503] Bridge: port 21(Ethernet84) entered disabled state
Feb 28 20:48:13.309784 vlab-01 INFO kernel: [  406.193659] device Ethernet84 left promiscuous mode
Feb 28 20:48:13.309798 vlab-01 INFO kernel: [  406.193661] Bridge: port 21(Ethernet84) entered disabled state
Feb 28 20:48:13.377813 vlab-01 INFO kernel: [  406.263672] PortChannel0003: Port device Ethernet120 removed
Feb 28 20:48:13.414148 vlab-01 INFO kernel: [  406.299086] PortChannel0004: Port device Ethernet124 removed
Feb 28 20:48:13.465958 vlab-01 INFO kernel: [  406.348376] PortChannel0001: Port device Ethernet112 removed
Feb 28 20:48:13.505784 vlab-01 INFO kernel: [  406.390569] PortChannel0002: Port device Ethernet116 removed
Feb 28 20:48:13.633802 vlab-01 INFO kernel: [  406.516627] Bridge: port 15(Ethernet76) entered disabled state
Feb 28 20:48:13.633830 vlab-01 INFO kernel: [  406.518284] device Ethernet76 left promiscuous mode
Feb 28 20:48:13.633833 vlab-01 INFO kernel: [  406.518286] Bridge: port 15(Ethernet76) entered disabled state
Feb 28 20:48:13.689947 vlab-01 INFO kernel: [  406.575122] Bridge: port 14(Ethernet72) entered disabled state
Feb 28 20:48:13.693794 vlab-01 INFO kernel: [  406.576713] device Ethernet72 left promiscuous mode
Feb 28 20:48:13.693809 vlab-01 INFO kernel: [  406.576715] Bridge: port 14(Ethernet72) entered disabled state
Feb 28 20:48:13.753803 vlab-01 INFO kernel: [  406.637277] Bridge: port 12(Ethernet64) entered disabled state
Feb 28 20:48:13.753829 vlab-01 INFO kernel: [  406.638778] device Ethernet64 left promiscuous mode
Feb 28 20:48:13.753833 vlab-01 INFO kernel: [  406.638780] Bridge: port 12(Ethernet64) entered disabled state
Feb 28 20:48:13.814181 vlab-01 INFO kernel: [  406.698227] Bridge: port 13(Ethernet68) entered disabled state
Feb 28 20:48:13.814209 vlab-01 INFO kernel: [  406.700449] device Ethernet68 left promiscuous mode
Feb 28 20:48:13.814212 vlab-01 INFO kernel: [  406.700451] Bridge: port 13(Ethernet68) entered disabled state
Feb 28 20:48:13.879029 vlab-01 INFO kernel: [  406.762171] Bridge: port 11(Ethernet60) entered disabled state
Feb 28 20:48:13.879058 vlab-01 INFO kernel: [  406.765303] device Ethernet60 left promiscuous mode
Feb 28 20:48:13.879061 vlab-01 INFO kernel: [  406.765305] Bridge: port 11(Ethernet60) entered disabled state
Feb 28 20:48:13.943097 vlab-01 INFO kernel: [  406.827206] Bridge: port 10(Ethernet56) entered disabled state
Feb 28 20:48:13.943123 vlab-01 INFO kernel: [  406.829374] device Ethernet56 left promiscuous mode
Feb 28 20:48:13.943127 vlab-01 INFO kernel: [  406.829376] Bridge: port 10(Ethernet56) entered disabled state
Feb 28 20:48:13.998244 vlab-01 INFO kernel: [  406.881826] Bridge: port 8(Ethernet48) entered disabled state
Feb 28 20:48:13.998347 vlab-01 INFO kernel: [  406.884197] device Ethernet48 left promiscuous mode
Feb 28 20:48:13.998354 vlab-01 INFO kernel: [  406.884198] Bridge: port 8(Ethernet48) entered disabled state
Feb 28 20:48:14.000351 vlab-01 INFO syncd.sh[2850]: 2019-03-01 04:48:13,997 WARN received SIGTERM indicating exit request
Feb 28 20:48:14.000924 vlab-01 INFO syncd.sh[2850]: 2019-03-01 04:48:13,997 INFO waiting for syncd, rsyslogd to die
Feb 28 20:48:14.057805 vlab-01 INFO kernel: [  406.941155] Bridge: port 9(Ethernet52) entered disabled state
Feb 28 20:48:14.057828 vlab-01 INFO kernel: [  406.942744] device Ethernet52 left promiscuous mode
Feb 28 20:48:14.057831 vlab-01 INFO kernel: [  406.942745] Bridge: port 9(Ethernet52) entered disabled state
Feb 28 20:48:14.173802 vlab-01 INFO kernel: [  407.056913] Bridge: port 18(Ethernet16) entered disabled state
Feb 28 20:48:14.173826 vlab-01 INFO kernel: [  407.058401] device Ethernet16 left promiscuous mode
Feb 28 20:48:14.173830 vlab-01 INFO kernel: [  407.058403] Bridge: port 18(Ethernet16) entered disabled state
Feb 28 20:48:14.229947 vlab-01 INFO kernel: [  407.114691] Bridge: port 19(Ethernet20) entered disabled state
Feb 28 20:48:14.233855 vlab-01 INFO kernel: [  407.116668] device Ethernet20 left promiscuous mode
Feb 28 20:48:14.233885 vlab-01 INFO kernel: [  407.116670] Bridge: port 19(Ethernet20) entered disabled state
Feb 28 20:48:14.293978 vlab-01 INFO kernel: [  407.178739] Bridge: port 17(Ethernet12) entered disabled state
Feb 28 20:48:14.297791 vlab-01 INFO kernel: [  407.180433] device Ethernet12 left promiscuous mode
Feb 28 20:48:14.297807 vlab-01 INFO kernel: [  407.180435] Bridge: port 17(Ethernet12) entered disabled state
Feb 28 20:48:14.357799 vlab-01 INFO kernel: [  407.240205] Bridge: port 16(Ethernet8) entered disabled state
Feb 28 20:48:14.357821 vlab-01 INFO kernel: [  407.241700] device Ethernet8 left promiscuous mode
Feb 28 20:48:14.357824 vlab-01 INFO kernel: [  407.241701] Bridge: port 16(Ethernet8) entered disabled state
Feb 28 20:48:14.414303 vlab-01 INFO kernel: [  407.296329] Bridge: port 5(Ethernet4) entered disabled state
Feb 28 20:48:14.417752 vlab-01 INFO kernel: [  407.303508] device Ethernet4 left promiscuous mode
Feb 28 20:48:14.417766 vlab-01 INFO kernel: [  407.303510] Bridge: port 5(Ethernet4) entered disabled state
Feb 28 20:48:14.501761 vlab-01 INFO kernel: [  407.387394] Bridge: port 7(Ethernet44) entered disabled state
Feb 28 20:48:14.506258 vlab-01 INFO kernel: [  407.388954] device Ethernet44 left promiscuous mode
Feb 28 20:48:14.506272 vlab-01 INFO kernel: [  407.388956] Bridge: port 7(Ethernet44) entered disabled state
Feb 28 20:48:14.561758 vlab-01 INFO kernel: [  407.447075] Bridge: port 6(Ethernet40) entered disabled state
Feb 28 20:48:14.565784 vlab-01 INFO kernel: [  407.448597] device Ethernet40 left promiscuous mode
Feb 28 20:48:14.565800 vlab-01 INFO kernel: [  407.448599] Bridge: port 6(Ethernet40) entered disabled state
Feb 28 20:48:14.629944 vlab-01 INFO kernel: [  407.515586] Bridge: port 3(Ethernet32) entered disabled state
Feb 28 20:48:14.633790 vlab-01 INFO kernel: [  407.517111] device Ethernet32 left promiscuous mode
Feb 28 20:48:14.633806 vlab-01 INFO kernel: [  407.517113] Bridge: port 3(Ethernet32) entered disabled state
Feb 28 20:48:14.693924 vlab-01 INFO kernel: [  407.579380] Bridge: port 4(Ethernet36) entered disabled state
Feb 28 20:48:14.698493 vlab-01 INFO kernel: [  407.581256] device Ethernet36 left promiscuous mode
Feb 28 20:48:14.698510 vlab-01 INFO kernel: [  407.581258] Bridge: port 4(Ethernet36) entered disabled state
Feb 28 20:48:14.749792 vlab-01 INFO kernel: [  407.632344] Bridge: port 2(Ethernet28) entered disabled state
Feb 28 20:48:14.749817 vlab-01 INFO kernel: [  407.633803] device Ethernet28 left promiscuous mode
Feb 28 20:48:14.749820 vlab-01 INFO kernel: [  407.633804] Bridge: port 2(Ethernet28) entered disabled state
Feb 28 20:48:14.802021 vlab-01 INFO kernel: [  407.687073] Bridge: port 1(Ethernet24) entered disabled state
Feb 28 20:48:14.805783 vlab-01 INFO kernel: [  407.688682] device Ethernet24 left promiscuous mode
Feb 28 20:48:14.805798 vlab-01 INFO kernel: [  407.688683] Bridge: port 1(Ethernet24) entered disabled state
Feb 28 20:48:14.825819 vlab-01 INFO kernel: [  407.709362] device Bridge entered promiscuous mode
Feb 28 20:48:14.839859 vlab-01 INFO syncd.sh[2850]: 2019-03-01 04:48:14,838 INFO stopped: syncd (exit status 0)
Feb 28 20:48:14.842817 vlab-01 INFO syncd.sh[2850]: 2019-03-01 04:48:14,841 INFO stopped: rsyslogd (exit status 0)
Feb 28 20:48:15.030911 vlab-01 INFO containerd[352]: time="2019-02-28T20:48:15.030763734Z" level=info msg="shim reaped" id=793bb8daebe70dc2e78b7b49f1af0f70151b461516779c12c01a70d95f5e9c74
Feb 28 20:48:15.041047 vlab-01 INFO dockerd[356]: time="2019-02-28T20:48:15.040928477Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Feb 28 20:48:15.342261 vlab-01 INFO syncd.sh[10032]: syncd
Feb 28 20:48:15.359567 vlab-01 INFO systemd[1]: Stopped syncd service.
Feb 28 20:48:15.362854 vlab-01 NOTICE admin: Stopped  syncd ...

Steps to reproduce the issue:
1.
ANSIBLE_SCP_IF_SSH=y ansible-playbook -vvvv -i lab test_sonic.yml -l vlab-01 --vault-password-file=~/password.txt -e testcase_name=warm-reboot -e testbed_name=vms-kvm-t0 -e testbed_file=vtestbed.csv

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions