Catalog vApp Templates Import from vSphere problems.

[kschroed]

I'm having two issues trying to import VMs from vSphere into an orgs catalog. First small issue being that an Org Administrator does not have the Import from vSphere option for their Org catalogs.

Second issue is an error when launching the Import from vSphere wizard I immediately receive an error: could not execute query - Numeric Overflow

Anyone else experiencing this or have any thoughts?

[WillL]

Only vCD admin have access to vSphere resource, on top of it to create Cloud resource for Orgnizations to use, so Org admin won't be able to reach vSphere resource directly.

What's the stack trace in vCD's log and vCenter's? It works fine in our environment.

[kschroed]

I'm not finding anything in the logs related to the error.

[dcouturier]

is there any solution to this error : could not execute query - Numeric Overflow ?

I have this error and don't know how to solve te problem

Thanks

[kschroed]

What I have found is that on certain more populated vCenter instances I get the Numeric Overflow when the vCenter is selected for import.  This error disappears though on search attempts that have text entered in the Text field under the vcenter drop down.  Seems perhaps since it defaults to All that there may be a limit to what that pop-up is capable of displaying without a filter.

[admin]

For the vSphere that's causing you problems, is there by any chance a VM with some really large disks? I think I just reproduced and fixed this bug, but wanted to see if I could confirm here that this is the root cause. I believe this was caused by a VM on the selected VC having disks that add up to over 2 TB in capacity. Certainly that does cause this error and the behavior is as you describe: filtering the VM selection criteria down to avoid this VM makes things work.

Please let me know if you have such a large VM. Either way, this should be fixed in the next release.

[rldleblanc]

I am trying to import a VM into vCloud that is 12.5 TB and I cannot import the VM because of this bug. I thought it was a problem becuase there are 11 hard disks attached, but I created a blank VM with 11 40 GB hard disks and I don't run into this problem. Does this mean that it is fixed in 1.5 or is there a 1.0.2 that will fix the problem?

Thanks,

Robert LeBlanc