[OVSDB-124] Bad openflow rules removal when VM is deleted Created: 02/Oct/14 Updated: 19/Oct/17 Resolved: 12/Jan/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Neutron |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Cédric Ollivier | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2132 |
| Description |
|
To manage broadcast messages (i.e. ARP), some OpenFlow rules are set with multiple actions (i.e. output:5,output:4). But when one of the port defined as output is removed (i.e. when VM shuts down), the OpenFlow rule is deleted. Then the second output can't receive broadcast messages. It induces strong issues when the second interface is a DHCP server. To reproduce (tested with Hydrogen):
|