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

frank zhang commented on CLOUDSTACK-4426:
-----------------------------------------

no needs. I am putting a fix to 4555, it's revealed by my fix but it's an old 
bug which has been there for a while.
4554 has nothing to do with my fix.
                
> [VMware] [upgrade] system VM not coming up after upgrade from 3.0.4 to 4.2
> --------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4426
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4426
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: VMware
>    Affects Versions: 4.2.1
>            Reporter: shweta agarwal
>            Assignee: frank zhang
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: cloud_after_upgrade.dmp, cloud-backup.dmp, 
> management-server.log.tar.gz
>
>
> did and upgrade on 3.0.4 patch1 to 4.2 . 
> Having two advance zone 
> 1 with EXI 4.1 
> second with xen 
> After upgrade I destroyed system VM of Vmware zone . New system Vm failed to 
> start . Hitting exception .. 
> MS log snippet shows : 
> 2013-08-20 03:34:58,662 DEBUG [cloud.storage.VolumeManagerImpl] 
> (consoleproxy-1:null) Checking if we need to prepare 1 volumes for 
> VM[ConsoleProxy|v-41-VM] 
> 2013-08-20 03:34:58,677 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (consoleproxy-1:null) template 202 is already in store:6, type:Image 
> 2013-08-20 03:34:58,688 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (consoleproxy-1:null) template 202 is already in store:201, type:Primary 
> 2013-08-20 03:34:58,691 DEBUG [storage.volume.VolumeServiceImpl] 
> (consoleproxy-1:null) Found template 
> 202-2-d0b7f194-a096-3dd3-b9fa-7fb26ed627a7 in storage pool 201 with 
> VMTemplateStoragePool id: 11 
> 2013-08-20 03:34:58,706 DEBUG [storage.volume.VolumeServiceImpl] 
> (consoleproxy-1:null) Acquire lock on VMTemplateStoragePool 11 with timeout 
> 3600 seconds 
> 2013-08-20 03:34:58,724 WARN [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Exception: tar --no-same-owner -xf 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
>  
> java.io.IOException: Cannot run program "tar" (in directory 
> "/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl/2/202"): 
> java.io.IOException: error=13, Permission denied 
>         at java.lang.ProcessBuilder.start(ProcessBuilder.java:488) 
>         at com.cloud.utils.script.Script.execute(Script.java:183) 
>         at com.cloud.utils.script.Script.execute(Script.java:161) 
>         at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:147)
>  
>         at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:222)
>  
>         at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:70)
>  
>         at 
> com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147)
>  
>         at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
>  
>         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:1146)
>  
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
>         at java.lang.Thread.run(Thread.java:679) 
> Caused by: java.io.IOException: java.io.IOException: error=13, Permission 
> denied 
>         at java.lang.UNIXProcess.<init>(UNIXProcess.java:164) 
>         at java.lang.ProcessImpl.start(ProcessImpl.java:81) 
>         at java.lang.ProcessBuilder.start(ProcessBuilder.java:470) 
>         ... 17 more 
> 2013-08-20 03:34:58,726 ERROR [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Unable to unpack snapshot OVA file at: 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
>  
> 2013-08-20 03:34:58,727 ERROR [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Unable to copy template to primary storage due 
> to exception:Exception: java.lang.Exception 
> Message: Unable to unpack snapshot OVA file at: 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
>  
> java.lang.Exception: Unable to unpack snapshot OVA file at: 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
>  
>         at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:151)
>  
>         at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:222)
>  
>         at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:70)
>  

--
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