Cluster / Workload Domain creation using vVOL storage type is blocked in the SDDC Manager UI with the error "Error in validating Config Profiles"

Products

• VMware SDDC Manager
• VCF - MCOE - SDDC

Issue/Introduction

In the SDDC Manager UI, when attempting to create a Workload Domain or a Cluster with vVOL storage fails with an error:
Error in validating Config Profiles

 

The domainmanager logs in /var/log/vmware/vcf/domainmanager/domainmanager.log will report errors similar to:

2024-01-05T05:28:33.916+0000 ERROR [vcf_dm,65979381152560ceebbbdb489533da96,7f56] [c.v.v.c.s.NetworkConfigProfileGenerator,dm-exec-16]

vVol is not a valid storage-protocol

2024-01-05T05:28:33.917+0000 ERROR [vcf_dm,65979381152560ceebbbdb489533da96,7f56] [c.v.v.c.s.i.ClusterManagerIsServiceImpl,dm-exec-16] 

Caught an exception while generating Network Config Profile for [queryId : xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, storage : vVol, networkConfigProfileInputSpec :

{"hostIds":["xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}]

java.lang.RuntimeException: vVol is not a valid storage-protocol

 at com.vmware.vcf.clustermanager.services.NetworkConfigProfileGenerator.generateNetworkConfigProfileEms(NetworkConfigProfileGenerator.java:805)

 at com.vmware.vcf.clustermanager.services.impl.ClusterManagerIsServiceImpl.lambda$createNetworkConfigProfile$3(ClusterManagerIsServiceImpl.java:1387)

 at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804)

 at com.vmware.vcf.common.tracing.TraceRunnable.run(TraceRunnable.java:59)

 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)

 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)

 at java.base/java.lang.Thread.run(Thread.java:840)

Cause

This is due to the SDDC Manager UI sending an incorrect strong protocol to the API: /v1/clusters/network-config-profiles for storage type vVol.  Hence, the API is failing with error "vVol is not a valid storage-protocol".

Resolution

This issue is resolved VCF 5.2.

 

To workaround this issue, run through the following steps:

• Login to the SDDC Manager via SSH using the vcf user, and then su root.
• Create the file /home/vcf/feature.properties (Skip if the file already exists)
  touch /home/vcf/feature.properties
• Add the following line to disable the multi-pnic feature:
  feature.vcf.multivds.multipnic=false
• Update file permissions and ownership:
chmod 755 /home/vcf/feature.properties
chown vcf:vcf /home/vcf/feature.properties
• Restart all services to apply the changes:
  /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh

Following that, the Multi-Pnic UI will be disabled and the SDDC Manager UI will allow the WLD or Cluster creation allowing only 2 PNICs.

Additional Information

Considerations:

• Disabling the Multi-Pnic feature will limit all Day-N workflows from the SDDC Manager UI to 2 Pnics.
• Leveraging Multi Pnic for any workflows will need to be done using direct API calls.