Feature #2270

vnet can be deleted when it has leases in use

Added by Matthew Richardson over 6 years ago. Updated about 6 years ago.

Status:ClosedStart date:08/14/2013
Priority:NoneDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Core & System
Target version:Release 4.6
Resolution:fixed Pull request:

Description

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 (1.2.3.4), associate that lease with a running guest.

2. Try to delete the lease:
$ onevnet rmleases testvnet 1.2.3.4
[VirtualNetworkRemoveLeases] Error modifying network leases. Error deleting lease, IP 1.2.3.4 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

Associated revisions

Revision caf44846
Added by Ruben S. Montero about 6 years ago

Feature #2270: VNets can be only deleted if there are not used leases

History

#1 Updated by Ruben S. Montero over 6 years ago

Hi Mathew,

We've been discussing about this, and we are not really sure about its implementation:
  1. First it make sense from the user point of view. For example we do not let you remove a host with VMs.
  2. 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.

#2 Updated by Ruben S. Montero over 6 years ago

  • Category set to Core & System

#3 Updated by Ruben S. Montero over 6 years ago

  • Tracker changed from Bug to Request

Moving this to request till he further discuss

#4 Updated by Ruben S. Montero about 6 years ago

  • Tracker changed from Request to Backlog
  • Priority changed from Normal to None

#5 Updated by Ruben S. Montero about 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

#6 Updated by Ruben S. Montero about 6 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF