Clean up operation not performed properly by nova .
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
while I associate a floating IP to an instance and when I remove fixed IP associated to that instance , fixed IP as well as floating IP are removed but when I list floating IP for the current tenant , floating IP list still maintains the old data . Floating IP list still shows the attachment of the fixed IP with the instance from which it was removed that is required clean up operations was not performed properly .
I reproduced this bug using the following steps:-
vyom@vyom:~$ nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| 7d4a97df-
| 973cc64d-
+------
vyom@vyom:~$ nova floating-ip-list
+------
| Ip | Server Id | Fixed Ip | Pool |
+------
| 172.24.4.10 | - | - | public |
| 172.24.4.16 | - | - | public |
| 172.24.4.15 | - | - | public |
| 172.24.4.11 | - | - | public |
| 172.24.4.7 |- | - | public |
| 172.24.4.12 | - | - | public |
| 172.24.4.5 | 973cc64d-
| 172.24.4.13 | - | - | public |
| 172.24.4.9 | - | - | public |
| 172.24.4.14 | - | - | public |
+-----
*Associating floating IP 172.24.4.10 to instance3 .
vyom@vyom:~$ nova floating-
vyom@vyom:~$ nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| 7d4a97df-
| 973cc64d-
+------
vyom@vyom:~$ nova floating-ip-list
+------
| Ip | Server Id | Fixed Ip | Pool |
+------
| 172.24.4.10 | 7d4a97df-
| 172.24.4.16 | - | - | public |
| 172.24.4.15 | - | - | public |
| 172.24.4.11 | - | - | public |
| 172.24.4.7 | - | - | public |
| 172.24.4.12 | - | - | public |
| 172.24.4.5 | 973cc64d-
| 172.24.4.13 | - | - | public |
| 172.24.4.9 | - | - | public |
| 172.24.4.14 | - | - | public |
+------
* Removing fixed ip from instance instance3
vyom@vyom:~$ nova remove-fixed-ip 7d4a97df-
vyom@vyom:~$ nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| 7d4a97df-
| 973cc64d-
+------
* Floating IP list still shows the old information .
vyom@vyom:~$ nova floating-ip-list
+------
| Ip | Server Id | Fixed Ip | Pool |
+------
| 172.24.4.10 | 7d4a97df-
| 172.24.4.16 | - | - | public |
| 172.24.4.15 | - | - | public |
| 172.24.4.11 | - | - | public |
| 172.24.4.7 | - | - | public |
| 172.24.4.12 | - | - | public |
| 172.24.4.5 | 973cc64d-
| 172.24.4.13 | - | - | public |
| 172.24.4.9 | - | - | public |
| 172.24.4.14 | - | - | public |
+-----
I think association of fixed IP 10.0.0.18 and server Id 7d4a97df-
Changed in nova: | |
assignee: | nobody → Anand Shanmugam (anand1712) |
Changed in nova: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in nova: | |
assignee: | Anand Shanmugam (anand1712) → nobody |
Changed in nova: | |
assignee: | nobody → sonu (sonu-bhumca11) |
tags: | added: db |
Changed in nova: | |
assignee: | nobody → Puja (pujachowdhary) |
status: | Confirmed → In Progress |
This bug report has an assignee for a while now but there is no patch
for that. It looks like that the chance of getting a patch is low.
I'm going to remove the assignee to signal to others that they can take
over if they like.
If you want to work on this, please:
* add yourself as assignee AND
* set the status to "In Progress" AND
* provide a (WIP) patch within the next 2 weeks after that.
If you need assistance, reach out on the IRC channel #openstack-nova or
use the mailing list.