Communication lost to N1kv vlan provider network after tenant network create/delete
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-cisco |
Confirmed
|
Undecided
|
Abhishek Raut |
Bug Description
OpenStack Version: Kilo
$ nova-manage version
2015.1
$ neutron --version
2.3.10
Communication is lost to the CSR for a short period of time after creating a network causing errors in the log when pings fail.
1. Why is communication lost for about 25 seconds after creating the network.
2. If not service impacting can we get rid of the error log
Steps to Repro:
1. From the Controller node setup a continuous ping to the CSR management interface
2. Create a network.
3. Immediately attach the network to the router (CSR)
4. Check the log for errors
5. Check the ping stats
2015-01-21 10:48:10.029 DEBUG neutron.
2015-01-21 10:48:10.029 DEBUG neutron.
2015-01-21 10:48:10.248 DEBUG neutron.
2015-01-21 10:48:12.096 ERROR neutron.
Command: ['ping', '-c', '5', '-W', '1', '-i', '0.2', '10.0.100.10']
Exit code: 1
Stdout: 'PING 10.0.100.10 (10.0.100.10) 56(84) bytes of data.\n\n--- 10.0.100.10 ping statistics ---\n5 packets transmitted, 0 received, 100% packet loss, time 832ms\n\n'
Stderr: ''
2015-01-21 10:48:12.097 WARNING neutron.
localadmin@
PING 10.0.100.10 (10.0.100.10) 56(84) bytes of data.
64 bytes from 10.0.100.10: icmp_seq=
1 ttl=255 time=1.06 ms
64 bytes from 10.0.100.10: icmp_seq=2 ttl=255 time=0.927 ms
64 bytes from 10.0.100.10: icmp_seq=3 ttl=255 time=1.00 ms
64 bytes from 10.0.100.10: icmp_seq=4 ttl=255 time=0.906 ms
64 bytes from 10.0.100.10: icmp_seq=5 ttl=255 time=1.03 ms
64 bytes from 10.0.100.10: icmp_seq=6 ttl=255 time=1.04 ms
64 bytes from 10.0.100.10: icmp_seq=7 ttl=255 time=1.18 ms
64 bytes from 10.0.100.10: icmp_seq=8 ttl=255 time=1.08 ms
64 bytes from 10.0.100.10: icmp_seq=9 ttl=255 time=1.37 ms
64 bytes from 10.0.100.10: icmp_seq=10 ttl=255 time=1.19 ms
64 bytes from 10.0.100.10: icmp_seq=11 ttl=255 time=0.993 ms
64 bytes from 10.0.100.10: icmp_seq=12 ttl=255 time=1.06 ms
64 bytes from 10.0.100.10: icmp_seq=13 ttl=255 time=1.12 ms
64 bytes from 10.0.100.10: icmp_seq=14 ttl=255 time=0.989 ms
64 bytes from 10.0.100.10: icmp_seq=15 ttl=255 time=0.951 ms
64 bytes from 10.0.100.10: icmp_seq=16 ttl=255 time=0.749 ms
64 bytes from 10.0.100.10: icmp_seq=17 ttl=255 time=0.944 ms
64 bytes from 10.0.100.10: icmp_seq=18 ttl=255 time=1.01 ms
64 bytes from 10.0.100.10: icmp_seq=19 ttl=255 time=1.15 ms
64 bytes from 10.0.100.10: icmp_seq=20 ttl=255 time=1.04 ms
64 bytes from 10.0.100.10: icmp_seq=21 ttl=255 time=1.04 ms
64 bytes from 10.0.100.10: icmp_seq=22 ttl=255 time=1.05 ms
64 bytes from 10.0.100.10: icmp_seq=23 ttl=255 time=0.920 ms
64 bytes from 10.0.100.10: icmp_seq=24 ttl=255 time=0.862 ms
64 bytes from 10.0.100.10: icmp_seq=25 ttl=255 time=0.998 ms
64 bytes from 10.0.100.10: icmp_seq=26 ttl=255 time=0.932 ms
64 bytes from 10.0.100.10: icmp_seq=27 ttl=255 time=0.926 ms
64 bytes from 10.0.100.10: icmp_seq=28 ttl=255 time=1.16 ms
64 bytes from 10.0.100.10: icmp_seq=29 ttl=255 time=1.03 ms
64 bytes from 10.0.100.10: icmp_seq=30 ttl=255 time=3.64 ms
64 bytes from 10.0.100.10: icmp_seq=56 ttl=255 time=4.22 ms
64 bytes from 10.0.100.10: icmp_seq=57 ttl=255 time=1.03 ms
64 bytes from 10.0.100.10: icmp_seq=58 ttl=255 time=1.34 ms
64 bytes from 10.0.100.10: icmp_seq=59 ttl=255 time=0.797 ms
^C
--- 10.0.100.10 ping statistics ---
59 packets transmitted, 34 received, 42% packet loss, time 58085ms
rtt min/avg/max/mdev = 0.749/1.
localadmin@
tags: |
added: csr removed: cisco |
description: | updated |
summary: |
- Communication lost to CSR after network create + Communication lost to N1kv vlan provider network after tenant network + create/delete |
Changed in networking-cisco: | |
assignee: | nobody → Abhishek Raut (abhraut) |
I verified this behavior in my test bed. Communication is indeed lost to the CSR mgmt network when a new tenant network is created or deleted. Step 3 : Immediately attach the network to the router (CSR) is not needed.
Pings to the CSR mgmt interface stops at step 2: network create itself
This network (created) has no relation to the mgmt network. It is a tenant network.
Also this happens when the tenant network that was created earlier is deleted.