Bug #3815

possible to give lease that is not in network

Added by ungleich GmbH about 6 years ago. Updated about 6 years ago.

Status:ClosedStart date:05/23/2015
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:worksforme Pull request:
Affected Versions:OpenNebula 4.10


As we managed the hosts, we recognized that chosing a wrong lease was possible.

The view should only show possible leases for the chosen host


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

  • Status changed from Pending to Closed
  • Resolution set to worksforme

Access is checked as cluster level: networks and hosts in the same cluster are supposed to work together. You can impose network-host checks if they are in the same cluster

#2 Updated by Nico Schottelius about 6 years ago

I think there is a slight misunderstanding here:

We have used a network definition like this:

NAME        = "cluster2" 
DESCRIPTION = "cluster2" 

BRIDGE = "br0" 

DNS             = "" 
GATEWAY         = "" 

    TYPE = "IP4",
    IP   = "",
    SIZE = "13" 

But where the actual address range has been out of the network. Opennebula accepts this, however it does not make any sense - does it?

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

Address ranges are in control of AR's. There is no check for CONTEXT variables. Multiple AR's with different address ranges, network masks or gateways can be combined in a network. You can define the Context variables per AR in this case.

Also available in: Atom PDF