VMs failed to get ip in vxlan setup due to keyerror
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-vsphere |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When spawning around 4k VMs in 100 network scenario , around 500 Vms failed to get ip by throwing below keyerror exception.
And it is getting ip by restarting dhcp (S40network) in the VM.
build used: HOS 4.0 ((build 01-547)
Attached logs
2016-06-22 12:01:36.112 31012 ERROR networking_
2016-06-22 12:01:36.112 31012 ERROR networking_
2016-06-22 12:01:36.112 31012 ERROR networking_
2016-06-22 12:01:36.112 31012 ERROR networking_
2016-06-22 12:01:36.112 31012 ERROR networking_
2016-06-22 12:01:36.112 31012 ERROR networking_
2016-06-22 12:01:36.112 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
2016-06-22 12:01:36.113 31012 ERROR networking_
Changed in neutron: | |
status: | New → In Progress |
assignee: | nobody → Arun Kumar (arooncoomar) |
I see networking_vsphere and HOS in this bug report, are you even sure this is a Neutron bug?