So in comparing this to a 6.0 Cluster - this may be a problem with DRS.
The message "Cluster does not contain any hosts" what you get in 6.0 when DRS is set to manual or partially automated.
Just speculating, but some of the new DRS controls available in 6.5 may not properly integrate with the rest of the platform when set to "fully automated"
I plan on opening a case with VMware next week - but I dread the multitudes of flow-chart readers I will have to speak with before I get to someone that actually knows the product.
2 people found this helpful
We have the same Setup - Role on Datacenter without propagation and on the Ressorcepool - and get the message "Cluster does not contain Hosts.".
We had to give "Read" permission on at least one Host of the Cluster for this to be fixed. You could also set this on the Cluster itself and propagate but would consequently see all Hosts and Ressourcepools of other users/groups.
Hope this helps.
So part of the problem is that we (by our own SSAE statement) can not expose the hosts (hosts = "Infrastructure Resource") to our OUs.
This seems like an arbitrary problem, but not exposing Infrastructure to consumers is one of the fundamental tenants of Private Cloud Computing. Basically, if I can't make this work without exposing the hosts, I can't qualify vSphere 6.5 for our environment!
"The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities"
Same here .... latest version of 6.5
Did you ever get to the bottom of the permissions issue with v6.5? I've encountered the same issue (vCenter v6.5.0, build #4602587), but I ended up granting the group 'read-only' permissions to one of the hosts in the cluster without propagation. While this did work, I would love to know if VMware support 'fixed' this for you.
Anyone have a workaround for this in 6.5? I've got a lab environment used for Computer Science Students. I really don't want to give them read permissions on the host. The permission worked great on 6.0.
Same issues - this has ruined a big piece of our app development teams progress as we cant add the Read Host permissions like others have said.