Hi,

After changing the Service Offering I can't start the VM:


2014-10-07 08:27:53,286 DEBUG [vmware.mo.HostMO] (DirectAgent-418:10.3.1.2) 
find VM i-47-683-TBN on host
2014-10-07 08:27:53,286 DEBUG [vmware.mo.HostMO] (DirectAgent-418:10.3.1.2) 
load VM cache on host
2014-10-07 08:27:53,501 INFO  [vmware.resource.VmwareResource] 
(DirectAgent-418:10.3.1.2) VM i-47-683-TBN is no longer in vSphere
2014-10-07 08:27:53,502 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-418:null) Seq 46-951962452: Response Received: 
2014-10-07 08:27:53,502 DEBUG [agent.transport.Request] (DirectAgent-418:null) 
Seq 46-951962452: Processing:  { Ans: , MgmtId: 345050455587, via: 46, Ver: v1, 
Flags: 110, 
[{"StopAnswer":{"vncPort":0,"bytesSent":0,"bytesReceived":0,"result":true,"details":"VM
 i-47-683-TBN is no longer in vSphere","wait":0}}] }
2014-10-07 08:27:53,502 DEBUG [agent.transport.Request] 
(Job-Executor-33:job-1551) Seq 46-951962452: Received:  { Ans: , MgmtId: 
345050455587, via: 46, Ver: v1, Flags: 110, { StopAnswer } }
2014-10-07 08:27:53,502 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-33:job-1551) Cleanup succeeded. Details VM i-47-683-TBN is no 
longer in vSphere
2014-10-07 08:27:53,502 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(DirectAgent-418:null) Cleanup succeeded. Details VM i-47-683-TBN is no longer 
in vSphere
2014-10-07 08:27:53,503 DEBUG [agent.manager.AgentAttache] 
(DirectAgent-418:null) Seq 46-951962452: No more commands found
2014-10-07 08:27:53,543 DEBUG [cloud.network.NetworkManagerImpl] 
(Job-Executor-33:job-1551) Service SecurityGroup is not supported in the 
network id=316
2014-10-07 08:27:53,555 DEBUG [cloud.network.NetworkManagerImpl] 
(Job-Executor-33:job-1551) Changing active number of nics for network id=316 on 
-1
2014-10-07 08:27:53,583 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-33:job-1551) Successfully cleanued up resources for the vm 
VM[User|i-47-683-TBN] in Starting state
2014-10-07 08:27:53,587 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-33:job-1551) Root volume is ready, need to place VM in volume's 
cluster
2014-10-07 08:27:53,587 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-33:job-1551) Vol[1000|vm=683|ROOT] is READY, changing deployment 
plan to use this pool's dcId: 8 , podId: 8 , and clusterId: 12
2014-10-07 08:27:53,587 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-33:job-1551) DataCenter id = '8' provided is in avoid set, 
DeploymentPlanner cannot allocate the VM, returning.
2014-10-07 08:27:53,587 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-33:job-1551) DataCenter id = '8' provided is in avoid set, 
DeploymentPlanner cannot allocate the VM, returning.
2014-10-07 08:27:53,650 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-33:job-1551) VM state transitted from :Starting to Stopped with 
event: OperationFailedvm's original host id: 47 new host id: null host id 
before state transition: 46
2014-10-07 08:27:53,656 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-33:job-1551) Hosts's actual total CPU: 38384 and CPU after 
applying overprovisioning: 307072
2014-10-07 08:27:53,656 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-33:job-1551) release cpu from host: 46, old used: 75400,reserved: 
0, actual total: 38384, total with overprovisioning: 307072; new used: 
65800,reserved:0; movedfromreserved: false,moveToReserveredfalse
2014-10-07 08:27:53,656 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-33:job-1551) release mem from host: 46, old used: 
62679678976,reserved: 0, total: 68708712448; new used: 54089744384,reserved:0; 
movedfromreserved: false,moveToReserveredfalse
2014-10-07 08:27:53,727 INFO  [cloud.api.ApiDispatcher] 
(Job-Executor-33:job-1551) Unable to create a deployment for 
VM[User|i-47-683-TBN]

Reply via email to