Hello!
I think we hit a bug, if you undeploy a VM from cluster 100 and then try to resume it the error says that is trying on cluster 0 “Incompatible clusters in NIC. Network for NIC 0 is not in the same cluster as the one used by other VM elements (cluster 0)”, or is it maybe a misconfigured scheduler? I’m on ONE 5.2.1.
The VM has ‘SCHED_REQUIREMENTS = "CLUSTER_ID=“100"”’
Any hint?
Regards,
Germán.
Hi GermanG,
For these kind of problems you can add the net manually to the proper cluster:
CLI:
use onecluster tool to associate a vnet to a cluster
$ onecluster addvnet
SUNSTONE:
Inside Networks | Virtual Networks section you can find the select cluster option
You can find more info here: http://docs.opennebula.org/5.4/operation/host_cluster_management/cluster_guide.html?highlight=clusters
CHeers
Thanks Sergio for your answer!
If I run:
onecluster show 100
I get (among other details)
VNETS
1
And showing onevnet show 1:
VIRTUAL NETWORK 1 INFORMATION
ID : 1
NAME : Cluster 100 Network
USER : oneadmin
GROUP : oneadmin
CLUSTERS : 100
So, everything seems to be in the proper place.