Subscribe

VSC 4.2 error destroying a datastore

Getting this stack trace when doing a datastore removal. Is this a config error or known bug? Eventually the whole process times out the job fails.

2013-06-13 08:56:50,448 (qtp1230531773-28) ERROR [DatastoreUtil] - Unable to umount datastore :v3240b_twj3202 from esx8.unclass2.iesil

com.vmware.vim25.ManagedObjectNotFound

          at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

          at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

          at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

          at java.lang.reflect.Constructor.newInstance(Unknown Source)

          at java.lang.Class.newInstance0(Unknown Source)

          at java.lang.Class.newInstance(Unknown Source)

          at com.vmware.vim25.ws.XmlGen.fromXml(XmlGen.java:205)

          at com.vmware.vim25.ws.XmlGen.parseSoapFault(XmlGen.java:82)

          at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:134)

          at com.vmware.vim25.ws.VimStub.removeDatastore(VimStub.java:2484)

          at com.vmware.vim25.mo.HostDatastoreSystem.removeDatastore(HostDatastoreSystem.java:156)

          at com.netapp.kamino.server.duplicator.DatastoreUtil.destroyDatastore(DatastoreUtil.java:3265)

          at com.netapp.kamino.server.duplicator.DatastoreUtil.destroyDatastore(DatastoreUtil.java:3077)

          at com.netapp.kamino.server.ServerServiceImpl.destroyDataStore(ServerServiceImpl.java:2208)

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

          at java.lang.reflect.Method.invoke(Unknown Source)

          at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:562)

          at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:188)

          at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)

          at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)

          at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

          at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

          at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598)

          at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1367)

          at com.netapp.nvpf.container.vsphere.request.VSphereClientRequestContextFilter.doFilterInternal(VSphereClientRequestContextFilter.java:47)

          at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

          at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)

          at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)

          at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

          at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)

          at com.netapp.nvpf.container.util.GWTCacheFilter.doFilter(GWTCacheFilter.java:55)

          at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)

          at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:484)

          at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)

          at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524)

          at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:233)

          at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065)

          at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413)

          at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192)

          at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999)

          at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)

          at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)

          at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)

          at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)

          at org.eclipse.jetty.server.Server.handle(Server.java:350)

          at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454)

          at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:47)

          at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:900)

          at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:954)

          at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:851)

          at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)

          at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:66)

          at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:254)

          at org.eclipse.jetty.server.ssl.SslSocketConnector$SslConnectorEndPoint.run(SslSocketConnector.java:665)

          at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)

          at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)

          at java.lang.Thread.run(Unknown Source)

Re: VSC 4.2 error destroying a datastore

Note: this was taken from the kamino.log file

Re: VSC 4.2 error destroying a datastore

com.vmware.vim25.ManagedObjectNotFound

for

v3240b_twj3202


Indicates that vCenter was not able to locate that datastore with the identifier given.

It is likely that this is a config issue, and that vCenter is out of sync with the identifier for the datastore, since VSC is just taking the identifier from vCenter (based on the GUI action) and sending it back to vCenter.