[
https://issues.apache.org/jira/browse/CLOUDSTACK-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801751#comment-13801751
]
prashant kumar mishra commented on CLOUDSTACK-4681:
---------------------------------------------------
tested on top of commit 455a9f47974c7c25456311c3517408c3604f1263
steps
--------
1-prepare CS setup with 1 kvm host +cluster wide primary storage
2-deploy a vm with local SO
2-Add a zone wide PS
3-pust Cluster wide PS in maintenance mode
5-deploy vm with local service offering
6-cancel cluster wide PS maintenance mode
7-deploy vm with local SO
Expected
---------
vm deployment should fail in all case since local storage is not availabel
Logs
-------
2013-10-22 22:52:20,563 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-17:job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ]) Listing
clusters in order of aggregate capacity, that have (atleast one host with)
enough CPU and RAM capacity under this Zone: 1
2013-10-22 22:52:20,568 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-17:job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ]) Removing
from the clusterId list these clusters from avoid set: [1]
2013-10-22 22:52:20,571 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-17:job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ]) No clusters
found after removing disabled clusters and clusters in avoid list, returning.
2013-10-22 22:52:20,575 DEBUG [cloud.vm.UserVmManagerImpl]
(Job-Executor-17:job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ]) Destroying
vm VM[User|zwp] as it failed to create on Host with Id:null
2013-10-22 22:52:20,591 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-17:job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ]) VM state
transitted from :Stopped to Error with event: OperationFailedToErrorvm's
original host id: null new host id: null host id before state transition: null
2013-10-22 22:52:20,605 WARN [apache.cloudstack.alerts]
(Job-Executor-17:job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ])
alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
message:: Failed to deploy Vm with Id: 6, on Host with Id: null
2013-10-22 22:52:20,763 INFO [user.vm.DeployVMCmd] (Job-Executor-17:job-17 = [
f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ])
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|zwp]Scope=interface com.cloud.dc.DataCenter; id=1
2013-10-22 22:52:20,764 INFO [user.vm.DeployVMCmd] (Job-Executor-17:job-17 = [
f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ]) Unable to create a deployment for
VM[User|zwp]
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|zwp]Scope=interface com.cloud.dc.DataCenter; id=1
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3424)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2985)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2971)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-10-22 22:52:20,769 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-17:job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ]) Complete
async job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ], jobStatus: 2,
resultCode: 530, result: Error Code: 533 Error text: Unable to create a
deployment for VM[User|zwp]
2013-10-22 22:52:21,844 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-14:null) Ping from 3
2013-10-22 22:52:23,333 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null)
===START=== 10.252.192.57 -- GET
command=queryAsyncJobResult&jobId=f37bb7cc-42e4-48a3-9c22-c3735c2a0766&response=json&sessionkey=xH6bVPwWPI%2B2cio8HKuJ%2B7cmuqk%3D&_=1382442872499
2013-10-22 22:52:23,349 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-24:null) Async job-17 = [ f37bb7cc-42e4-48a3-9c22-c3735c2a0766 ]
completed
2013-10-22 22:52:23,397 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null)
===END=== 10.252.192.57 -- GET
command=queryAsyncJobResult&jobId=f37bb7cc-42e4-48a3-9c22-c3735c2a0766&response=json&sessionkey=xH6bVPwWPI%2B2cio8HKuJ%2B7cmuqk%3D&_=1382442872499
2013-10-22 22:52:23,442 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 10.252.192.57 -- GET
command=listVirtualMachines&id=363b28c0-4b58-4f03-bf04-52a06e7bd697&response=json&sessionkey=xH6bVPwWPI%2B2cio8HKuJ%2B7cmuqk%3D&_=1382442872608
2013-10-22 22:52:23,525 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.252.192.57 -- GET
command=listVirtualMachines&id=363b28c0-4b58-4f03-bf04-52a06e7bd697&response=json&sessionkey=xH6bVPwWPI%2B2cio8HKuJ%2B7cmuqk%3D&_=1382442872608
> data disk with local disk offering are geting created on shared storage .
> -----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4681
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4681
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.2.1
> Environment: hypervisor:KVM
> Reporter: prashant kumar mishra
> Assignee: Koushik Das
> Priority: Critical
> Fix For: 4.2.1
>
> Attachments: Logs_DB.rar
>
>
> Steps to reproduce
> ----------------------------
> 1-prapare a CS setup with kvm host +zone wide primary
> 2-deploy a vm
> 3-enable local storage at zone level(do not restart MS )
> 4-create a local disk offering
> 5-create a service offering with storage type local
> 6-deploy a vm with local SO and local disk offering
> Expected
> --------------
> 1-since local storage is not visible to MS(did not restart MS) vm deployment
> should fail
> Actual
> -----------
> vm root and data disk are getting created on shared storage
> My observation
> ----------------------
> 1-After MS restart root disk and data disk are getting created on local
> storage.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
