Backlog #4962

Prevent VMs from assigning Virtual Networks outside its cluster

Added by Gerben Meijer over 4 years ago. Updated over 3 years ago.

Status:PendingStart date:12/29/2016
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


There are two clusters; cluster 'foo' with a few KVM hosts and cluster 'bar' with a vcenter host. Both cluster 'foo' and 'bar' use VLANs, so there is a Virtual Network using vlan 10 for each, e.g. 'VLAN 10 - KVM' and 'VLAN 10 - VMWare'. These vlans are assigned only to their respective cluster.

In the cloud view, when a VM is made on KVM cluster 'foo', it is possible to select a vlan from cluster 'bar' - e.g. 'VLAN 10 - VMWare' - and to then create that VM template, which then fails to instantiate with this error:

"[TemplateInstantiate] Error allocating a new virtual machine template. Incompatible clusters in NIC. Network for NIC 0 is not in the same cluster as the one used by other VM elements (cluster 0)"

Sunstone should prevent the listing of incompatible VLAN types, or otherwise VLANs that are not assigned to that cluster, so that users in at least the 'cloud' view cannot select a combination that leads to this error, because an unusable template is left behind that needs to be removed.


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

  • Tracker changed from Bug to Backlog
  • Category set to Sunstone

Also available in: Atom PDF