[
https://issues.apache.org/jira/browse/CLOUDSTACK-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694623#comment-13694623
]
Kiran Koneti commented on CLOUDSTACK-2384:
------------------------------------------
The below message is observed in the logs which clearly states that the vmdk
file copy is failed but the response code shows the value as '0'.
2013-06-27 11:31:55,230 DEBUG [agent.transport.Request]
(AgentManager-Handler-8:null) Seq 13-1832845372: Processing: { Ans: , MgmtId:
7332683579487, via: 13, Ver: v1, Flags: 10,
[{"storage.CreatePrivateTemplateAnswer":{"_virtualSize":0,"_physicalSize":0,"result":false,"details":"CreatePrivateTemplateFromSnapshotCommand
exception: java.lang.Exception: unable to copy snapshot vmdk file
/mnt/SecStorage/260a9aae-b540-3bb3-bcbe-2c52303a815f/snapshots/2/33/ to
/mnt/SecStorage/260a9aae-b540-3bb3-bcbe-2c52303a815f/template/tmpl/2/205\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.createTemplateFromSnapshot(VmwareStorageManagerImpl.java:765)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:438)\ncom.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.execute(VmwareSecondaryStorageResourceHandler.java:137)\ncom.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:79)\ncom.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)\ncom.cloud.agent.Agent.processRequest(Agent.java:525)\ncom.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\ncom.cloud.utils.nio.Task.run(Task.java:83)\njava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\njava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\njava.lang.Thread.run(Thread.java:679)\n","wait":0}}]
}
2013-06-27 11:31:55,231 DEBUG [agent.transport.Request]
(Job-Executor-134:job-134) Seq 13-1832845372: Received: { Ans: , MgmtId:
7332683579487, via: 13, Ver: v1, Flags: 10, { CreatePrivateTemplateAnswer } }
2013-06-27 11:31:55,273 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-134:job-134) Complete async job-134, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.TemplateResponse@5127b3b1
When we check the template folder in the secondary storage it only shows the
.ovf file but the .vmdk file is not at all created.
"[root@Sanjeev-dev 205]# ls -ltr
total 8
-rwxrwxrwx+ 1 root root 6500 Jun 26 18:03
0293e39b-329b-4ae4-a7f3-f4a8bd007ebb.ovf"
I waited around 3 hrs to check if it takes longer time and creates the template
but it hasn't happened.
I tried it with the Centos template this time which is much smaller volume when
compared with the previous windows vm volumes.
> Template created from snapshot or root disk is not displayed in the templates
> view in VMware setup.
> ---------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2384
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2384
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
> Affects Versions: 4.2.0
> Environment: Vmware
> Reporter: Kiran Koneti
> Assignee: Fang Wang
> Priority: Blocker
> Fix For: 4.2.0
>
>
> The below are the steps followed.
> I created a VM with a root disk and data disk using the windows 2012 and
> windows 8 32bit ISO's.
> Case 1:
> In the case 1 stopped the windows 2012 machine and created the template the
> aysnc job shows completed for the same case but the template is not displayed
> in the UI.
> I waited for longer time i.e almost 1 day then I was able to see the same in
> the UI of the templates view.
> The DB details for the same still shows allocated and all the details are as
> below:
> *************************** 20. row ***************************
> id: 210
> unique_name: 221a6cfd2-f609-3cb6-a879-afdc47ca2c43
> name: Winserve8
> uuid: 0efb17b3-13d0-4e25-bb9b-709a4e71f584
> public: 1
> featured: 1
> type: USER
> hvm: 1
> bits: 64
> url: NULL
> format: OVA
> created: 2013-05-07 15:44:19
> removed: NULL
> account_id: 2
> checksum: 93418461b411aa5559bc978a9b0d73f3
> display_text: Winserve8
> enable_password: 0
> enable_sshkey: 0
> guest_os_id: 168
> bootable: 1
> prepopulate: 0
> cross_zones: 0
> extractable: 1
> hypervisor_type: VMware
> source_template_id: 204
> template_tag: NULL
> sort_key: 0
> size: NULL
> state: Allocated
> update_count: 0
> updated: NULL
> image_data_store_id: 1
> I initially observed only the ovf file and later after a day I was able to
> see the .vmdk,.ova and also templates.properties file.
> Case2:
> In the case 2 I took a snapshot of the windows 2012 root disk.
> from this snapshot I tried to create a template then I observed the similar
> behaviour.
> investigating into deep I found that the secondary storage has only the .ovf
> file and the details of the snapshot are as below:
> "*************************** 21. row ***************************
> id: 211
> unique_name: 272531697-0e83-3556-8a7f-346aa8d58beb
> name: CreatedfromSnapshot
> uuid: d110660c-48cf-4362-875a-e3ae068ef89d
> public: 1
> featured: 0
> type: USER
> hvm: 1
> bits: 64
> url: NULL
> format: RAW
> created: 2013-05-08 14:25:04
> removed: NULL
> account_id: 2
> checksum: NULL
> display_text: win8server
> enable_password: 0
> enable_sshkey: 0
> guest_os_id: 168
> bootable: 1
> prepopulate: 0
> cross_zones: 0
> extractable: 0
> hypervisor_type: VMware
> source_template_id: 204
> template_tag: NULL
> sort_key: 0
> size: NULL
> state: Allocated
> update_count: 0
> updated: NULL
> image_data_store_id: 1"
> I observed the same behaviour even with the centos VM .
--
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
