Back to bug 1001751
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Dave Allan | 2013-09-19 00:54:06 UTC | Status | NEW | ASSIGNED |
| CC | dallan | |||
| Assignee | rhos-maint | beagles | ||
| Jaroslav Henner | 2013-10-03 21:48:03 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=985954 | |
| Brent Eagles | 2013-12-03 12:20:00 UTC | Status | ASSIGNED | ON_DEV |
| Scott Lewis | 2013-12-13 18:16:24 UTC | Keywords | ZStream | |
| Scott Lewis | 2013-12-13 18:21:04 UTC | Target Milestone | --- | async |
| RHEL Program Management | 2013-12-18 01:28:17 UTC | Target Release | --- | 4.0 |
| Scott Lewis | 2014-01-09 20:06:05 UTC | Target Milestone | async | --- |
| Brent Eagles | 2014-01-10 20:25:20 UTC | Target Milestone | --- | A2 |
| John Skeoch | 2014-01-13 01:04:33 UTC | CC | hateya | |
| Brent Eagles | 2014-01-27 15:13:28 UTC | CC | jhenner | |
| Flags | needinfo?(jhenner) | |||
| Ami Jeain | 2014-02-03 10:28:16 UTC | QA Contact | ajeain | oblaut |
| Ofer Blaut | 2014-02-05 15:13:22 UTC | QA Contact | oblaut | yfried |
| Brent Eagles | 2014-02-06 21:01:04 UTC | CC | yfried | |
| Flags | needinfo?(yfried) | |||
| Brent Eagles | 2014-02-10 18:01:15 UTC | Status | ON_DEV | MODIFIED |
| Fixed In Version | openstack-nova-2013.2-0.25.rc1.el6ost | |||
| Flags | needinfo?(jhenner) needinfo?(yfried) | |||
| Lon Hohberger | 2014-02-10 21:00:47 UTC | Keywords | TestOnly | |
| Ofer Blaut | 2014-02-18 13:55:08 UTC | CC | beagles, oblaut | |
| Flags | needinfo?(beagles) | |||
| Brent Eagles | 2014-02-18 14:21:55 UTC | Status | MODIFIED | ON_QA |
| Doc Text | Cause: The neutron implementation of the network API for associating floating IP addresses did not check for previous assignments of the relevant address, nor remove the association if there was one found. Consequence: Floating IP addresses would appear to be assigned to multiple instances until background tasks reconciled the change in assignment. Fix: The neutron implementation checks for previous assignments of a floating IP and immediately removes the association upon establishing the new association. Result: The floating IP address information available to nova clients (python-novaclient, horizon) is immediately updated and the apparent duplicate assignment no longer occurs under these conditions. | |||
| Flags | needinfo?(beagles) | |||
| Martin Lopes | 2014-02-24 01:55:08 UTC | Status | ON_QA | VERIFIED |
| Status | VERIFIED | ON_QA | ||
| Status | ON_QA | VERIFIED | ||
| CC | mlopes | |||
| Doc Text | Cause: The neutron implementation of the network API for associating floating IP addresses did not check for previous assignments of the relevant address, nor remove the association if there was one found. Consequence: Floating IP addresses would appear to be assigned to multiple instances until background tasks reconciled the change in assignment. Fix: The neutron implementation checks for previous assignments of a floating IP and immediately removes the association upon establishing the new association. Result: The floating IP address information available to nova clients (python-novaclient, horizon) is immediately updated and the apparent duplicate assignment no longer occurs under these conditions. | Prior to this update, the Networking API implementation for associating floating IP addresses would not validate previous assignments of the same address, nor remove the association if one was found. As a result, floating IP addresses would appear to be assigned to multiple instances until background tasks reconciled the change in assignment. This issue has been resolved with this update, and Networking now checks for previous assignments of a floating IP and immediately removes the association upon establishing the new association. Consequently, the floating IP address information available to Compute clients (python-novaclient, Dashboard) is immediately updated, and the apparent duplicate assignment no longer occurs under these conditions. |
||
| Bruce Reeler | 2014-02-26 01:24:44 UTC | CC | breeler | |
| Doc Text | Prior to this update, the Networking API implementation for associating floating IP addresses would not validate previous assignments of the same address, nor remove the association if one was found. As a result, floating IP addresses would appear to be assigned to multiple instances until background tasks reconciled the change in assignment. This issue has been resolved with this update, and Networking now checks for previous assignments of a floating IP and immediately removes the association upon establishing the new association. Consequently, the floating IP address information available to Compute clients (python-novaclient, Dashboard) is immediately updated, and the apparent duplicate assignment no longer occurs under these conditions. | Prior to this update, the Networking API implementation for associating floating IP addresses would not validate previous assignments of the same address, nor remove the association if one was found. As a result, floating IP addresses would appear to be assigned to multiple instances until background tasks reconciled the change in assignment. This issue has been resolved with this update, and Networking now checks for previous assignments of a floating IP and immediately removes the association upon establishing the new association. Consequently, the floating IP address information available to Compute clients (python-novaclient, Dashboard) is immediately updated, and the apparent duplicate assignment no longer occurs under these conditions. |
||
| errata-xmlrpc | 2014-03-04 15:01:53 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2014-03-04 20:12:40 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-03-04 15:12:40 UTC | |||
| Russell Bryant | 2019-09-09 15:31:56 UTC | CC | rbryant |
Back to bug 1001751