ML2 hierarchical port binding needs additional tests
Bug #1427291 reported by
Robert Kukura
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Medium
|
Unassigned |
Bug Description
Although the current unit tests cover the hierarchical port binding code reasonably well, additional tests are needed that verify the following:
* Binding loops are properly avoided
* Binding limit is detected
* Dead-end binding attempts are handled properly
Changed in neutron: | |
milestone: | kilo-3 → kilo-rc1 |
Changed in neutron: | |
milestone: | kilo-rc1 → liberty-1 |
Changed in neutron: | |
milestone: | liberty-1 → liberty-2 |
Changed in neutron: | |
milestone: | liberty-2 → liberty-3 |
Changed in neutron: | |
milestone: | liberty-3 → none |
Changed in neutron: | |
assignee: | Robert Kukura (rkukura) → Federico Ressi (federico-ressi-9) |
status: | New → In Progress |
Changed in neutron: | |
assignee: | Federico Ressi (federico-ressi-9) → nobody |
Changed in neutron: | |
assignee: | nobody → Sergey Belous (sbelous) |
Changed in neutron: | |
assignee: | Sergey Belous (sbelous) → nobody |
tags: | added: low-hanging-fruit |
To post a comment you must log in.
This bug has been here for a long time. What is its state? Is still valid? Specifications doesn't look to clear to me.
* Binding loops are properly avoided
What do you mean with this? How can this happen?
* Binding limit is detected
What do you mean with this? How can this happen?
* Dead-end binding attempts are handled properly
What do you mean with this? How can this happen?