floating IP status is not changed when the floatingIP is disassociated
Bug #1691930 reported by
Sangho Shin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-onos |
Fix Released
|
Undecided
|
Sangho Shin | ||
Bug Description
Even when floating IPs are disassociated from VMs, the floating IP status in the floating IP update message from neutron is still ACTIVE.
It seems to be the bug of the neutron event, but we can fix it in our driver for now.
Please refer to the relevant fix from Plumgrid driver.
https:/
| Changed in networking-onos: | |
| assignee: | nobody → Sangho Shin (sanghoshin) |
| Changed in networking-onos: | |
| status: | New → Confirmed |
| Changed in networking-onos: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to networking-onos (master) | #1 |
| Changed in networking-onos: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/networking-onos ocata-eol | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1847186c3f53b02
Author: sanghoshin <email address hidden>
Date: Fri May 19 05:03:21 2017 +0000
Fix the bug of floating IP status is not changed in the floating IP update event from neutron when floating IPs are disassociated from VMs.
Change-Id: Ifc95205ae76b50
Closes-Bug: #1691930