neutron floatingip-associate on port can cause server exception
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Brian Haley |
Bug Description
Associating a floating IP address with a port, when it's not itself associated with an instance, can cause the neutron server to throw an exception, leaving neutron completely unusable.
Here's how to reproduce it:
1. Start-up devstack, having it clone the latest upstream code, making sure to enable dvr by setting Q_DVR_MODE=dvr_snat
(this will create a network, subnet, and router and attach it to private and ext-nets)
2. neutron net-list
3. neutron port-create $private_network_id
4. neutron floatingip-create $public_network_id
5. neutron floatingip-
You'll start seeting this in screen-q-svc.log:
2014-09-17 20:56:17.758 5423 DEBUG neutron.
2014-09-17 20:56:17.760 5423 ERROR oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.760 5423 TRACE oslo.messaging.
2014-09-17 20:56:17.768 5423 ERROR oslo.messaging.
And it will just keep repeating as the l3-agent retries the call.
The result is the l3-agent won't be able to do any work.
I have a fix I'll send out for review.
Changed in neutron: | |
assignee: | nobody → Brian Haley (brian-haley) |
tags: | added: l3-dvr-backlog |
Changed in neutron: | |
importance: | Undecided → High |
milestone: | none → juno-rc1 |
Changed in neutron: | |
assignee: | Brian Haley (brian-haley) → Carl Baldwin (carl-baldwin) |
Changed in neutron: | |
assignee: | Carl Baldwin (carl-baldwin) → Brian Haley (brian-haley) |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-rc1 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/122298
Review: https:/