Could not find 'VimSdk::Vim::ResourcePool about bosh-vsphere-cpi-release HOT 12 CLOSED

Hi @ljfranklin
Thank you for mentioning "Resource Pool". I went back to my environment and created a resource pool. Now it started deploying.

from bosh-vsphere-cpi-release.

@cpraveen412 we'll see if we can reproduce this. In the meantime, can you tell us which version of the vSphere CPI you are using? It should be listed in your BOSH Director manifest.

from bosh-vsphere-cpi-release.

@cpraveen412: We suspect that the vSphere Resource Pool CF-Datastore2 is not accessible from within the vSphere Cluster CF-Cluster or does not exist — perhaps CF-Datastore2 refers to a datastore and not a Resource Pool?

We opened a bug to make the error message more readable, e.g. "Resource Pool XXXXX is not accessible from Cluster YYYYY or does not exist." https://www.pivotaltracker.com/story/show/132845249

from bosh-vsphere-cpi-release.

hi @ljfranklin
I'm using Version 29.
CF-Datastore is just datastore name.

from bosh-vsphere-cpi-release.

I came across this when seeing the same error deploying a director. It's not the same case, but I do know that my resource pool exists and the user I'm deploying as can access it and create machines in it. I'm trying to figure out if this is issue is still open or not since it was tagged "open-for-contibution" and "planned-enhancement" after @cpraveen412 suggested it was resolved.

Is there still an open issue around this error?

from bosh-vsphere-cpi-release.

Hi @crdant, what version of the vSphere CPI are you using? Could you paste a snippet of your manifest where specifies the resource_pool property? Thanks

from bosh-vsphere-cpi-release.

In my case I'm using the Kubo deployment scripts to deploy a new director. It generates a manifest through a few steps of interpolation. The failure is when creating the stemcell. I can create a VM in the same resource pool as the same user with the govc cli.

The relevant snippet (which appears twice):

    vcenter:
      address: garundasana.crdant.net
      datacenters:
      - clusters:
        - primary-cluster:
            resource_pool: /home-lab/host/primary-cluster/Resources/zone-1
        datastore_pattern: ssd
        disk_path: kubo-disks
        name: home-lab
        persistent_datastore_pattern: ssd
        template_folder: kubo-templates
        vm_folder: kubo-vms

The CPI is version 44.

from bosh-vsphere-cpi-release.

from bosh-vsphere-cpi-release.

Thanks Chris. That is the fully qualified name in vSphere, but it looks like I can just use zone-1 and the deployment completes.

from bosh-vsphere-cpi-release.

from bosh-vsphere-cpi-release.

@yeshwantbabar : Should we support fully qualified names for the resource pools?

from bosh-vsphere-cpi-release.

Working on a support for specification of fully qualified names.
https://www.pivotaltracker.com/story/show/163777434

from bosh-vsphere-cpi-release.