Primary and secondary storage are both NFS from the management server. I'm able to mount and read/write to both from xenserver.
This is the SMlog from xenserver, just loops with the same over and over, kills the copy processes as soon as it starts. [27089] 2013-04-17 11:44:54.961908 SUCCESS [27089] 2013-04-17 11:44:54.962075 #### VMOPS exit copy_vhd_from_secondarystorage #### [27115] 2013-04-17 11:44:55.908821 #### VMOPS enter kill_copy_process #### [27115] 2013-04-17 11:44:55.908959 ['bash', '/opt/xensource/bin/kill_copy_process.sh', ''] [27115] 2013-04-17 11:44:55.925590 SUCCESS [27115] 2013-04-17 11:44:55.925730 #### VMOPS exit kill_copy_process #### [27124] 2013-04-17 11:44:57.107388 #### VMOPS enter copy_vhd_from_secondarystorage #### [27124] 2013-04-17 11:44:57.107529 ['bash', '/opt/xensource/bin/copy_vhd_from_secondarystorage.sh', '208.85.1.110:/export/secondary/template/tmpl/1/1/', '67bb7c6b-784a-9ed4-b370-abd0b950b908', 'cloud-c7143302-b71c-4cb7-ad6e-abd297c3ff19'] > Can you also please check the logs on Xenserver especially the SMlog - > that might give more clue > > On 17/04/13 9:20 AM, "Ahmad Emneina" <[email protected]> wrote: > >>my guess is that CloudStack cant copy the template from secondary to >>primary storage. Can you check the write permissions on your primary >>storage? >> >> >>On Tue, Apr 16, 2013 at 11:15 AM, Joe Schoonbeck <[email protected]> wrote: >> >>> Getting the below error, system VM's won't provision. Verified >>>networking >>> and vhd-util works on both the xenserver and master. I'm able to access >>> the NFS on the master from the xenserver, so no problems there either. >>>Any >>> ideas? >>> >>> >>> 2013-04-16 14:09:56,868 WARN [xen.resource.CitrixResourceBase] >>> (DirectAgent-26:null) can not create vdi in sr >>> 67bb7c6b-784a-9ed4-b370-abd0b950b908 >>> 2013-04-16 14:09:56,869 WARN [xen.resource.CitrixResourceBase] >>> (DirectAgent-26:null) Catch Exception >>> com.cloud.utils.exception.CloudRuntimeException on >>> host:3d714397-cd1f-4b11-aa8a-c3e4196093e3 for template: >>> nfs://208.85.1.110/export/secondary/template/tmpl/1/1/ due to >>> com.cloud.utils.exception.CloudRuntimeException: can not create vdi in >>>sr >>> 67bb7c6b-784a-9ed4-b370-abd0b950b908 >>> com.cloud.utils.exception.CloudRuntimeException: can not create vdi in >>>sr >>> 67bb7c6b-784a-9ed4-b370-abd0b950b908 >>> >>> >>> 2013-04-16 14:09:56,870 DEBUG [agent.manager.AgentManagerImpl] >>> (secstorage-1:null) Details from executing class >>> com.cloud.agent.api.storage.PrimaryStorageDownloadCommand: Catch >>>Exception >>> com.cloud.utils.exception.CloudRuntimeException on >>> host:3d714397-cd1f-4b11-aa8a-c3e4196093e3 for template: >>> nfs://208.85.1.110/export/secondary/template/tmpl/1/1/ due to >>> com.cloud.utils.exception.CloudRuntimeException: can not create vdi in >>>sr >>> 67bb7c6b-784a-9ed4-b370-abd0b950b908 >>> >>> 2013-04-16 14:09:56,870 DEBUG [cloud.template.TemplateManagerImpl] >>> (secstorage-1:null) Template 1 download to pool 200 failed due to Catch >>> Exception com.cloud.utils.exception.CloudRuntimeException on >>> host:3d714397-cd1f-4b11-aa8a-c3e4196093e3 for template: >>> nfs://208.85.1.110/export/secondary/template/tmpl/1/1/ due to >>> com.cloud.utils.exception.CloudRuntimeException: can not create vdi in >>>sr >>> 67bb7c6b-784a-9ed4-b370-abd0b950b908 >>> >>> > >
