[NETVIRT-1309] Orphaned vpn-portip-to-port entry after deleting VM Created: 13/Jun/18 Updated: 25/Jun/18 Resolved: 25/Jun/18 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Oxygen-SR3, Fluorine |
| Type: | Bug | Priority: | Medium |
| Reporter: | Vinh Nguyen | Assignee: | Vinh Nguyen |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The vpn-portip-to-port entry associates with VM remains after the VM is deleted. This might cause issue if netvirt checks for known neutron port via call to method VpnUtil.getNeutronPortFromVpnPortFixedIp. The entry is not removed even when the router (vpn) is removed. Version Tested: master Reproduction Steps: 1) Create net/subnet 2) Create VM on subnet 3) Create router 4) Add subnet to router The "vpn-portip-to-port" entry for the VM is added to DS: "neutron-vpn-portip-port-data": { ] 5) Delete the VM (fixed IP 10.100.1.15) - The vpn-portip-to-port entry associates with the deleted VM remains in DS, even though the port with fixed IP 10.100.1.15 is gone. 6) Remove the subnet from router 7) Delete the router The above vpn-portip-to-port entry still exists even though the router VPN is deleted
|