VVOL - Datastore does not satisfy required properties CPG

[harleyrcc]

Hi All,

I've followed the "Implementing VMware Virtual Volumes on HP 3PAR StoreServ" and have arrived at the point where I'm able to create a virtual machine.

What I've noticed is that there is a warning whenever I try to use FC_r6 or FC_r5. If I try to use FC_r1 then the warning is not displayed.

If I proceed anyway things "appear" to be created ok...

The warning message is:

Datastore does not satisfy required properties "cpg" of value "(pbm.capability.types.DiscreteSet){dynamicType = null, dynamicProperty = null, values = (ANY) [ FC_r6] 

}" belonging to capability "provisioningGroup". The supported "cpg" is of value "(pbm.capability.types.DiscreteSet){dynamicType = null, dynamicProperty = null, values = (ANY) [ FC_r1]} However, the datastore matches other rule set. So, an empty profile blob will be sent during provsioning, if VSAN datastore selected. 

VCSA 6.0.0 2776510

ESXi 6.0.0 2809209

3PAR OS 3.2.1 MU3

HBA drivers: 6.0.0-qlnativefc-2.1.20.0

Any ideas?

Cheers,

Derek

[rufat-root]

The same issue. Is there any suggestion?

[Marcin_Trzyna]

As more people (if not all people using VVOLs) experience the same problem, it would be nice if somebody from HP could take a look at this problem and share their thoughts... Thanks in advance!

[rufat-root]

Any updates on this?

[Patrick Terlisten]

Hi everybody,

same here. 3PAR OS 3.2.1 MU2 and vSphere 6.0 U2. Is there a solution?

[Dennis Handly]

>If I proceed anyway things "appear" to be created ok

I finally got around to asking my colleague and he said:

This is a vSphere bug. The error message is invalid and can be ignored.

I don't have definitive information as to when VMware fixed it, but I believe it is fixed in vSphere 6.0 U2.

VMware internal bug number 1461228.

[SprinkleJames]

I don't think it's fixed in vCenter 6.0 U2. I'm seeing this issue too, in this environment:

vCSA 6.0 4541948 (U2a)
HPE-ESXi-6.0.0-Update2-iso-600.9.6.5.7
3PAR OS 3.2.2.612 (MU4)+P51,P56,P58,P59,P72

I cannot find any more info on this, besides the OP's thread at the VMware communities.

[SprinkleJames]

I've now updated vCenter to 6.0 U3b, and still seeing this.