Skip to main content
NetApp Knowledge Base

COTVC-1735: VASA Provider binds namespace incorrectly for bindVirtualVolume call

  1. Last updated
    Apr 7, 2025
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:
4/7/2025, 12:59:49 PM

Issue

When a ESXi host issues a bindVirtualVolume call, VP receives the bind request and it attaches the underlying namespace to the NVMe subsystem.
If a different host issues a bind request for already bound vVols, VP should return the existing NQN and NSID, where the namespace is already attached. However, the target host receives the wrong NQN.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.