vnet can be deleted when it has leases in use
|Assignee:||Ruben S. Montero||% Done:|
|Category:||Core & System|
|Target version:||Release 4.6|
While it isn't possible to remove a lease from a vnet when it is in use, it is possible to delete a vnet which contains leases which are in use.
Steps to reproduce:
1. Create a vnet (testvnet), add a lease (188.8.131.52), associate that lease with a running guest.
2. Try to delete the lease:
$ onevnet rmleases testvnet 184.108.40.206
[VirtualNetworkRemoveLeases] Error modifying network leases. Error deleting lease, IP 220.127.116.11 is currently in use
3. Try to delete the vnet:
$ onevnet delete testvnet
$ onevnet show testvnet
VNET named testvnet not found.
command show: argument 0 must be one of vnetid
#1 Updated by Ruben S. Montero almost 7 years ago
Hi Mathew,We've been discussing about this, and we are not really sure about its implementation:
- First it make sense from the user point of view. For example we do not let you remove a host with VMs.
- On the other hand, the VM can work with the network (as opposed of a VM without a host). The MAC address, the network drivers of the host... Everything needed to keep the VMs running without the network is there.
So we are not sure about adding this check.
#5 Updated by Ruben S. Montero over 6 years ago
- Tracker changed from Backlog to Feature
- Status changed from Pending to New
- Assignee set to Ruben S. Montero
- Target version set to Release 4.6
It seems that this feature is useful to prevent IP/MAC collisions between networks. We are going for this for 4.6