HPE OneView
1841624 Members
4132 Online
110182 Solutions
New Discussion

HPE ONEView CommandLet New-OVClusterProfile

 
dave04
Frequent Visitor

HPE ONEView CommandLet New-OVClusterProfile

 

I’m having an issue creating a Hypervisor Cluster Profile in HPE OneView using the PowerShell module. When I run the New-OVClusterProfile cmdlet, I immediately get this error:

New-OVClusterProfile: The "type" field content, "HypervisorClusterProfileV3", included in this request is not valid. Correct the content in the 'type' field of the JSON and retry the request.

When I check the PowerShell module source, it still uses HypervisorClusterProfileV3 as the cluster profile type (see screenshot).

Version 3 in psmVersion 3 in psm
However, when I look at existing cluster profiles created through the OneView GUI, they are all using HypervisorClusterProfileV6 (screenshot)Version 6 by gui-createdVersion 6 by gui-created.
So OneView clearly expects V6, but the PowerShell library is still hardcoded to V3.

I tried manually updating the PSM file so the cmdlet outputs “HypervisorClusterProfileV6”, but after doing that, the JSON that gets generated becomes invalid, and OneView returns errors saying there are “multiple problems with the JSON file.” So at this point V3 is rejected by the appliance, and V6 breaks the JSON structure if I try to force it.

problems with jsonproblems with json

My questions:

  • Is there official PowerShell support for HypervisorClusterProfileV6?

  • Is the OneView PowerShell module outdated compared to the REST API schema?

  • Is there a supported or documented method to create V6 Hypervisor Cluster Profiles via PowerShell?

  • Why does modifying the PSM file cause the JSON to become invalid—are there additional schema fields required for V6 that the module doesn’t know about?

Any help or clarification would be really appreciated. I’ll add screenshots below.