github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix panic in vSphere when deploying on a single ESX node.

Browse Source 
Use ComputeResource instead of ClusterComputeResource when
initializing the vSphere Cloud Provider
This commit is contained in:
Ritesh H Shukla
2016-10-17 23:42:59 +00:00
parent bb0bc660cf
commit 26db528da3
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
pkg/cloudprovider/providers/vsphere/vsphere.go
View File

@@ -252,7 +252,7 @@ func readInstance(cfg *VSphereConfig) (string, string, error) {
var rp mo.ResourcePool var rp mo.ResourcePool
err = s.Properties(ctx, *vm.ResourcePool, []string{"parent"}, &rp) err = s.Properties(ctx, *vm.ResourcePool, []string{"parent"}, &rp)
if err == nil { if err == nil {
var ccr mo.ClusterComputeResource var ccr mo.ComputeResource
err = s.Properties(ctx, *rp.Parent, []string{"name"}, &ccr) err = s.Properties(ctx, *rp.Parent, []string{"name"}, &ccr)
if err == nil { if err == nil {
cluster = ccr.Name cluster = ccr.Name