Storage policy limit per PVDC

[Danooo]

Hi,

I have a problem adding storage profile to existing Provider VDC in vCloud Director 5.1.2. Storage profile is recognized but after it's added to PVDC it's not visible in the organizations. Also Datastorea & Datastores Clusters view states that newly added storage profile is not attached to PVDC.

I have recreated entire storage profile in vSphere but every time I have exactly same behavior.

I have noticed that currently I have 10 storage profiles attached into PVDC and all of them works fine. New one  (the one that I'm trying to add) is number 11. Maybe there is some limit of storage profiles per PVDC which I'm not aware of?

Any feedback will be appreciated.

Regards,

[IamTHEvilONE]

there should not be a limit that I am aware of.

If you add a new Profile, you have to add it to the provider vdc first.  go to the providers list, double click the provider, go to the profiles tab for storage, and then click plus.

afterwards, then you should be able to add the storage profile to the Org vDC afterwards.

[Danooo]

Hi, thanks for quick answer.

This is exactly what I did,

I have added new storage profile under PVDC using green plus button, and this shows blank under "Used" and "Provisioned" for new storage profile. After going to organization that use my PVDC I want to add storage profile to organization level, new storage profile is not visible.

The thing that interest me is that under Datastores & Datastores Clusters view, newly added storage profile is not assigned to any PVDC (shows 0 under PVDC). That's why I started to suspect it can be some storage profile limit per PVDC.

Regards,

[IamTHEvilONE]

In vCenter for this datastore profile, is it a datastore cluster?  if so, can you verify that all the datastores inside the cluster have the correct attributes/policy applied.

Otherwise, try to refresh the stoage policies from vCenters section.

If the capacity columns have a dash "-" in them, these are provisioned, used, free, then we either cannot compute the values or there are no detected Datastores.

It might be good to tag a datastore outside of a Storage DRS cluster and sync profiles again to see if it'll compute based off of the single datastore.  this would confirm that it's something to do with the storage drs cluster config.

It may also take up to 5 minutes to compute the capacity columns.  if this isn't working correctly, there are 4 stored procedures provided with the db schema.  execute each one of them sequentially just to force it to happen once.

[Danooo]

Thanks - I have tried both - storage cluster and single datastore, on datastore proper capability was added, still same results. I have left current configuration over the night but this didn't helped.

Can you point me to some articles about db schema that should be executed?

Regards,