Skip to main content

Exciting new changes are coming to the Knowledge Base site soon!
Starting April 4, 2023, you will notice Support-Specific categorization and improvements to the search filters on the site. In May, we will be launching a new and enhanced Site UI and Navigation. To know more, read our Knowledge Article.

NetApp Knowledge Base

Provision datastore task fails as Virtual Storage Console is unable to select a host

Views:
196
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

Virtual Storage Console

Issue

When provisioning a datastore at the ESXi level using Virtual Storage Console (VSC), a pop up error is thrown (as seen in the vSphere WebClient):

"There are no hosts under the selected item. You must select a datacenter, cluster, or host for the provisioning operation to work successfully"

clipboard_e7103a5ba9199cf05ae96f32509163e39.png

The error is generated when selecting the following in the vSphere WebClient: Host and Clusters > right-click on a ESXi host > click NetApp VSC > Provision Datastore

In VSC's kamino log, the following Null Pointer Exception (NPE) is seen:


2018-11-05 20:52:12,476 (pool-1207-thread-1) ERROR [EsxHostTaskManager] - Unable to get hostsystem info for: HostSystem:host-765 @ https://<vcentername>:443/sdk.
java.lang.NullPointerException
 at com.netapp.kamino.server.duplicator.EsxHostTaskManager.getHostInfo(EsxHostTaskManager.java:1378)
 at com.netapp.kamino.server.duplicator.EsxHostTaskManager$1.call(EsxHostTaskManager.java:1183)
 at com.netapp.kamino.server.duplicator.EsxHostTaskManager$1.call(EsxHostTaskManager.java:1172)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:748)

 

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

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device