vStorageObjectManager not able to create a disk under specified folder about rbvmomi

[jrgarcia]

@kartikaydw Just to make sure I'm understanding the issue correctly, the vmdk_spec refuses to allow you to pass a path which means that it always uses the default path and you need to use a non-default path. Is this correct?

[kartikaydw]

@jrgarcia Yes you are right, basically I want to create a disk under specified VM folder and then attach the virtual disk to the VM.

[jrgarcia]

@kartikaydw Looking at your code snippet, you are creating a VslmCreateSpecDiskFileBackingSpec, but the VslmCreateSpec takes a VslmCreateSpecBackingSpec and that takes an optional path parameter. I can see that the vmodl.db has this correctly.

...
"VslmCreateSpecBackingSpec"=>
  {"kind"=>"data",
   "props"=>
    [{"name"=>"datastore", "is-optional"=>false, "is-array"=>false, "version-id-ref"=>nil, "wsdl_type"=>"Datastore"},
     {"name"=>"path", "is-optional"=>true, "is-array"=>false, "version-id-ref"=>"vim.version.version12", "wsdl_type"=>"xsd:string"}],
   "wsdl_base"=>"DynamicData"},
...

If you use this type (VslmCreateSpecBackingSpec), does it work?

[kartikaydw]

Thanks @jrgarcia for looking into this.
Yes I tried using VslmCreateSpecBackingSpec in the below snippet , but it fails out with error

 vmdk_spec = RbVmomi::VIM::VslmCreateSpecBackingSpec(
    datastore: vmdk_datastore,
    #provisioningType: 'thin',
    path: "[#{vmdk_datastore.name}] #{vmdk_file_name}"
  )

vmdk_backing = RbVmomi::VIM::VslmCreateSpec(
capacityInMB: size.to_i * 1024,
backingSpec: vmdk_spec,
name: "[#{vmdk_datastore.name}] #{vmdk_file_name}",
)

vdisk = vim.serviceContent.vStorageObjectManager.CreateDisk_Task(
spec: vmdk_backing,
).wait_for_completion

Traceback (most recent call last):
1: from vCenter/add_disk.rb:172:in <main>' /usr/local/lib/ruby/gems/2.6.0/gems/rbvmomi-2.0.0/lib/rbvmomi/vim/Task.rb:14:in wait_for_completion': InvalidArgument: A specified parameter was not correct: spec.backingSpec (RbVmomi::Fault)

[jrgarcia]

Ok, just wanted to make sure. I'll continue to check into this. Thanks!

[jrgarcia]

I'm still looking into this. I'm waiting on feedback to confirm a suspicion I have. I'll let you know as soon as I have any info.

[kartikaydw]

Thanks @jrgarcia

[jrgarcia]

Ok, it appears that the path is expected to be a certain format. It should be an existing folder and nothing more meaning that you don't include [#{datastore.name}] or give a file name. It is just the name of an existing folder on that datastore. For example, instead of '[datastore1] folder1/folder2/filename.vmdk' you would just do 'folder1/folder2'.