Skip to main content
NetApp Knowledge Base

vCenter Plug-in Unexpected error: No thread-bound request found

Views:
423
Visibility:
Public
Votes:
3
Category:
not set
Specialty:
not set
Last Updated:

Applies to

  • NetApp SolidFire Cluster
  • NetApp Hybrid Cloud Infrastructure (HCI) Cluster
  • Management Services for Element Software and NetApp HCI v2.22.7
  • NetApp Element Plug-in for vSphere Client v5.0.0.0
  • VMware ESXi v7.0 Update 3

Issue

After updating VMware ESXi v6.7 Update 3 to VMware ESXi v7.0 Update 3, the NetApp Element Plug-in for vSphere Client v5.0.0.0 may prevent the creation of a new datastore.

The following message is displayed:

clipboard_e0c38490831b8b2471adcaf573d102c29.png

The vcp-remote log file will report the following stack trace:

2023-02-08 20:58:59,280 ERROR c.s.v.s.d.CreateDatastoreTask [pool-5-thread-1] No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
at org.springframework.web.context.request.RequestContextHolder.currentRequestAttributes(RequestContextHolder.java:131) ~[spring-web-5.3.23.jar!/:5.3.23]
at com.solidfire.vcp.vim25.gateway.VcenterSessionServiceImpl.extractRequestHeader(VcenterSessionServiceImpl.java:271) ~[classes!/:?]
at com.solidfire.vcp.vim25.gateway.VcenterSessionServiceImpl.getVimPort(VcenterSessionServiceImpl.java:183) ~[classes!/:?]
at com.solidfire.vcp.service.datastore.MapVolumeToHostsWithChapStep2.mapVolume(MapVolumeToHostsWithChapStep2.java:83) ~[classes!/:?]
at com.solidfire.vcp.service.datastore.MapVolumeToHostsWithChapStep2.execute(MapVolumeToHostsWithChapStep2.java:64) ~[classes!/:?]
at com.solidfire.vcp.service.datastore.AbstractDatastoreTask2.executeStep(AbstractDatastoreTask2.java:61) ~[classes!/:?]
at com.solidfire.vcp.service.datastore.CreateDatastoreTask.call(CreateDatastoreTask.java:103) ~[classes!/:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_302]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_302]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_302]
at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_302]

  • Unregistering the NetApp Element Plug-in for vSphere Client v5.0.0.0 and re-registering it does not resolve this issue
  • Creating the datastore using an iSCSI initiator group with Challenge-Handshake Authentication Protocol (CHAP)  Secrets enabled allows the new datastore creation to work as expected when using VMware ESXi v6.7 Update 3 and the NetApp Element Plug-in for vSphere Client v4.10.0.0

 

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.