vVOL datastore are showing as inaccessible or 0 bytes
Applies to
- Element OS 9.x
- Element OS 10.x
- ONTAP vVOLs
- VMWare vCenter 6.x
- vCenter Plugin 3.x
Issue
- Some of the vVOLs are showing as inaccessible
- When creating a storage container and datastore using the vCenter Plugin for vVols on SolidFire, the datastore shows as 0 bytes in vCenter after creation.
- Storage container creation with datastore completes, but the resulting datastore shows as 0 bytes rather than the selected value.
- ESX hosts connected to the datastore show SSL errors in
/var/log/vvold.log
Example:
2018-02-13T16:29:07.853Z info vvold[FFE92B70] [Originator@6876 sub=Default]
VasaSession::Initialize url is empty
2018-02-13T16:29:07.853Z warning vvold[FFE92B70] [Originator@6876 sub=Default]
VasaSession::DoSetContext: Empty VP URL for VP (Solidfire)!
2018-02-13T16:29:07.853Z info vvold[FFE92B70] [Originator@6876 sub=Default] Initialize: Failed
to establish connection https://xxx.xxx.xxx.xxx:8444/vasa/servi...ce/version.xml
2018-02-13T16:29:07.853Z error vvold[FFE92B70] [Originator@6876 sub=Default] Initialize:
Unable to init session to VP Solidfire state: 0
2018-02-13T16:29:15.917Z info vvold[FFE92B70] [Originator@6876 sub=Default]
VVolUnbindManager::UnbindIdleVVols called
2018-02-13T16:29:15.917Z info vvold[FFE92B70] [Originator@6876 sub=Default]
VVolUnbindManager::UnbindIdleVVols done for 0 VVols
2018-02-13T16:29:20.085Z info vvold[FFA8BB70] [Originator@6876 sub=Default] Came to
SI::GetVvolContainer: container 1a185b33-fc9e-4aad-9735-d63b017ee95e
2018-02-13T16:29:20.085Z info vvold[FFA8BB70] [Originator@6876 sub=Default]
SI:GetVvolContainer successful for esxi-sf-vvol, id=, maxVVol=0 MB
2018-02-13T16:29:37.864Z info vvold[FFE92B70] [Originator@6876 sub=Default]
VasaSession::GetEndPoint: with url
https://xxx.xxx.xxx.xxx:8444/vasa/servi...ce/version.xml
2018-02-13T16:29:37.875Z error vvold[FFA4A380] [Originator@6876 sub=HttpConnectionPool000000] [ConnectComplete] Connect failed to <cs p:1f1a0ac8, TCP:xxx.xxx.xxx.xxx:8444>; cnx:
(null), error: N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
--> PeerThumbprint:
--> ExpectedThumbprint:
--> ExpectedPeerName: xxx.xxx.xxx.xxx
--> The remote host certificate has these problems:
-->
--> * unable to get local issuer certificate)
2018-02-13T16:29:37.875Z warning vvold[FFE92B70] [Originator@6876 sub=Default]
VasaSession::GetEndPoint: failed to get endpoint, err=SSL Exception: Verification parameters:
--> PeerThumbprint:
--> ExpectedThumbprint:
--> ExpectedPeerName: xxx.xxx.xxx.xxx
--> The remote host certificate has these problems:
-->
--> * unable to get local issuer certificate, using default
2018-02-13T16:29:37.875Z info vvold[FFE92B70] [Originator@6876 sub=Default]
VasaSession::Initialize url is empty
2018-02-13T16:29:37.875Z warning vvold[FFE92B70] [Originator@6876 sub=Default]
VasaSession::DoSetContext: Empty VP URL for VP (Solidfire)!
2018-02-13T16:29:37.875Z info vvold[FFE92B70] [Originator@6876 sub=Default] Initialize: Failed
to establish connection https://xxx.xxx.xxx.xxx:8444/vasa/servi...ce/version.xml
2018-02-13T16:29:37.875Z error vvold[FFE92B70] [Originator@6876 sub=Default] Initialize:
Unable to init session to VP Solidfire state: 0
2018-02-13T16:29:40.085Z info vvold[FFA4A380] [Originator@6876 sub=Default] Came to
SI::GetVvolContainer: container 1a185b33-fc9e-4aad-9735-d63b017ee95e
2018-02-13T16:29:40.086Z info vvold[FFA4A380] [Originator@6876 sub=Default]
SI:GetVvolContainer successful for esxi-sf-vvol, id=, maxVVol=0 MB
2018-02-13T16:29:45.917Z info vvold[FFE92B70] [Originator@6876 sub=Default]
VVolUnbindManager::UnbindIdleVVols called
2018-02-13T16:29:45.918Z info vvold[FFE92B70] [Originator@6876 sub=Default]
VVolUnbindManager::UnbindIdleVVols done for 0 VVols