You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Sunstone Interface for launching a new VM and selection a cluster or Host Placement sets two bad variables in "Host requirements expression".
Selecting a Cluster gives: (HYPERVISOR=undefined)
Selecting a Host gives: (HYPERVISOR=undefined) & (HOST_ID = 20)
HYPERVISOR=undefined is somewhat obvious and most user figure out to change that to "KVM" for example.
However HOST_ID will cost you a few days of confusion. It needs to be ID. Only that will work.
To Reproduce
Launch a VM and attempt to select a particular host to force it to be scheduled on that host.
Expected behavior
I expect the UI to set "Host requirements expression" properly for selected Host or cluster's HYPERVISOR type and ID variable should be correct.
In below screen shot, UI should automatically set the proper values of "(HYPERVISOR=kvm) & (ID = 20)"
Description
Sunstone Interface for launching a new VM and selection a cluster or Host Placement sets two bad variables in "Host requirements expression".
Selecting a Cluster gives: (HYPERVISOR=undefined)
Selecting a Host gives: (HYPERVISOR=undefined) & (HOST_ID = 20)
HYPERVISOR=undefined is somewhat obvious and most user figure out to change that to "KVM" for example.
However HOST_ID will cost you a few days of confusion. It needs to be ID. Only that will work.
To Reproduce
Launch a VM and attempt to select a particular host to force it to be scheduled on that host.
Expected behavior
I expect the UI to set "Host requirements expression" properly for selected Host or cluster's HYPERVISOR type and ID variable should be correct.
In below screen shot, UI should automatically set the proper values of "(HYPERVISOR=kvm) & (ID = 20)"
Details
Additional context
While this is easy to fix once you know about the issue. The HOST_ID bug has cost multiple user and even Community support Champion HOURS/DAYS of debug time pulling out their hair. See this Post which is also linked to two other User posts.
https://forum.opennebula.io/t/onprem-cannot-schedule-vm-there-is-no-suitable-host/13209/6
Progress Status
The text was updated successfully, but these errors were encountered: