cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4501) system vm not coming up in vmware ESX4.1 after upgrade from 3.0.4 to 4.2
Date Tue, 27 Aug 2013 04:23:52 GMT

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

Min Chen commented on CLOUDSTACK-4501:
--------------------------------------

Thanks Chandan for the clarification. shweta, can you please try with correct system vm template?

                
> system vm not coming up in vmware ESX4.1 after upgrade from 3.0.4 to 4.2
> ------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4501
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4501
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade, VMware
>    Affects Versions: 4.2.1
>         Environment: upgrade from 3.0.4 patch 1 to 4.2 
> with vmware EXI 4.1 
>            Reporter: shweta agarwal
>            Assignee: Min Chen
>            Priority: Blocker
>             Fix For: 4.2.1
>
>         Attachments: cloud-after-upgrade.dmp, cloud.dmp, management-server.log.tar.gz
>
>
> did an upgrade from 3.0.4 patch 1to 4.2 with two advance zone  one vmware4.2 and one
xen 6.0.2
> Now after upgrade system vm for vmware not coming up . hitting exception :
> 013-08-26 05:36:05,392 ERROR [storage.resource.VmwareStorageProcessor] (DirectAgent-15:10.147.40.27)
Unable to copy template to primary storage due to exception:Exception: javax.xml.ws.soap.SOAPFaultException
> Message:
> Required parameter spec is missing
> while parsing call information for method ImportVApp
> at line 1, column 110
> while parsing SOAP body
> at line 1, column 102
> while parsing SOAP envelope
> at line 1, column 38
> while parsing HTTP request for method importVApp
> on object of type vim.ResourcePool
> at line 1, column 0
> javax.xml.ws.soap.SOAPFaultException:
> Required parameter spec is missing
> while parsing call information for method ImportVApp
> at line 1, column 110
> while parsing SOAP body
> at line 1, column 102
> while parsing SOAP envelope
> at line 1, column 38
> while parsing HTTP request for method importVApp
> on object of type vim.ResourcePool
> at line 1, column 0
>         at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
>         at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119)
>         at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
>         at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
>         at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
>         at sun.proxy.$Proxy91.importVApp(Unknown Source)
>         at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.importVmFromOVF(HypervisorHostHelper.java:1321)
>         at com.cloud.hypervisor.vmware.mo.HostMO.importVmFromOVF(HostMO.java:736)

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

Mime
View raw message