[
https://issues.apache.org/jira/browse/CLOUDSTACK-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796678#comment-13796678
]
Koushik Das commented on CLOUDSTACK-4682:
-----------------------------------------
VM deployment with shared service offering and local compute offering is fine
as long as the data disk is on the same host as the VM. Attach volume was not
handling the scenarios correctly.
The following needs to be logic of attached volume:
1. if data volume scope is zone then allow attach (this is already there)
2. if data volume scope is cluster
a. if root volume scope is host, allow if both are in same cluster (already
there)
b. if root volume scope is zone, allow if vm and data volume in same
cluster (need to be fixed)
3. if data volume scope is host
a. allow if vm and data volume in same host (need to be fixed)
> VMs are getting deployed with shared service offering and local compute
> offering
> ----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4682
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4682
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.2.0, 4.2.1
> Environment: hyp:KVM
> Reporter: prashant kumar mishra
> Assignee: Koushik Das
> Priority: Critical
> Fix For: 4.2.1
>
> Attachments: Logs_DB.rar
>
>
> Steps to reproduce
> ---------------------------
> 1-prepare a CS setup with kvm host+zone wide primary storage
> 2-mark Local storage enabled to true at zone level and restart MS
> 3-create a local disk offering
> 4-deploy a vm with shared service offering and local compute offering
> expected
> ---------------
> vm deployment should fail because CS can't move volume between scope: HOST
> and ZONE
> Actual
> ----------
> vm deployment went successful with root disk on shared and data disk on
> local storage storage
> My observation
> ----------------------
> once i detach the data disk(created in step 4) ,was not able to attach data
> disk to vm(deployed in step 4)
> with error
> ---------------
> 2013-09-16 13:01:53,697 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-9:job-35 = [ ad075b33-d308-4056-bc8a-f3a7d71ad60f ]) Unexpected
> exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Can't move volume between
> scope: HOST and ZONE
> at
> com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1605)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1880)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> 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-09-16 13:01:53,702 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-9:job-35 = [ ad075b33-d308-4056-bc8a-f3a7d71ad60f ]) Complete
> async job-35 = [ ad075b33-d308-4056-bc8a-f3a7d71ad60f ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Can't move volume
> between scope: HOST and ZONE
--
This message was sent by Atlassian JIRA
(v6.1#6144)
