Error trying to 'createDatastores' Unable to connect to NFS server

[TonyReyes]

Scenario:

• - im using the lastest 3.7.8  HPE_OmniStack_Software_3.7.8_Q8A57-11063.zip
• - upgrade my gen10 servers to the lastest firmware using simplivity support pack SVTSP-2019_0315.04.ISO
• - fresh deployment, node 1 just added to vcenter server 6.5 u2d. VMware-VCSA-all-6.5.0-10964411.ISO
• root@omnicube-ip167-235:/home/svtcli# ping omni.cube.io
  PING omni.cube.io (192.168.167.235) 56(84) bytes of data.
  64 bytes from omni.cube.io (192.168.167.235): icmp_seq=1 ttl=64 time=0.036 ms

the ISSUE:

i cant add new datastore it says cant connec to NFS server, thanks for your help 

svtcli@omnicube-ip167-235:~$ svt-datastore-create --name test --policy Silver --size 100gb
................................................................................................................................................................................................................................................Command still in progress, but timed out To check status, execute
svt-task-show --task 8d722642-9485-771b-d56d-59bd9045af06:8d722642-9485-771b-d56d- 9bd9045af06:9cb07405-5314-473f-9cd5-aae804894b1d
svtcli@omnicube-ip167-235:~$ svt-task-show --task 8d722642-9485-771b-d56d-59bd9045af06:8d722642-9485-771b-d56d-59bd9045af06:9cb07405-5314-473f-9cd5-aae804894b1d
task 8d722642-9485-771b-d56d-59bd9045af06:8d722642-9485-771b-d56d-59bd9045af06:9cb07405-5314-473f-9cd5-aae804894b1d is 66 percent complete.

Additional Information:
Platform: Error trying to 'createDatastores' with names 'test': HVALPlatformException:Type: 'com.vmware.vim25.PlatformConfigFault' Detail: 'null' Cause: 'null' FaultCause: 'null' FaultMessage: '[key-vob.vmfs.nfs.mount.error.connect.failed message-NFS mount omni.cube.io:b3b7af11-3f5d-4424-9941-db605c8b283e failed: Unable to connect to NFS server.]'
....................

[DaveOb]

Did something go wrong during deployment ?

Was anything changed post deployment.

I think a support ticket would be needed to get to the bottom of it,

It may be best just to double check the configuration and redeploy it.