Booting VM with a Floating IP and pinging it via that takes a long time with errors in L3-Agent logs when using DVR
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Undecided
|
Unassigned |
Bug Description
A Rally test to launch a VM, attach a floating IP and ping the VM via the floating IP 40 times in case of legacy routers vs DVR routers was done for comparison. Time taken to create network,subnet, launch VM, attach floating IP etc. are similar in legacy and DVR cases but for the VM to be pingable via the floating ip(after it has been booted with floating ip) it takes a lot more time in some iterations with DVR. The VM is ping ready(after booting and being given a floating ip) in less than a second not counting time to boot or attach floating ip in case of Legacy. However in case of DVR sometimes we see the VM being ping ready in less than 1 second whereas in some cases it takes around 250 seconds. Digging into the L3-agent logs on the computes we see this for the instances that were taking the most time to be pingable via the floating ip
https:/
Specifically we keep seeing errors like this:
2016-09-19 18:58:52.675 23696 DEBUG neutron.
2016-09-19 18:58:52.696 23696 ERROR neutron.
2016-09-19 18:58:52.697 23696 ERROR neutron.
However, it is worth noting that bumping up the ping timeout to about 300 seconds, all VMS are pingable but it takes 100-200x the time it was taking in legacy case.
This is the rally plugin used(create network, subnet, boot server with fip and ping):
https:/
The Rally results for legacy:
https:/
The Rally results for DVR:
https:/
tags: | added: l3-dvr-backlog |
Can you paste the parameters for the Rally scenario so people could reproduce this?