Customers using vVOL with ESXi 8.0U2 may experience failures when accessing vVOL datastores as a result of bindVirtualVolume failures following setPEContext call failures.

Products

• VMware vSphere ESXi 8.0

Issue/Introduction

When attempting to access a vVOL datastore, failures occur when connecting to the vVOL datastore initially, but eventually succeed.

 

The following entries are present in the VVOL daemon log (/var/run/log/vvold.log)

"FINAL FAILURE setPEContext, error (STORAGE_FAULT / org.apache.axis2.databinding.ADBException: Unexpected subelement"
And/Or
"VP failed to setPEContext: STORAGE_FAULT (org.apache.axis2.databinding.ADBException: Unexpected subelement {http://vvol.data.vasa.vim.vmware.com/xsd}isUsedByStretchedContainer)  "

Environment

VMware vSphere ESXi 8.0 U2

Cause

The host occasionally sends an extra element as part of the ProtocolEndpoint VASA object in the setPEContext vasa call due to a bug in ESXi 8.0u2.

Resolution

At this time VMware is aware of this issue and it will be addressed in the upcoming ESXi 8.x release.

 

This issue has no workaround, but it will be resolved after some time with setPEContext succeeding. You can verify that setPEContext is passing successfully by looking for a specific message in the vVOL daemon log (vvold.log)

2024-03-03T06:37:42.168Z In(166) VVold[2103716]: [Originator@6876 sub=Default] VasaOp::SetPEContext [#169482]: ===> Issuing 'setPEContext' to VP [VP:Connected (Outstanding 0/5)]
2024-03-03T06:37:43.015Z In(166) VVold[2103716]: [Originator@6876 sub=Default] VasaOp[#169482] ===> FINAL SUCCESS setPEContext VP (VP) Container (VP) timeElapsed=846 msecs (#outstanding 0)