[ https://issues.apache.org/jira/browse/CLOUDSTACK-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Koneti updated CLOUDSTACK-3147: ------------------------------------- Description: Failed to Create System VM's in the ESX 5.0 using the latest systemVM template with the below error messages: 2013-06-21 16:18:20,009 DEBUG [cloud.storage.VolumeManagerImpl] (secstorage-1:null) Checking if we need to prepare 1 volumes for VM[SecondaryStorageVm|s-1-VM] 2013-06-21 16:18:20,017 DEBUG [storage.image.ImageDataFactoryImpl] (secstorage-1:null) template 8 is not in store:1, type:Image 2013-06-21 16:18:20,096 DEBUG [storage.datastore.ObjectInDataStoreManagerImpl] (secstorage-1:null) allow muliple create requests 2013-06-21 16:18:21,686 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-25:null) Ping from 4 2013-06-21 16:18:22,116 ERROR [vmware.manager.VmwareStorageManagerImpl] (DirectAgent-15:10.223.250.131) Unable to execute PrimaryStorageDownloadCommand due to exception 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) Then tried to import the template trough the Vcenter 5.0 manually and found the below error message "The OVF package requires unsupported hardware. Details:Line25: Unsupported hardware family 'vmx-09'." When tried with the ESX 5.1 it works fine. Attaching the management server logs. was: Failed to Create System VM's in the ESX 5.0 using the latest systemVM template with the below error messages: 2013-06-21 16:18:20,009 DEBUG [cloud.storage.VolumeManagerImpl] (secstorage-1:null) Checking if we need to prepare 1 volumes for VM[SecondaryStorageVm|s-1-VM] 2013-06-21 16:18:20,017 DEBUG [storage.image.ImageDataFactoryImpl] (secstorage-1:null) template 8 is not in store:1, type:Image 2013-06-21 16:18:20,096 DEBUG [storage.datastore.ObjectInDataStoreManagerImpl] (secstorage-1:null) allow muliple create requests 2013-06-21 16:18:21,686 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-25:null) Ping from 4 2013-06-21 16:18:22,116 ERROR [vmware.manager.VmwareStorageManagerImpl] (DirectAgent-15:10.223.250.131) Unable to execute PrimaryStorageDownloadCommand due to exception 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) Then tried to import the template trough the Vcenter 5.0 and found the below error message "The OVF package requires unsupported hardware. Details:Line25: Unsupported hardware family 'vmx-09'." When tried with the ESX 5.1 it works fine. > Failed to Create System VM's in the ESX 5.0 using the latest systemVM > template. > ------------------------------------------------------------------------------- > > Key: CLOUDSTACK-3147 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3147 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup > Affects Versions: 4.2.0 > Reporter: Kiran Koneti > Assignee: Sateesh Chodapuneedi > Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Failed to Create System VM's in the ESX 5.0 using the latest systemVM > template with the below error messages: > 2013-06-21 16:18:20,009 DEBUG [cloud.storage.VolumeManagerImpl] > (secstorage-1:null) Checking if we need to prepare 1 volumes for > VM[SecondaryStorageVm|s-1-VM] > 2013-06-21 16:18:20,017 DEBUG [storage.image.ImageDataFactoryImpl] > (secstorage-1:null) template 8 is not in store:1, type:Image > 2013-06-21 16:18:20,096 DEBUG > [storage.datastore.ObjectInDataStoreManagerImpl] (secstorage-1:null) allow > muliple create requests > 2013-06-21 16:18:21,686 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-25:null) Ping from 4 > 2013-06-21 16:18:22,116 ERROR [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-15:10.223.250.131) Unable to execute > PrimaryStorageDownloadCommand due to exception > 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) > Then tried to import the template trough the Vcenter 5.0 manually and found > the below error message > "The OVF package requires unsupported hardware. > Details:Line25: Unsupported hardware family 'vmx-09'." > When tried with the ESX 5.1 it works fine. > Attaching the management server logs. -- 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