Highlighted
Enthusiast
Enthusiast

Storage Profiles not retained

I'm having a issue where a vApp with two VM's one VM configured with a storage profile of "fast" and one VM configured with a storage profile of "slow" when saved to the catalog defaults to only a single storage profile requring a full copy for the VM that is not on the default.  If I change it once it is in the catalog back to what it was orignally it will clone out as expected.

Is this a bug or expected behivor?

Tags (1)
0 Kudos
4 Replies
Highlighted
Immortal
Immortal

As of right now, when you capture to catalog, you have to put them in the same storage profile.

0 Kudos
Highlighted
Enthusiast
Enthusiast

I take it this is a bug, is the team aware of this or do I need to submit some sort of request?

Thanks for the help!

0 Kudos
Highlighted
Immortal
Immortal

File a support request for vCLoud Director ... explain the current functionality, and the desired functionality.

There is also this:

https://www.vmware.com/contact/contactus.html?department=prod_request

0 Kudos
Highlighted
Immortal
Immortal

I do think we have a feature request in place for this ... to have a storage profile per disk on a VM, and to have that persist across clone or capture to catalog.

Also, can you mark on of the replies as answered, so that anyone who finds this thread knows the solution?

0 Kudos