DVR associating a new floatingip on existing network fails after restart of l3 agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Erik Colnick | ||
Kilo |
New
|
Undecided
|
Unassigned |
Bug Description
If DVR is enabled and an l3-agent is restarted, adding a new vm to an existing network and then associating a floating ip to that vm will fail and set all floating ip statuses on that network to 'ERROR'. In tracking down this issue, it appears that the 'floating_
To reproduce this issue:
On a running DVR enabled installation, create a network, subnet, external network and router.
Boot a vm on the network and associate a floating ip to the vm.
Restart the neutron-l3-agent on the compute node hosting the vm.
Boot a second vm on the existing network hosted on the compute node where the neutron-l3-agent has been restarted.
Associate a new floatingip to the second vm.
Observe that the flaotingip is in the ERROR state and that the vm is not pingable via that floatingip.
Changed in neutron: | |
assignee: | nobody → Erik Colnick (erikcolnick) |
tags: | added: ki |
tags: |
added: kilo-backport-potential liberty-backport-potential removed: ki |
tags: | added: l3-dvr-backlog |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
tags: | removed: kilo-backport-potential liberty-backport-potential |
Fix proposed to branch: master /review. openstack. org/244258
Review: https:/