NSX: floating ip status can be incorrectly reset
Bug #1357314 reported by
Salvatore Orlando
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
High
|
Salvatore Orlando | ||
Bug Description
This method can return None if:
1) an active floating ip is associated
2) a down floating ip is disassociated
Due to the default value for statsu being ACTIVE this implies that when a floating IP is associated at create-time its status is reset.
| no longer affects: | python-neutronclient |
| Changed in neutron: | |
| importance: | Undecided → High |
| assignee: | nobody → Salvatore Orlando (salvatore-orlando) |
| milestone: | none → juno-3 |
| Changed in neutron: | |
| milestone: | juno-3 → juno-rc1 |
Revision history for this message
| Salvatore Orlando (salvatore-orlando) wrote | #1 |
| Changed in neutron: | |
| status: | New → Fix Committed |
| Changed in neutron: | |
| status: | Fix Committed → Fix Released |
| Changed in neutron: | |
| milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
A big whoops on my side. This bug has been fixed by https:/