Okay - reran the deployment from "new" UI and it displays "Request Failed (530)
- Request failed with status code 530".
This is ACS 4.15 deploying to vCenter 6.7 using a Windows10x64 image template.
Right now, I have global setting vmware.root.disk.controller as blank. If I
recall the previous build, I could set this setting at the instance provision
wizard. See anything below to indicate my hiccup?
Logs below:
2021-05-21 10:39:05,421 DEBUG [c.c.a.ApiServlet]
(qtp1026871825-20:ctx-90b111cd) (logid:03c48de3) ===START=== 10.4.89.3 -- GET
zoneid=1cf90fc6-1ae5-416f-a2b4-672176740ecb&podid=be90d04e-5257-43fb-97de-7727d10fae6a&clusterid=61445715-9baa-4768-863f-473652c324cc&hostid=7edc7494-a78f-4d72-8158-6dcbf7370f3f&templateid=1ada50d8-a523-4670-93c3-6d942169b7ae&serviceofferingid=5777d4fc-87b7-46c4-a253-4ff69f80b4ca&affinitygroupids=&nicnetworklist[0].nic=8&nicnetworklist[0].network=62bfbed1-d07c-4886-b4f4-bf594543bb28&name=CV-Test01&displayname=CV-Test01&command=deployVirtualMachine&response=json
2021-05-21 10:39:05,427 DEBUG [c.c.a.ApiServer] (qtp1026871825-20:ctx-90b111cd
ctx-d1342fe9) (logid:03c48de3) CIDRs from which account
'Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin]' is allowed to perform API
calls: 0.0.0.0/0,::/0
2021-05-21 10:39:05,462 TRACE [o.a.c.a.c.u.v.DeployVMCmd]
(qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) nic, '8', goes on
net, '62bfbed1-d07c-4886-b4f4-bf594543bb28'
2021-05-21 10:39:05,469 DEBUG [c.c.u.AccountManagerImpl]
(qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) Access granted to
Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin] to
org.apache.cloudstack.quota.vo.ServiceOfferingVO$$EnhancerByCGLIB$$f1711368@49f71a9e
by AffinityGroupAccessChecker
2021-05-21 10:39:05,469 DEBUG [c.c.u.AccountManagerImpl]
(qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) Access granted to
Acct[a5f712c7-ac2e-11eb-b0fb-00505695799f-admin] to null by
AffinityGroupAccessChecker
2021-05-21 10:39:05,493 DEBUG [c.c.n.NetworkModelImpl]
(qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) Service
SecurityGroup is not supported in the network id=204
2021-05-21 10:39:05,506 DEBUG [c.c.u.d.T.Transaction]
(qtp1026871825-20:ctx-90b111cd ctx-d1342fe9) (logid:03c48de3) Rolling back the
transaction: Time = 3 Name = qtp1026871825-20; called by
-TransactionLegacy.rollback:888-TransactionLegacy.removeUpTo:831-TransactionLegacy.close:655-Transaction.execute:38-UserVmManagerImpl.commitUserVm:3970-UserVmManagerImpl.commitUserVm:4157-UserVmManagerImpl.createVirtualMachine:3865-UserVmManagerImpl.createAdvancedVirtualMachine:3391-UserVmManagerImpl.createVirtualMachine:5315-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:62-DelegatingMethodAccessorImpl.invoke:43
2021-05-21 10:39:05,507 ERROR [c.c.a.ApiServer] (qtp1026871825-20:ctx-90b111cd
ctx-d1342fe9) (logid:03c48de3) unhandled exception executing api command:
[Ljava.lang.String;@32b6d5fc
java.lang.NullPointerException
at
com.cloud.vm.UserVmManagerImpl$4.doInTransaction(UserVmManagerImpl.java:4034)
at
com.cloud.vm.UserVmManagerImpl$4.doInTransaction(UserVmManagerImpl.java:3970)
at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
at
com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:3970)
at
com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:4157)
at
com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:3865)
at
com.cloud.vm.UserVmManagerImpl.createAdvancedVirtualMachine(UserVmManagerImpl.java:3391)
at
com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:5315)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy177.createVirtualMachine(Unknown Source)
at
org.apache.cloudstack.api.command.user.vm.DeployVMCmd.create(DeployVMCmd.java:719)
at
com.cloud.api.dispatch.CommandCreationWorker.handle(CommandCreationWorker.java:47)
at com.cloud.api.dispatch.DispatchChain.dispatch(DispatchChain.java:37)
at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:88)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:688)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:588)
at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:321)
at com.cloud.api.ApiServlet$1.run(ApiServlet.java:134)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:131)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:93)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
at
org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1386)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:547)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:590)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1610)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1580)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1215)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at
org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:767)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
at org.eclipse.jetty.server.Server.handle(Server.java:500)
at
org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383)
at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375)
at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273)
at
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:543)
at
org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:398)
at
org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
at
org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)
at java.base/java.lang.Thread.run(Thread.java:829)
2021-05-21 10:39:05,514 DEBUG [c.c.a.ApiServlet] (qtp1026871825-20:ctx-90b111cd
ctx-d1342fe9) (logid:03c48de3) ===END=== 10.4.89.3 -- GET
zoneid=1cf90fc6-1ae5-416f-a2b4-672176740ecb&podid=be90d04e-5257-43fb-97de-7727d10fae6a&clusterid=61445715-9baa-4768-863f-473652c324cc&hostid=7edc7494-a78f-4d72-8158-6dcbf7370f3f&templateid=1ada50d8-a523-4670-93c3-6d942169b7ae&serviceofferingid=5777d4fc-87b7-46c4-a253-4ff69f80b4ca&affinitygroupids=&nicnetworklist[0].nic=8&nicnetworklist[0].network=62bfbed1-d07c-4886-b4f4-bf594543bb28&name=CV-Test01&displayname=CV-Test01&command=deployVirtualMachine&response=json
-----Original Message-----
From: Corey, Mike <[email protected]>
Sent: Friday, May 21, 2021 7:50 AM
To: [email protected]
Subject: [CAUTION] RE: VMware Instance Error
Understood. I only tried the old UI because the instance deployment failed
under the new UI and there wasn't a specific error thrown to hint at an issue.
I'll try again today and dig through the logs and come back with findings.
MC
-----Original Message-----
From: Andrija Panic <[email protected]>
Sent: Thursday, May 20, 2021 5:47 PM
To: users <[email protected]>
Subject: Re: VMware Instance Error
Hi Mike,
that is expected in the old UI - at some point, new features were (in UI)
supported only for the new UI and not in old UI - so this failure is
expected/fine (I'm aware of the specific feature that is being
used/throwing an error here)
Get over the old UI, I know there are emotional connections (for me at
least) and use just the new UI :)
Best,
On Thu, 20 May 2021 at 22:57, Corey, Mike <[email protected]>
wrote:
> I’m having a VM instance fail and I can’t pinpoint the issue. Maybe
> someone has seen this error below – I see it at the legacy UI and not on
> the new UI. The new UI just fails the instance after the VM is created in
> vCenter.
>
>
>
> “Boot type and boot mode are not supported on VMware, as we honour what is
> defined in the template."
>
>
>
> I thought it was the global setting vmware.root.disk.controller – I had it
> as osdefault (failed) scsi (failed) and blank (failed) – so I’m not sure
> where or what is triggering the error/failure.
>
>
>
> Many thanks!
>
> Mike
>
>
>
>
>
>
>
>
>
> *Mike Corey*
>
>
> Technology Senior Consultant, IT CS CTW Operation & Virtualization Service
> US
>
>
> *SAP AMERICA, INC.* 3999 West Chester Pike, Newtown Square, 19073 United
> States
>
>
> T +1 610 661 0905, M +1 484 274 2658, E [email protected]
>
>
>
>
>
>
>
--
Andrija Panić
