[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739157#comment-13739157
 ] 

Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4143:
-----------------------------------------------------------------

Fix committed to 4.2 in commit :

Commit c850f0a0e3749090fe5ed7d5c410bf10d06b2281 in branch refs/heads/4.2 from 
[~vijayendrabvs]
 [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c850f0a ]
 
CLOUDSTACK-4139: [VMWARE][ZWPS] Failed to resize the volumes which are created 
from snapshot
 
Description:
 
    Support offline volume resize on ESX by creating a worker VM
     to attach the unattached volume to and then resize it.




I entered the wrong bug ID in the commit message - will mention this in a 
future commit when fixing 4139, apologies.
                
> [VMWARE] Resize request sent for the volumes which are not attached to the 
> instance 
> ------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4143
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4143
>             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
>            Reporter: Sailaja Mada
>            Assignee: Venkata Siva Vijayendra Bhamidipati
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: apilog.log, management-server.log, newdb.sql
>
>
> Steps:
> 1. Configure Adv zone with VMWARE cluster
> 2.  Deploy instance 
> 3. Add Data disk with 5 GB offering and attach to the instance  
> 4.  Resize works fine when it is attached to the instance 
> 5. Detach the DATA volume 
> 6. State of the DATA volume is ready and VM ID is none for this volume. 
> 7.  From UI i get to see resize option for this detached volume 
> 8. Try to resize this volume from 5 GB to 20 GB.
> Notes :    Even for Volumes which are created from snapshots would be in 
> ready state .  I think we are letting resize to be sent if the state of the 
> volume is Ready.  We should sent the request only if the volume has VM ID . 
> It failed as  :
> 2013-08-07 17:55:19,878 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
> ===START===  10.144.6.19 -- GET  
> command=resizeVolume&id=98b2a53b-1475-4658-a874-cf5c911e0faf&shrinkok=false&diskofferingid=ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88&size=27&response=json&sessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D&_=1375878539230
> 2013-08-07 17:55:19,913 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-1:null) submit async job-81 = [ 
> 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ], details: AsyncJobVO {id:81, userId: 
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null, 
> cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd, 
> cmdOriginator: null, cmdInfo: 
> {"id":"98b2a53b-1475-4658-a874-cf5c911e0faf","response":"json","sessionkey":"nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d","shrinkok":"false","cmdEventType":"VOLUME.RESIZE","ctxUserId":"3","httpmethod":"GET","_":"1375878539230","ctxAccountId":"3","diskofferingid":"ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88","ctxStartEventId":"286","size":"27"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-08-07 17:55:19,916 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
> ===END===  10.144.6.19 -- GET  
> command=resizeVolume&id=98b2a53b-1475-4658-a874-cf5c911e0faf&shrinkok=false&diskofferingid=ee864ab1-1c70-4aff-8eb3-dc01d6e6ab88&size=27&response=json&sessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D&_=1375878539230
> 2013-08-07 17:55:19,918 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Executing 
> org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-81 = [ 
> 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]
> 2013-08-07 17:55:19,949 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Access to 
> Vol[38|vm=null|DATADISK] granted to Acct[3-cdcuser1] by 
> DomainChecker_EnhancerByCloudStack_ccb7a71
> 2013-08-07 17:55:20,103 DEBUG [agent.transport.Request] 
> (Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq 
> 1-1575617095: Sending  { Cmd , MgmtId: 187767034175903, via: 1, Ver: v1, 
> Flags: 100011, 
> [{"com.cloud.agent.api.storage.ResizeVolumeCommand":{"path":"6344e3d83b6541ec863aaa6cd19fd66b","pool":{"id":2,"uuid":"004a6f4c-232c-3a09-9013-e47fe47da3fb","host":"10.102.192.100","path":"/cpg_vol/sailaja/finalps2","port":2049,"type":"NetworkFilesystem"},"vmInstance":"none","newSize":28991029248,"currentSize":27917287424,"shrinkOk":false,"wait":0}}]
>  }
> 2013-08-07 17:55:20,104 DEBUG [agent.transport.Request] 
> (Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq 
> 1-1575617095: Executing:  { Cmd , MgmtId: 187767034175903, via: 1, Ver: v1, 
> Flags: 100011, 
> [{"com.cloud.agent.api.storage.ResizeVolumeCommand":{"path":"6344e3d83b6541ec863aaa6cd19fd66b","pool":{"id":2,"uuid":"004a6f4c-232c-3a09-9013-e47fe47da3fb","host":"10.102.192.100","path":"/cpg_vol/sailaja/finalps2","port":2049,"type":"NetworkFilesystem"},"vmInstance":"none","newSize":28991029248,"currentSize":27917287424,"shrinkOk":false,"wait":0}}]
>  }
> 2013-08-07 17:55:20,110 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-148:null) Seq 1-1575617095: Executing request
> 2013-08-07 17:55:20,146 ERROR [vmware.resource.VmwareResource] 
> (DirectAgent-148:10.102.192.23) VM none does not exist in VMware datacenter
> 2013-08-07 17:55:20,146 ERROR [vmware.resource.VmwareResource] 
> (DirectAgent-148:10.102.192.23) Unable to resize volume
> java.lang.Exception: VM none does not exist in VMware datacenter
>         at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:625)
>         at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:560)
>         at 
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>         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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>         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-08-07 17:55:20,147 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-148:null) Seq 1-1575617095: Response Received:
> 2013-08-07 17:55:20,148 DEBUG [agent.transport.Request] 
> (DirectAgent-148:null) Seq 1-1575617095: Processing:  { Ans: , MgmtId: 
> 187767034175903, via: 1, Ver: v1, Flags: 10, 
> [{"com.cloud.agent.api.storage.ResizeVolumeAnswer":{"newSize":0,"result":false,"details":"failed
>  to resize volume:java.lang.Exception: VM none does not exist in VMware 
> datacenter","wait":0}}] }
> 2013-08-07 17:55:20,148 DEBUG [agent.transport.Request] 
> (Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Seq 
> 1-1575617095: Received:  { Ans: , MgmtId: 187767034175903, via: 1, Ver: v1, 
> Flags: 10, { ResizeVolumeAnswer } }
> 2013-08-07 17:55:20,157 WARN  
> [storage.datastore.ObjectInDataStoreManagerImpl] (Job-Executor-64:job-81 = [ 
> 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Unsupported data object (VOLUME, 
> org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@3b6272cd), no 
> need to delete from object in store ref table
> 2013-08-07 17:55:20,214 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Complete 
> async job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ], jobStatus: 1, 
> resultCode: 0, result: 
> org.apache.cloudstack.api.response.VolumeResponse@69470c10
> 2013-08-07 17:55:20,225 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-64:job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]) Done 
> executing org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for 
> job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 ]
> 2013-08-07 17:55:22,564 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-359:null) Ping from 2
> 2013-08-07 17:55:22,936 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
> ===START===  10.144.6.19 -- GET  
> command=queryAsyncJobResult&jobId=7fa69c72-c5e5-4aac-b91a-cddc1766a6b0&response=json&sessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D&_=1375878542366
> 2013-08-07 17:55:22,948 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-20:null) Async job-81 = [ 7fa69c72-c5e5-4aac-b91a-cddc1766a6b0 
> ] completed
> Notes:
> We are passing VM as none here to the vCenter.  We should handle before even 
> sending the request to hypervisor. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to