[jira] [Commented] (CLOUDSTACK-2895) Can't start a VM with 3 volumes attached [VMWare]
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343021#comment-14343021 ] Nicolas Lamirault commented on CLOUDSTACK-2895: --- This commit [1] seems fix the BUG. Regards [1]: https://github.com/apache/cloudstack/commit/a3babdd61ca8cae668a1b13c2724a0a6dd13fa05 > Can't start a VM with 3 volumes attached [VMWare] > - > > Key: CLOUDSTACK-2895 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2895 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 >Reporter: Nicolas Lamirault >Assignee: Damodar Reddy T > Fix For: 4.3.0 > > Attachments: CloudStack_VM_Volumes.png, > CloudStack_VM_Volumes_Error.png, CloudStack_VM_Volumes_Starting.png, > CloudStack_VM_Volumes_VSPhere.png, i-26-1713-VM.vmx > > > We got a VM with 3 volumes attach. > CS can't start the VM. We've got an error on the ESX. The output logs > (/scratch/log/hostd.log) : > 2013-06-07T13:24:59.745Z [80A1CB90 info > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] State Transition (VM_STATE_OFF -> VM_STATE_RECONFIGURING) > 2013-06-07T13:24:59.745Z [80A1CB90 verbose 'ha-host' opID=e81c34d3-d5] > ModeMgr::Begin: op = normal, current = normal, count = 2 > 2013-06-07T13:24:59.745Z [80A1CB90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Invoking interceptor:1-hbr > 2013-06-07T13:24:59.750Z [80A1CB90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Done invoking interceptor:1-hbr > 2013-06-07T13:24:59.779Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Current VM Tracking state: disabled > 2013-06-07T13:24:59.782Z [80281B90 info 'HostsvcPlugin' opID=e81c34d3-d5] > Lookupvm: World ID not set for VM 14 > 2013-06-07T13:24:59.783Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Adjusting tracking state for disk > /vmfs/volumes/f9d1a9e8-e9294a75/ROOT-108-149.vmdk to state disabled. > 2013-06-07T13:24:59.794Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Disk /vmfs/volumes/f9d1a9e8-e9294a75/ROOT-108-149.vmdk: > Tracking is already deactivated, skipping. > 2013-06-07T13:24:59.794Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Adjusting tracking state for disk > /vmfs/volumes/f9d1a9e8-e9294a75/5ea7e674b1324876985a6572fd40b72c.vmdk to > state disabled. > 2013-06-07T13:24:59.804Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Disk > /vmfs/volumes/f9d1a9e8-e9294a75/5ea7e674b1324876985a6572fd40b72c.vmdk: > Tracking is already deactivated, skipping. > 2013-06-07T13:24:59.804Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Adjusting tracking state for disk > /vmfs/volumes/f9d1a9e8-e9294a75/29e04b4363194c45a72638ac97281c57.vmdk to > state disabled. > 2013-06-07T13:24:59.813Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Disk > /vmfs/volumes/f9d1a9e8-e9294a75/29e04b4363194c45a72638ac97281c57.vmdk: > Tracking is already deactivated, skipping. > 2013-06-07T13:24:59.815Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Adjusting tracking state for disk > /vmfs/volumes/f9d1a9e8-e9294a75/615d905d145e4af3b284e935e754422e.vmdk to > state disabled. > 2013-06-07T13:24:59.824Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Disk > /vmfs/volumes/f9d1a9e8-e9294a75/615d905d145e4af3b284e935e754422e.vmdk: > Tracking is already deactivated, skipping. > 2013-06-07T13:24:59.824Z [80281B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] Setting VM's tracking state to disabled. > 2013-06-07T13:24:59.866Z [80816B90 info 'Libs'] VMHS: Transitioned > vmx/execState/val to poweredOff > 2013-06-07T13:24:59.872Z [80D06B90 verbose > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx'] No Upgrade > required > 2013-06-07T13:24:59.884Z [80816B90 info 'Libs'] Vix: [9253 > foundryVMPowerOps.c:973]: FoundryVMPowerStateChangeCallback: > /vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx, vmx/execState/val > = poweredOff. > 2013-06-07T13:24:59.902Z [80281B90 info > 'vm:/vmfs/volumes/f9d1a9e8-e9294a75/i-3-108-VM/i-3-108-VM.vmx' > opID=e81c34d3-d5] State Transition (VM_STATE_RECONFIG
[jira] [Created] (CLOUDSTACK-4779) Migrate Primary Storage
Nicolas Lamirault created CLOUDSTACK-4779: - Summary: Migrate Primary Storage Key: CLOUDSTACK-4779 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4779 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Reporter: Nicolas Lamirault When you launch the migration of primary storage to a VM stopped, CS raise an exception when trying to untar the file ova corresponding to the VM because it can not find it. He's not looking in the correct directory : /mnt/SecStorage/f85aba8f-b21d-3e56-9dd7-df90636eb181/volumes/370//4ded9248-1d3f-4bdd-be13-37adbb70bf66.ova the ova is in: /mnt/SecStorage/f85aba8f-b21d-3e56-9dd7-df90636eb181/volumes/370/4ded9248-1d3f-4bdd-be13-37adbb70bf66/4ded9248-1d3f-4bdd-be13-37adbb70bf66.ova The directory / mnt/SecStorage/f85aba8f-b21d-3e56-9dd7-df90636eb181 is one mounted by the SSVM. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-2860) Add new host into VMWare Cluster failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2860: -- Fix Version/s: 4.2.0 > Add new host into VMWare Cluster failed > --- > > Key: CLOUDSTACK-2860 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2860 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault > Fix For: 4.1.1, 4.2.0 > > -- 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
[jira] [Updated] (CLOUDSTACK-4046) Can't edit global settings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-4046: -- Fix Version/s: 4.2.0 > Can't edit global settings > -- > > Key: CLOUDSTACK-4046 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Minor > Fix For: 4.2.0 > > Attachments: CloudStack_GlobalSettingsOK2.png, > CloudStack_GlobalSettingsOK3.png, CloudStack_GlobalSettingsOK.png > > > Hi, > in our Cloudstack, we've got a strange behavior. > gradually as one moves down the settings, the "Edit" box disappears. > See screenshots. > Regards -- 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
[jira] [Created] (CLOUDSTACK-4046) Can't edit global settings
Nicolas Lamirault created CLOUDSTACK-4046: - Summary: Can't edit global settings Key: CLOUDSTACK-4046 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.1.0 Reporter: Nicolas Lamirault Priority: Minor Attachments: CloudStack_GlobalSettingsOK2.png, CloudStack_GlobalSettingsOK3.png, CloudStack_GlobalSettingsOK.png Hi, in our Cloudstack, we've got a strange behavior. gradually as one moves down the settings, the "Edit" box disappears. See screenshots. Regards -- 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
[jira] [Updated] (CLOUDSTACK-4046) Can't edit global settings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-4046: -- Attachment: CloudStack_GlobalSettingsOK3.png CloudStack_GlobalSettingsOK2.png CloudStack_GlobalSettingsOK.png > Can't edit global settings > -- > > Key: CLOUDSTACK-4046 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4046 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Minor > Attachments: CloudStack_GlobalSettingsOK2.png, > CloudStack_GlobalSettingsOK3.png, CloudStack_GlobalSettingsOK.png > > > Hi, > in our Cloudstack, we've got a strange behavior. > gradually as one moves down the settings, the "Edit" box disappears. > See screenshots. > Regards -- 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
[jira] [Comment Edited] (CLOUDSTACK-2860) Add new host into VMWare Cluster failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675970#comment-13675970 ] Nicolas Lamirault edited comment on CLOUDSTACK-2860 at 7/9/13 12:31 PM: After upgrading our PREPRODUCTION environment from 2.2.14 to 4.1.0, we try to add a new host to a cluster : 2013-06-05 16:25:29,863 DEBUG [utils.crypt.DBEncryptionUtil] (TP-Processor21:null) Error while decrypting: Kl0ud-prp 2013-06-05 16:25:29,865 ERROR [cloud.api.ApiServer] (TP-Processor21:null) unhandled exception executing api command: addHost org.jasypt.exceptions.EncryptionOperationNotPossibleException at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:918) at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725) at com.cloud.utils.crypt.DBEncryptionUtil.decrypt(DBEncryptionUtil.java:65) at com.cloud.dc.ClusterDetailsDaoImpl.findDetails(ClusterDetailsDaoImpl.java:73) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:619) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:505) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:355) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:315) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:776) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:705) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:898) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:662) Into database : mysql> select * from cluster_details where id = 5 ; +++--+---+ | id | cluster_id | name | value | +++--+---+ | 5 | 1 | password | Kl0ud-prp | +++--+---+ so we encrypt the database value like in "cloud-setup-encryption -m cloudstackprp -k cloudstackprp" : $ java -classpath /usr/share/java/jasypt-1.9.0.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="Kl0ud-prp" password=cloudstackprp verbose=false wrGoxbgFD4BO437vs+f5rP4fY53yRyn+ And update dabase : mysql> update cluster_details set value = 'wrGoxbgFD4BO437vs+f5rP4fY53yRyn+' where id = 5 ; We retry to add a new host and it works. Regards was (Author: nlamirault): After upgrading our PREPRODUCTION environment from 2.2.14 to 4.1.0, we try to add a new host to a cluster : 2013-06-05 16:25:29,863 DEBUG [utils.crypt.DBEncryptionUtil] (TP-Processor21:null) Error while decrypting: Kl0ud-prp 2013-06-05 16:25:29,865 ERROR [cloud.api.ApiServer] (TP-Processor21:null) unhandled exception executing api command: addHost org.jasypt.exceptions.EncryptionOperationNotPossibleException at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:918) at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725) at com.cloud.utils.crypt.DBEncryptionUtil.decrypt(DBEncryptionUtil.java:65) at com.cloud.dc.ClusterDetailsDaoImpl.findDetails(ClusterDetailsDaoI
[jira] [Updated] (CLOUDSTACK-2860) Add new host into VMWare Cluster failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2860: -- Fix Version/s: 4.1.1 > Add new host into VMWare Cluster failed > --- > > Key: CLOUDSTACK-2860 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2860 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault > Fix For: 4.1.1 > > -- 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
[jira] [Commented] (CLOUDSTACK-2860) Add new host into VMWare Cluster failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675970#comment-13675970 ] Nicolas Lamirault commented on CLOUDSTACK-2860: --- After upgrading our PREPRODUCTION environment from 2.2.14 to 4.1.0, we try to add a new host to a cluster : 2013-06-05 16:25:29,863 DEBUG [utils.crypt.DBEncryptionUtil] (TP-Processor21:null) Error while decrypting: Kl0ud-prp 2013-06-05 16:25:29,865 ERROR [cloud.api.ApiServer] (TP-Processor21:null) unhandled exception executing api command: addHost org.jasypt.exceptions.EncryptionOperationNotPossibleException at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.decrypt(StandardPBEByteEncryptor.java:918) at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.decrypt(StandardPBEStringEncryptor.java:725) at com.cloud.utils.crypt.DBEncryptionUtil.decrypt(DBEncryptionUtil.java:65) at com.cloud.dc.ClusterDetailsDaoImpl.findDetails(ClusterDetailsDaoImpl.java:73) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:619) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:505) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:355) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:315) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:776) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:705) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:898) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:662) Into database : mysql> select * from cluster_details where id = 5 ; +++--+---+ | id | cluster_id | name | value | +++--+---+ | 5 | 1 | password | Kl0ud-prp | +++--+---+ so we encrypt the database value like in "cloud-setup-encryption -m cloudstackprp -k cloudstackprp" : $ java -classpath /usr/share/java/jasypt-1.9.0.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="Kl0ud-prp" password=cloudstackprp verbose=false wrGoxbgFD4BO437vs+f5rP4fY53yRyn+ And update dabase : mysql> update value = 'wrGoxbgFD4BO437vs+f5rP4fY53yRyn+' where id = 5 ; We retry to add a new host and it works. Regards > Add new host into VMWare Cluster failed > --- > > Key: CLOUDSTACK-2860 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2860 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault > -- 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
[jira] [Created] (CLOUDSTACK-2860) Add new host into VMWare Cluster failed
Nicolas Lamirault created CLOUDSTACK-2860: - Summary: Add new host into VMWare Cluster failed Key: CLOUDSTACK-2860 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2860 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Nicolas Lamirault -- 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
[jira] [Commented] (CLOUDSTACK-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673144#comment-13673144 ] Nicolas Lamirault commented on CLOUDSTACK-2822: --- i try both systemvm-vmware-3.0.5 and systemvm-vmware-4.0 . > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached 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
[jira] [Commented] (CLOUDSTACK-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673116#comment-13673116 ] Nicolas Lamirault commented on CLOUDSTACK-2822: --- The SQL request comes from file : ./server/src/com/cloud/upgrade/dao/Upgrade30xBase.java > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached 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
[jira] [Updated] (CLOUDSTACK-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2822: -- Attachment: output.log > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2822 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > Attachments: output.log > > > We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. > See attached 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
[jira] [Created] (CLOUDSTACK-2822) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
Nicolas Lamirault created CLOUDSTACK-2822: - Summary: Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade Key: CLOUDSTACK-2822 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2822 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Nicolas Lamirault Priority: Blocker Fix For: 4.1.0 We can't upgrade from 2.2.14 to 4.1.0 due to error during database migration. See attached 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
[jira] [Commented] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found (configuration : advanced network with security groups)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658179#comment-13658179
]
Nicolas Lamirault commented on CLOUDSTACK-2463:
---
I don't understand how this bug is fixed ?
> CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found
> (configuration : advanced network with security groups)
>
>
> Key: CLOUDSTACK-2463
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2463
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0
>Reporter: Nicolas Lamirault
>Assignee: Brian Federle
>Priority: Blocker
> Fix For: 4.1.0
>
>
> According Wei Zhou last patch
> (https://issues.apache.org/jira/browse/CLOUDSTACK-528), i can add a new
> secondary storage. The SSVM creation failed due to :
> 2013-05-13 15:17:52,868 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-05-13 15:17:52,879 INFO
> [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) No
> running secondary storage vms found in datacenter id=1, starting one
> 2013-05-13 15:17:52,889 INFO [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) No stopped secondary storage vm is available, need to
> allocate a new secondary storage vm
> 2013-05-13 15:17:52,894 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Assign secondary storage vm from a newly started instance
> for request from data center : 1
> 2013-05-13 15:17:52,922 WARN [cloud.vm.SystemVmLoadScanner]
> (secstorage-1:null) Unexpected exception Found 22 networks of type Guest when
> expect to find 1
> com.cloud.utils.exception.CloudRuntimeException: Found 22 networks of type
> Guest when expect to find 1
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStorageVmInstance(SecondaryStorageManagerImpl.java:552)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(SecondaryStorageManagerImpl.java:499)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:666)
> at
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300)
> at
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:121)
> at
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:52)
> at
> com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104)
> at
> com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
> at
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
> at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> We try this patch :
> diff --git
> a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> index fca89dc..d40d22f 100755
> --- a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> +++ b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
> @@ -541,7 +541,7 @@ public class SecondaryStorageManagerImpl extends
> ManagerBase implements Secondar
> DataCenter dc = _dcDao.findById(plan.getDataCenterId());
> TrafficType defaultTrafficType = TrafficType.Public;
> - if (dc.getNetworkType() == NetworkType.Basic ||
> dc.isSecurityGroupEnabled()) {
> + if (dc.getNetworkType() == NetworkType.Basic) {
> defaultTrafficType = TrafficType.Gu
[jira] [Created] (CLOUDSTACK-2463) CS Upgrade 2.2.14 to 4.1.0 failed due to no public network found (configuration : advanced network with security groups)
Nicolas Lamirault created CLOUDSTACK-2463:
-
Summary: CS Upgrade 2.2.14 to 4.1.0 failed due to no public
network found (configuration : advanced network with security groups)
Key: CLOUDSTACK-2463
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2463
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.1.0
Reporter: Nicolas Lamirault
Priority: Blocker
Fix For: 4.1.0
According Wei Zhou last patch
(https://issues.apache.org/jira/browse/CLOUDSTACK-528), i can add a new
secondary storage. The SSVM creation failed due to :
2013-05-13 15:17:52,868 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-05-13 15:17:52,879 INFO
[cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) No
running secondary storage vms found in datacenter id=1, starting one
2013-05-13 15:17:52,889 INFO [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) No stopped secondary storage vm is available, need to
allocate a new secondary storage vm
2013-05-13 15:17:52,894 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Assign secondary storage vm from a newly started instance
for request from data center : 1
2013-05-13 15:17:52,922 WARN [cloud.vm.SystemVmLoadScanner] (secstorage-1:null)
Unexpected exception Found 22 networks of type Guest when expect to find 1
com.cloud.utils.exception.CloudRuntimeException: Found 22 networks of type
Guest when expect to find 1
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStorageVmInstance(SecondaryStorageManagerImpl.java:552)
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(SecondaryStorageManagerImpl.java:499)
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:666)
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300)
at
com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:121)
at
com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:52)
at
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104)
at
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
We try this patch :
diff --git
a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
index fca89dc..d40d22f 100755
--- a/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
+++ b/server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java
@@ -541,7 +541,7 @@ public class SecondaryStorageManagerImpl extends
ManagerBase implements Secondar
DataCenter dc = _dcDao.findById(plan.getDataCenterId());
TrafficType defaultTrafficType = TrafficType.Public;
- if (dc.getNetworkType() == NetworkType.Basic || dc.isSecurityGroupEnabled())
{
+ if (dc.getNetworkType() == NetworkType.Basic) {
defaultTrafficType = TrafficType.Guest;
}
@@ -1143,7 +1143,7 @@ public class SecondaryStorageManagerImpl extends
ManagerBase implements Secondar
List nics = profile.getNics();
for (NicProfile nic : nics) {
if ((nic.getTrafficType() == TrafficType.Public &&
dc.getNetworkType() == NetworkType.Advanced)
- || (nic.getTrafficType() == TrafficType.Guest && (dc.getNetworkType() ==
NetworkType.Basic || dc.isSecurityGroupEnabled( {
+ || (nic.getTrafficType() == TrafficType.Guest && (dc.getNetworkType() ==
NetworkType.Basi
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656028#comment-13656028 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- In our CS 2.2.13, we've got this configuration : select distinct(traffic_type) from networks where data_center_id = 1 and state <> 'DESTROY'; +--+ | traffic_type | +--+ | Management | | Control | | Storage | | Guest| +--+ select count(*) as nb, traffic_type from networks where data_center_id = 1 group by traffic_type; +-+--+ | nb | traffic_type | +-+--+ | 1 | Control | | 362 | Guest| | 1 | Management | | 1 | Storage | +-+--+ > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0, 4.1.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.1.0 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID matches but A
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656020#comment-13656020 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- With the last patch : 2013-05-13 16:56:27,084 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) No stopped secondary storage vm is available, need to allocate a new secondary storage vm 2013-05-13 16:56:27,090 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Assign secondary storage vm from a newly started instance for request from data center : 1 2013-05-13 16:56:27,126 WARN [cloud.vm.SystemVmLoadScanner] (secstorage-1:null) Unexpected exception Found 0 networks of type Public when expect to find 1 com.cloud.utils.exception.CloudRuntimeException: Found 0 networks of type Public when expect to find 1 at com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStorageVmInstance(SecondaryStorageManagerImpl.java:555) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(SecondaryStorageManagerImpl.java:499) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:669) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1304) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:121) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:52) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Into database : select distinct(traffic_type) from networks where data_center_id = 1 and state <> 'DESTROY'; +--+ | traffic_type | +--+ | Management | | Control | | Storage | | Guest| +--+ select count(*) as nb, traffic_type from networks where data_center_id = 1 group by traffic_type; ++--+ | nb | traffic_type | ++--+ | 1 | Control | | 25 | Guest| | 1 | Management | | 1 | Storage | ++--+ > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0, 4.1.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.1.0 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655997#comment-13655997 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- hi we are in Advanced and Security Group enabled. > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0, 4.1.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.1.0 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID matches but API throws exception while the IS is supplied in the > query. > Scenario: > I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not > update the systemVMs to the new template I've applied a workaround and > recreated the systemVMs with the new templates. After that I've enabled > storage clean-up and the cleanup script destroyed everything on my primary > storage including systemVMs. I wanted to re-create them but cannot add > secondary storage to the Zone. > The applied workarounds during
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655952#comment-13655952 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- Hi, @weizhou, thanks for you comment. We had in database 'HIDDEN ' and not 'HIDDEN'. So we had update the database, and now management server try to create SSVM : 2013-05-13 15:17:52,868 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM 2013-05-13 15:17:52,879 INFO [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:null) No running secondary storage vms found in datacenter id=1, starting one 2013-05-13 15:17:52,889 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) No stopped secondary storage vm is available, need to allocate a new secondary storage vm 2013-05-13 15:17:52,894 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Assign secondary storage vm from a newly started instance for request from data center : 1 2013-05-13 15:17:52,922 WARN [cloud.vm.SystemVmLoadScanner] (secstorage-1:null) Unexpected exception Found 22 networks of type Guest when expect to find 1 com.cloud.utils.exception.CloudRuntimeException: Found 22 networks of type Guest when expect to find 1 at com.cloud.storage.secondary.SecondaryStorageManagerImpl.createSecStorageVmInstance(SecondaryStorageManagerImpl.java:552) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startNew(SecondaryStorageManagerImpl.java:499) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:666) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:121) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:52) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0, 4.1.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.1.0 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) >
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655881#comment-13655881
]
Nicolas Lamirault commented on CLOUDSTACK-528:
--
I change code like this :
git diff server/src/com/cloud/storage/secondary/SecondaryStorageDiscoverer.java
diff --git
a/server/src/com/cloud/storage/secondary/SecondaryStorageDiscoverer.java
b/server/src/com/cloud/storage/secondary/SecondaryStorageDiscoverer.java
index 3ca74a3..9e219bb 100755
--- a/server/src/com/cloud/storage/secondary/SecondaryStorageDiscoverer.java
+++ b/server/src/com/cloud/storage/secondary/SecondaryStorageDiscoverer.java
@@ -92,8 +92,9 @@ public class SecondaryStorageDiscoverer extends
DiscovererBase implements Discov
s_logger.debug("It's not NFS or file or ISO, so not a secondary
storage server: " + uri.toString());
return null;
}
-
+s_logger.info("URI Scheme: " + uri.getScheme());
if (uri.getScheme().equalsIgnoreCase("nfs") ||
uri.getScheme().equalsIgnoreCase("iso")) {
+s_logger.info("NFS Secondary Storage find");
return createNfsSecondaryStorageResource(dcId, podId, uri);
} else if (uri.getScheme().equalsIgnoreCase("file")) {
return createLocalSecondaryStorageResource(dcId, podId, uri);
@@ -105,7 +106,11 @@ public class SecondaryStorageDiscoverer extends
DiscovererBase implements Discov
}
protected Map>
createNfsSecondaryStorageResource(long dcId, Long podId, URI uri) {
-
+
+s_logger.info("userServiceVM : " + _useServiceVM);
+if (!_useServiceVM) {
+_useServiceVM = true;
+}
if (_useServiceVM) {
return createDummySecondaryStorageResource(dcId, podId, uri);
}
In logs :
2013-05-13 11:52:12,913 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor17:null) Trying to add a new host at
nfs://rr.isia.boi.cloud.mbs/ifs/cloud/chevilly/clustervmw-prp/secondarystorage
in data center 1
2013-05-13 11:52:12,913 INFO [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor17:null) URI Scheme: nfs
2013-05-13 11:52:12,913 INFO [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor17:null) NFS Secondary Storage find
2013-05-13 11:52:12,913 INFO [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor17:null) userServiceVM : false
2013-05-13 11:52:12,920 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Retrieving network interface: xenbr0
2013-05-13 11:52:12,920 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Unable to get network interface for xenbr0
2013-05-13 11:52:12,920 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Retrieving network interface: xenbr1
2013-05-13 11:52:12,921 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Unable to get network interface for xenbr1
2013-05-13 11:52:12,921 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Retrieving network interface: null
2013-05-13 11:52:12,921 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Retrieving network interface: null
2013-05-13 11:52:12,921 ERROR [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Nics are not configured!
2013-05-13 11:52:12,922 INFO [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Designating private to be nic eth0
2013-05-13 11:52:12,923 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor17:null) Find resource Storage
2013-05-13 11:52:12,924 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Parameters for private nic: 10.200.194.26 -
00:50:56:a9:50:b6-255.255.254.0
2013-05-13 11:52:12,924 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor17:null) Parameters for storage nic: 10.200.194.26 -
00:50:56:a9:50:b6-255.255.254.0
2013-05-13 11:52:12,931 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor17:null) Startup cmds : 1
2013-05-13 11:52:12,931 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor17:null) Cmd: StartupCommand{type=Storage, dataCenter='1',
pod='null', cluster='null', guid='nfs://rr.isia.boi.cloud.mbs/ifs/cloud/ch
evilly/clustervmw-prp/secondarystorage',
name='nfs://rr.isia.boi.cloud.mbs/ifs/cloud/chevilly/clustervmw-prp/secondarystorage',
id=null, version='4.1.0', iqn='null', publicIpAddress='null',
publicNetmask='null', p
ublicMacAddress='null', privateIpAddress='nfs',
privateMacAddress='00:50:56:a9:50:b6', privateNetmask='255.255.254.0',
storageIpAddress='10.200.194.26', storageNetmask='255.255.254.0',
storageMacAddress='00:50:56:
a9:50:b6', storageIpAddressDeux='null', storageMacAddressDeux='null',
storageNetmaskDeux='null', agentTag='null', resourceName='null',
gatewayIpAddress='null'}
2013-05-13 11:52:12,934 DEBUG [agent.transport.Request] (TP-Processor17:null)
Seq -1--1: Startup request from directly connected host: { Cmd , MgmtId: -1,
via: -1,
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655850#comment-13655850
]
Nicolas Lamirault commented on CLOUDSTACK-528:
--
Hi,
it seems, value in configuration table are already encrypted :
select * from configuration where name = 'secondary.storage.vm' ;
+--+--+---+--+--++
| category | instance | component | name | value
| description
|
+--+--+---+--+--++
| Hidden | DEFAULT | management-server | secondary.storage.vm |
c5j1YtdWPXA2NTcyWEkJwg== | Deploys a VM per zone to manage secondary storage if
true, otherwise secondary storage is mounted on management server |
+--+--+---+--+--++
$> java -classpath /usr/share/java/jasypt-1.9.0.jar
org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI decrypt.sh
input="c5j1YtdWPXA2NTcyWEkJwg==" password=cloudstackprp verbose=false
true
select * from configuration where name = 'security.hash.key' ;
+--+--+---+---+--+-+
| category | instance | component | name | value
| description |
+--+--+---+---+--+-+
| Hidden | DEFAULT | management-server | security.hash.key |
LhnMbg0+2YuuYqwGiKab+VC8oehnKRwcRJ7hojDVdq6vsANs+S+TPd7yymWIcX6n | for generic
key-ed hash |
+--+--+---+---+--+-+
$> java -classpath /usr/share/java/jasypt-1.9.0.jar
org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI decrypt.sh
input="LhnMbg0+2YuuYqwGiKab+VC8oehnKRwcRJ7hojDVdq6vsANs+S+TPd7yymWIcX6n"
password=cloudstackprp verbose=false
0b873a52-5abb-451a-af62-114e98a0f73f
select * from configuration where name = 'router.ram.size' ;
+--+--++-+--++
| category | instance | component | name| value
| description|
+--+--++-+--++
| Hidden | DEFAULT | NetworkManager | router.ram.size |
KNXD3Y9CDuSiyCiWOUJDVQ== | Default RAM for router VM (in MB). |
+--+--++-+--++
$> java -classpath /usr/share/java/jasypt-1.9.0.jar
org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI decrypt.sh
input="KNXD3Y9CDuSiyCiWOUJDVQ==" password=cloudstackprp verbose=false
128
@edison, so 'secondary.storage.vm' is set to true in database. But according to
the logs, management server loads NfsSecondaryStorageResource.
2013-05-13 10:44:09,569 INFO [storage.resource.NfsSecondaryStorageResource]
(TP-Processor17:null) Cmd ajoute : StartupCommand{type=SecondaryStorage,
dataCenter='1', pod='null', cluster='null', guid='nfs://rr.isia
.boi.cloud.mbs/ifs/cloud/chevilly/clustervmw-prp/secondarystorage',
name='nfs://rr.isia.boi.cloud.mbs/ifs/cloud/chevilly/clustervmw-prp/secondarystorage',
id=null, version='4.1.0', iqn='NoIqn', publicIpAddress='nu
ll', publicNetmask='null', publicMacAddress='null',
privateIpAddress='10.200.194.26', privateMacAddress='00:50:56:a9:50:b6',
privateNetmask='255.255.254.0', storageIpAddress='10.200.194.26',
storageNetmask='255.25
5.254.0', storageMacAddress='00:50:56:a9:50:b6', storageIpAddressDeux='null',
storageMacAddressDeux='null', storageNetmaskDeux='null', agentTag='null',
resourceName='null', gatewayIpAddress='null'}
2013-05-13 10:44:09,569
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648493#comment-13648493
]
Nicolas Lamirault commented on CLOUDSTACK-528:
--
there is no "resource state adapter response", due to
createHostVOForDirectConnectAgent method in createHostVOForDirectConnectAgent.
name of the command must be fix perhaps :
Cmd: StartupCommand{type=SecondaryStorage, dataCenter='1', pod='null',
cluster='null', guid='nfs://xx/
/secondarystorage',
name='nfs://xxx/secondarystorage', id=null,
version='4.1.0', iqn='NoIqn', publicIpAddress='null', publicNetmask
='null', publicMacAddress='null', privateIpAddress='10.200.194.26',
privateMacAddress='00:50:56:a9:50:b6', privateNetmask='255.255.254.0',
storageIpAddress='10.200.194.26', storageNetmask='255.255.254.0', storageM
acAddress='00:50:56:a9:50:b6', storageIpAddressDeux='null',
storageMacAddressDeux='null', storageNetmaskDeux='null', agentTag='null',
resourceName='null', gatewayIpAddress='null'}
> Failed to create secondary storage
> --
>
> Key: CLOUDSTACK-528
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.0.0, 4.1.0
> Environment: CentOS
>Reporter: Tamas Monos
>Priority: Blocker
> Fix For: 4.1.0
>
>
> Hi,
> I cannot add secondary storage to my existing Zone. This prevents the
> platform from operating.
> API call via GUI captured by tcpdump:
> http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114
> Result:
> Unable to connect due to
> java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data
> center: null
> at
> com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501)
> at
> com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720)
> at
> com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551)
> at
> com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> at
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl]
> (catalina-exec-23:null) server resources successfully discovered by
> SecondaryStorage
> 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher]
> (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to
> add secondary storage
> Debug:
> mysql> select uuid from d
[jira] [Updated] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-528: - Fix Version/s: 4.0.2 > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0, 4.1.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.0.2, 4.1.0 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID matches but API throws exception while the IS is supplied in the > query. > Scenario: > I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not > update the systemVMs to the new template I've applied a workaround and > recreated the systemVMs with the new templates. After that I've enabled > storage clean-up and the cleanup script destroyed everything on my primary > storage including systemVMs. I wanted to re-create them but cannot add > secondary storage to the Zone. > The applied workarounds during upgrade: > 1. Add new vmware template to CS with name systemvm-vmware-4.0 (I have > re-imported
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648430#comment-13648430
]
Nicolas Lamirault commented on CLOUDSTACK-528:
--
With some logs, it seems datacenter is find :
2013-05-03 15:10:21,707 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor21:null) Search zone : 1
2013-05-03 15:10:21,707 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor21:null) Find zone 1 CloudMBS_PRP
2013-05-03 15:10:21,708 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor21:null) Trying to add a new host at
nfs:///xxp/secondarystorage in data center 1
2013-05-03 15:10:21,709 DEBUG [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor21:null) Executing: sudo mount x:/xx/secondarystorage
/mnt/cloudstack/73f30888
2013-05-03 15:10:22,245 DEBUG [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor21:null) Execution is successful.
2013-05-03 15:10:22,246 DEBUG [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor21:null) Executing: sudo umount /mnt/cloudstack/73f30888
2013-05-03 15:10:22,329 DEBUG [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor21:null) Execution is successful.
2013-05-03 15:10:22,351 WARN [storage.resource.NfsSecondaryStorageResource]
(TP-Processor21:null) Wait, what's going on? eth1ip is null!!
2013-05-03 15:10:22,351 WARN [storage.resource.NfsSecondaryStorageResource]
(TP-Processor21:null) Wait, there is no storageip in /proc/cmdline, something
wrong!
but when StartCommand is created, data is empty :
StartupCommand{type=SecondaryStorage, dataCenter='null', pod='null',
cluster='null', guid='null', name='null', id=null, version='null', iqn='NoIqn',
publicIpAddress='null', publicNetmask='null', publicMacAddress='null',
privateIpAddress='10.200.194.26', privateMacAddress='00:50:56:a9:50:b6',
privateNetmask='255.255.254.0', storageIpAddress='10.200.194.26',
storageNetmask='255.255.254.0', storageMacAddress='00:50:56:a9:50:b6',
storageIpAddressDeux='null', storageMacAddressDeux='null',
storageNetmaskDeux='null', agentTag='null', resourceName='null',
gatewayIpAddress='null'}
I try that in NfsSecondaryStorageResource :
@Override
public StartupCommand[] initialize() {
final StartupSecondaryStorageCommand cmd = new
StartupSecondaryStorageCommand();
fillNetworkInformation(cmd);
cmd.setDataCenter(_dc);
cmd.setPod(_pod);
cmd.setGuid(_guid);
cmd.setName(_guid);
cmd.setVersion(NfsSecondaryStorageResource.class.getPackage().getImplementationVersion());
s_logger.info("Cmd ajoute : " + cmd.describe());
...
}
but now the error is :
2013-05-03 15:59:10,034 INFO [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Cmd ajoute : StartupCommand{type=SecondaryStorage,
dataCenter='1', pod='null', cluster='null',
guid='nfs://xx/secondarystorage',
name='nfs://xxx/secondarystorage', id=null, version='4.1.0',
iqn='NoIqn', publicIpAddress='nu
ll', publicNetmask='null', publicMacAddress='null',
privateIpAddress='10.200.194.26', privateMacAddress='00:50:56:a9:50:b6',
privateNetmask='255.255.254.0', storageIpAddress='10.200.194.26',
storageNetmask='255.25
5.254.0', storageMacAddress='00:50:56:a9:50:b6', storageIpAddressDeux='null',
storageMacAddressDeux='null', storageNetmaskDeux='null', agentTag='null',
resourceName='null', gatewayIpAddress='null'}
2013-05-03 15:59:10,034 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Executing: /bin/bash -c ln -sf /mnt/SecStorage
/var/www/html/copy
2013-05-03 15:59:10,038 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Execution is successful.
2013-05-03 15:59:10,039 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Startup cmds : 1
2013-05-03 15:59:10,039 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Cmd: StartupCommand{type=SecondaryStorage,
dataCenter='1', pod='null', cluster='null', guid='nfs://xx/
/secondarystorage',
name='nfs://xxx/secondarystorage', id=null,
version='4.1.0', iqn='NoIqn', publicIpAddress='null', publicNetmask
='null', publicMacAddress='null', privateIpAddress='10.200.194.26',
privateMacAddress='00:50:56:a9:50:b6', privateNetmask='255.255.254.0',
storageIpAddress='10.200.194.26', storageNetmask='255.255.254.0', storageM
acAddress='00:50:56:a9:50:b6', storageIpAddressDeux='null',
storageMacAddressDeux='null', storageNetmaskDeux='null', agentTag='null',
resourceName='null', gatewayIpAddress='null'}
2013-05-03 15:59:10,040 DEBUG [agent.transport.Request] (TP-Processor18:null)
Seq -1--1: Startup request from directly connected host: { Cmd , MgmtId: -1,
via: -1, Ver: v1, Flags: 111, [{"type":"SecondaryStorage"
,"dataCenter":"1","guid":"nfs://xxxp/secondarystorage","n
[jira] [Comment Edited] (CLOUDSTACK-528) Failed to create secondary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648359#comment-13648359
]
Nicolas Lamirault edited comment on CLOUDSTACK-528 at 5/3/13 12:36 PM:
---
I add some logs :
2013-05-03 13:58:51,752 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Trying to add a new host at
nfs://x/secondarystorage in data center 1
2013-05-03 13:58:51,753 DEBUG [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor18:null) Executing: sudo mount rxx:/xxx/secondarystorage
/mnt/cloudstack/7e
fdc0d
2013-05-03 13:58:52,273 DEBUG [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor18:null) Execution is successful.
2013-05-03 13:58:52,274 DEBUG [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor18:null) Executing: sudo umount /mnt/cloudstack/7efdc0d
2013-05-03 13:58:52,341 DEBUG [storage.secondary.SecondaryStorageDiscoverer]
(TP-Processor18:null) Execution is successful.
2013-05-03 13:58:52,363 WARN [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Wait, what's going on? eth1ip is null!!
2013-05-03 13:58:52,363 WARN [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Wait, there is no storageip in /proc/cmdline, something
wrong!
2013-05-03 13:58:52,364 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor18:null) Retrieving network interface: xenbr0
2013-05-03 13:58:52,364 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor18:null) Unable to get network interface for xenbr0
2013-05-03 13:58:52,364 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor18:null) Retrieving network interface: xenbr1
2013-05-03 13:58:52,364 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor18:null) Unable to get network interface for xenbr1
2013-05-03 13:58:52,364 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor18:null) Retrieving network interface: null
2013-05-03 13:58:52,364 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor18:null) Retrieving network interface: null
2013-05-03 13:58:52,364 ERROR [cloud.resource.ServerResourceBase]
(TP-Processor18:null) Nics are not configured!
2013-05-03 13:58:52,366 INFO [cloud.resource.ServerResourceBase]
(TP-Processor18:null) Designating private to be nic eth0
2013-05-03 13:58:52,409 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Executing: /bin/bash -c ln -sf /mnt/SecStorage
/var/www/html/copy
2013-05-03 13:58:52,472 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Execution is successful.
2013-05-03 13:58:52,472 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Startup cmds : 1
2013-05-03 13:58:52,472 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Cmd: StartupCommand{type=SecondaryStorage,
dataCenter='null', pod='null', cluster='null', guid='null', name='null',
id=null,
version='null', iqn='NoIqn', publicIpAddress='null', publicNetmask='null',
publicMacAddress='null', privateIpAddress='10.200.194.26',
privateMacAddress='00:50:56:a9:50:b6', privateNetmask='255.255.254.0', storage
IpAddress='10.200.194.26', storageNetmask='255.255.254.0',
storageMacAddress='00:50:56:a9:50:b6', storageIpAddressDeux='null',
storageMacAddressDeux='null', storageNetmaskDeux='null', agentTag='null',
resourceName
='null', gatewayIpAddress='null'}
2013-05-03 13:58:52,473 DEBUG [agent.transport.Request] (TP-Processor18:null)
Seq -1--1: Startup request from directly connected host: { Cmd , MgmtId: -1,
via: -1, Ver: v1, Flags: 111, [{"type":"SecondaryStorage"
,"iqn":"NoIqn","privateIpAddress":"10.200.194.26","privateMacAddress":"00:50:56:a9:50:b6","privateNetmask":"255.255.254.0","storageIpAddress":"10.200.194.26","storageNetmask":"255.255.254.0","storageMacAddress":"0
0:50:56:a9:50:b6","wait":0}] }
2013-05-03 13:58:52,480 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Create cmd
com.cloud.agent.api.StartupSecondaryStorageCommand
2013-05-03 13:58:52,492 WARN [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Unable to connect due to
java.lang.IllegalArgumentException: Host 10.200.194.26 sent incorrect data
center: null
at
com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1767)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1947)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:848)
at
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:628)
at
org.apache.cloudstack.api.command.admin.host.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:80)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:509)
at com.cloud.api.ApiServer.handleRequest(
[jira] [Comment Edited] (CLOUDSTACK-528) Failed to create secondary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648359#comment-13648359
]
Nicolas Lamirault edited comment on CLOUDSTACK-528 at 5/3/13 12:32 PM:
---
I add some logs :
2013-05-03 13:58:51,752 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Trying to add a new host at
nfs://x/secondarystorage in data center 1
2013-05-03 13:58:52,409 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Executing: /bin/bash -c ln -sf /mnt/SecStorage
/var/www/html/copy
2013-05-03 13:58:52,472 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Execution is successful.
2013-05-03 13:58:52,472 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Startup cmds : 1
2013-05-03 13:58:52,472 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Cmd: StartupCommand{type=SecondaryStorage,
dataCenter='null', pod='null', cluster='null', guid='null', name='null',
id=null,
version='null', iqn='NoIqn', publicIpAddress='null', publicNetmask='null',
publicMacAddress='null', privateIpAddress='10.200.194.26',
privateMacAddress='00:50:56:a9:50:b6', privateNetmask='255.255.254.0', storage
IpAddress='10.200.194.26', storageNetmask='255.255.254.0',
storageMacAddress='00:50:56:a9:50:b6', storageIpAddressDeux='null',
storageMacAddressDeux='null', storageNetmaskDeux='null', agentTag='null',
resourceName
='null', gatewayIpAddress='null'}
2013-05-03 13:58:52,473 DEBUG [agent.transport.Request] (TP-Processor18:null)
Seq -1--1: Startup request from directly connected host: { Cmd , MgmtId: -1,
via: -1, Ver: v1, Flags: 111, [{"type":"SecondaryStorage"
,"iqn":"NoIqn","privateIpAddress":"10.200.194.26","privateMacAddress":"00:50:56:a9:50:b6","privateNetmask":"255.255.254.0","storageIpAddress":"10.200.194.26","storageNetmask":"255.255.254.0","storageMacAddress":"0
0:50:56:a9:50:b6","wait":0}] }
2013-05-03 13:58:52,480 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Create cmd
com.cloud.agent.api.StartupSecondaryStorageCommand
2013-05-03 13:58:52,492 WARN [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Unable to connect due to
java.lang.IllegalArgumentException: Host 10.200.194.26 sent incorrect data
center: null
at
com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1767)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1947)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:848)
at
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:628)
at
org.apache.cloudstack.api.command.admin.host.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:80)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:509)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:359)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:315)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
in the api.log file :
GET
command=addSecondaryStorage&zoneId=dda44dc5-1084-442a-b946-00c66387a45a&url=nfs%3A%2F%2Frr.xx%2FifsxxFsecondarystorage&response=json&sessionkey=b2ORpgifHR1biF2EqFGYBiSHsN8%3D&_=1367582345384
530 Failed to add secondary storage
in the database :
select id from data_center where uuid = 'dda44dc5-1084-442a-b946-00c66387a45a' ;
++
| id |
++
| 1 |
++
It seems CS doesn't find the Zone using the uuid (from the api command).
was (Author: nlamirault):
I add some logs :
2013-05-03 13:58:52,409 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Executing: /bin/bash -c ln -sf /mnt/SecStorage
/var/www/html/copy
2013-05-03 13:58:52,472 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Execution is successful.
2013-05-03 13:58:52,472 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Startup cmds : 1
2013-05-03 13:58:52,472 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Cmd: StartupCommand{type=SecondaryStorage,
dataCenter='nu
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648359#comment-13648359
]
Nicolas Lamirault commented on CLOUDSTACK-528:
--
I add some logs :
2013-05-03 13:58:52,409 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Executing: /bin/bash -c ln -sf /mnt/SecStorage
/var/www/html/copy
2013-05-03 13:58:52,472 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor18:null) Execution is successful.
2013-05-03 13:58:52,472 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Startup cmds : 1
2013-05-03 13:58:52,472 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Cmd: StartupCommand{type=SecondaryStorage,
dataCenter='null', pod='null', cluster='null', guid='null', name='null',
id=null,
version='null', iqn='NoIqn', publicIpAddress='null', publicNetmask='null',
publicMacAddress='null', privateIpAddress='10.200.194.26',
privateMacAddress='00:50:56:a9:50:b6', privateNetmask='255.255.254.0', storage
IpAddress='10.200.194.26', storageNetmask='255.255.254.0',
storageMacAddress='00:50:56:a9:50:b6', storageIpAddressDeux='null',
storageMacAddressDeux='null', storageNetmaskDeux='null', agentTag='null',
resourceName
='null', gatewayIpAddress='null'}
2013-05-03 13:58:52,473 DEBUG [agent.transport.Request] (TP-Processor18:null)
Seq -1--1: Startup request from directly connected host: { Cmd , MgmtId: -1,
via: -1, Ver: v1, Flags: 111, [{"type":"SecondaryStorage"
,"iqn":"NoIqn","privateIpAddress":"10.200.194.26","privateMacAddress":"00:50:56:a9:50:b6","privateNetmask":"255.255.254.0","storageIpAddress":"10.200.194.26","storageNetmask":"255.255.254.0","storageMacAddress":"0
0:50:56:a9:50:b6","wait":0}] }
2013-05-03 13:58:52,480 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Create cmd
com.cloud.agent.api.StartupSecondaryStorageCommand
2013-05-03 13:58:52,492 WARN [cloud.resource.ResourceManagerImpl]
(TP-Processor18:null) Unable to connect due to
java.lang.IllegalArgumentException: Host 10.200.194.26 sent incorrect data
center: null
at
com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1767)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1947)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:848)
at
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:628)
at
org.apache.cloudstack.api.command.admin.host.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:80)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:509)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:359)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:315)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
in the api.log file :
GET
command=addSecondaryStorage&zoneId=dda44dc5-1084-442a-b946-00c66387a45a&url=nfs%3A%2F%2Frr.xx%2FifsxxFsecondarystorage&response=json&sessionkey=b2ORpgifHR1biF2EqFGYBiSHsN8%3D&_=1367582345384
530 Failed to add secondary storage
in the database :
select id from data_center where uuid = 'dda44dc5-1084-442a-b946-00c66387a45a' ;
++
| id |
++
| 1 |
++
It seems CS doesn't find the Zone using the uuid (from the api command).
> Failed to create secondary storage
> --
>
> Key: CLOUDSTACK-528
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.0.0
> Environment: CentOS
>Reporter: Tamas Monos
>Priority: Blocker
> Fix For: 4.0.2
>
>
> Hi,
> I cannot add secondary storage to my existing Zone. This prevents the
> platform from operating.
> API call via GUI captured by tcpdump:
> http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648280#comment-13648280 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- We did that too. Currently we have no more SSVM and we can not add any secondary storage. > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.0.2 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID matches but API throws exception while the IS is supplied in the > query. > Scenario: > I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not > update the systemVMs to the new template I've applied a workaround and > recreated the systemVMs with the new templates. After that I've enabled > storage clean-up and the cleanup script destroyed everything on my primary > storage including systemVMs. I wanted to re-create them but cannot add > secondary storage to the Zone. > The ap
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648260#comment-13648260 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- Hi, Our upgrade from 2.2.14 to 4.1.0 works using a systemvm-vmware-3.0.0 (and not like documentation says "systemvm-vmware-3.0.5" or "systemvm-vmware-4.0.0"). [https://issues.apache.org/jira/browse/CLOUDSTACK-2207] Before upgrade, we have added a new template system using CS 2.2.14. After update, that we have rebooted SSVM from CS 4.1.0 UI, and all network static routes disapeared in the SSCM (https://issues.apache.org/jira/browse/CLOUDSTACK-2309) So we have destroyed the SSVM and CPVM, and the secondary storage. Then, we have tried to add the same secondary storage. And it fails. > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.0.2 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID mat
[jira] [Commented] (CLOUDSTACK-2309) Upgrade from 2.2.14 to 4.1.0 : network static routes deleted on SSVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648237#comment-13648237 ] Nicolas Lamirault commented on CLOUDSTACK-2309: --- We have destroyed the SSVM and CPVM Then try to add a new secondary storage, and we have this error : https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Upgrade from 2.2.14 to 4.1.0 : network static routes deleted on SSVM > > > Key: CLOUDSTACK-2309 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2309 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > > After upgrading from 2.2.14 to 4.1.0, we have rebooted the SSVM. After that, > all network static routes disapeared. > This static routes was added by CS on 2.2.14 dynamically. -- 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
[jira] [Reopened] (CLOUDSTACK-528) Failed to create secondary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lamirault reopened CLOUDSTACK-528:
--
We try to upgrade from 2.2.14 to 4.1.0.
After having destroyed the SSVM and secondary storage (due to this bug
https://issues.apache.org/jira/browse/CLOUDSTACK-2309), we add a new secondary
storage.
2013-05-03 08:49:06,017 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor15:null) Parameters for private nic: 10.200.194.26 -
00:50:56:a9:50:b6-255.255.254.0
2013-05-03 08:49:06,017 DEBUG [cloud.resource.ServerResourceBase]
(TP-Processor15:null) Parameters for storage nic: 10.200.194.26 -
00:50:56:a9:50:b6-255.255.254.0
2013-05-03 08:49:06,017 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor15:null) Executing: /bin/bash -c ln -sf /mnt/SecStorage
/var/www/html/copy
2013-05-03 08:49:06,021 DEBUG [storage.resource.NfsSecondaryStorageResource]
(TP-Processor15:null) Execution is successful.
2013-05-03 08:49:06,024 DEBUG [agent.transport.Request] (TP-Processor15:null)
Seq -1--1: Startup request from directly connected host: { Cmd , MgmtId: -1,
via: -1, Ver: v1, Flags: 111,
[{"type":"SecondaryStorage","iqn":"NoIqn","privateIpAddress":"10.200.194.26","privateMacAddress":"00:50:56:a9:50:b6","privateNetmask":"255.255.254.0","storageIpAddress":"10.200.194.26","storageNetmask":"255.255.254.0","storageMacAddress":"00:50:56:a9:50:b6","wait":0}]
}
2013-05-03 08:49:06,040 WARN [cloud.resource.ResourceManagerImpl]
(TP-Processor15:null) Unable to connect due to
java.lang.IllegalArgumentException: Host 10.200.194.26 sent incorrect data
center: null
at
com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1765)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1940)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847)
at
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:628)
at
org.apache.cloudstack.api.command.admin.host.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:80)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:509)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:359)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:315)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:776)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:705)
at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:898)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:662)
2013-05-03 08:49:06,047 INFO [cloud.resource.ResourceManagerImpl]
(TP-Processor15:null) server resources successfully discovered by
SecondaryStorage
2013-05-03 08:49:06,047 INFO [cloud.api.ApiServer] (TP-Processor15:null)
Failed to add secondary storage
This bug is also in CS 4.1.0.
> Failed to create secondary storage
> --
>
> Key: CLOUDSTACK-528
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.0.0
> Environment: CentOS
>Reporter: Tamas Monos
>Priority: Blocker
> Fix For: 4.0.2
>
>
> Hi,
> I cannot add secondary storage to my existing Zone. This prevents the
> platform from operating.
> API
[jira] [Commented] (CLOUDSTACK-2302) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647677#comment-13647677 ] Nicolas Lamirault commented on CLOUDSTACK-2302: --- Can be closed. Duplicate of : https://issues.apache.org/jira/browse/CLOUDSTACK-2207 > Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade > --- > > Key: CLOUDSTACK-2302 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2302 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > > I try to upgrade from 2.2.14 to 4.1.0 > INFO: Initializing log4j from [classpath:log4j-cloud.xml] > May 2, 2013 10:05:45 AM org.apache.catalina.core.ApplicationContext log > INFO: Initializing Spring root WebApplicationContext > INFO [web.context.ContextLoader] (main:) Root WebApplicationContext: > initialization started > INFO [context.support.XmlWebApplicationContext] (main:) Refreshing Root > WebApplicationContext: startup date [Thu May 02 10:05:45 CEST 2013]; root of > context hierarchy > INFO [factory.xml.XmlBeanDefinitionReader] (main:) Loading XML bean > definitions from class path resource [applicationContext.xml] > INFO [factory.xml.XmlBeanDefinitionReader] (main:) Loading XML bean > definitions from class path resource [nonossComponentContext.xml] > INFO [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:) > JSR-330 'javax.inject.Inject' annotation found and supported for autowiring > INFO [context.support.XmlWebApplicationContext] (main:) Bean > 'transactionContextBuilder' of type [class > com.cloud.utils.db.TransactionContextBuilder] is not eligible for getting > processed by all BeanPostProcessor > s (for example: not eligible for auto-proxying) > INFO [context.support.XmlWebApplicationContext] (main:) Bean > 'actionEventInterceptor' of type [class > com.cloud.event.ActionEventInterceptor] is not eligible for getting processed > by all BeanPostProcessors (for ex > ample: not eligible for auto-proxying) > |...] > INFO [utils.component.ComponentContext] (main:) Setup Spring Application > context > INFO [db.Transaction.Transaction] (main:) Encryption set > INFO [db.Transaction.Transaction] (main:) SQL :cloudstackprp cloudstackprp > INFO [cloud.serializer.GsonHelper] (main:) Default Builder inited. > INFO [hypervisor.vmware.VmwareServerDiscoverer] (main:) > VmwareServerDiscoverer is constructed > INFO [web.context.ContextLoader] (main:) Root WebApplicationContext: > initialization completed in 12179 ms > INFO [cloud.utils.LogUtils] (main:) log4j configuration found at > /usr2/web/cloudstack-prp.bop.cloud.mbs/client/WEB-INF/classes/log4j-cloud.xml > INFO [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:) > JSR-330 'javax.inject.Inject' annotation found and supported for autowiring > INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean > com.cloud.service.dao.ServiceOfferingDaoImpl_EnhancerByCloudStack_af34365d@5e8dc627 > May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig > deployDescriptor > INFO: Deploying configuration descriptor host-manager.xml > INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean > com.cloud.storage.dao.DiskOfferingDaoImpl_EnhancerByCloudStack_eb5bef65@5d9d277e > May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig > deployDescriptor > INFO: Deploying configuration descriptor manager.xml > May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig > deployDescriptor > WARNING: A docBase /usr/local/webapps/manager inside the host appBase has > been specified, and will be ignored > INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean > com.cloud.dc.dao.DataCenterDaoImpl_EnhancerByCloudStack_64f15179@7f371a59 > May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig deployDirectory > INFO: Deploying web application directory examples > INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean > com.cloud.dc.dao.HostPodDaoImpl_EnhancerByCloudStack_8ac13ca5@351775bc > INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean > com.cloud.dc.dao.VlanDaoImpl_EnhancerByCloudStack_77d75d5@15b57dcb > INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean > com.cloud.user.dao.UserDaoImpl_EnhancerByCloudStack_f3e2d1d9@4e81d783 > INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean > com.cloud.storage.dao.VMTemplateDaoImpl_EnhancerByCloudStack_c338eac7@29086036 > INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean > com.cloud.hypervisor.dao.Hyperv
[jira] [Created] (CLOUDSTACK-2309) Upgrade from 2.2.14 to 4.1.0 : network static routes deleted on SSVM
Nicolas Lamirault created CLOUDSTACK-2309: - Summary: Upgrade from 2.2.14 to 4.1.0 : network static routes deleted on SSVM Key: CLOUDSTACK-2309 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2309 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Nicolas Lamirault Priority: Blocker Fix For: 4.1.0 After upgrading from 2.2.14 to 4.1.0, we have rebooted the SSVM. After that, all network static routes disapeared. This static routes was added by CS on 2.2.14 dynamically. -- 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
[jira] [Comment Edited] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647498#comment-13647498 ] Nicolas Lamirault edited comment on CLOUDSTACK-2207 at 5/2/13 1:19 PM: --- i try with system-wmware-3.0.5 it fails. According to the code : select id from `cloud`.`vm_template` where name = 'systemvm-vmware-3.0.0' and removed is null"); I try with "system-wmware-3.0.0" it works. You could update the documentation. was (Author: nlamirault): i try with system-wmware-3.0.5 it fails. I try with "system-wmware-3.0.0" it works. You could update the documentation. > Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present > > > Key: CLOUDSTACK-2207 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Chip Childers >Priority: Critical > Fix For: 4.1.0 > > > We're trying to upgrade from 2.2.14 to 4.1.0. > DatabaseUpgradeChecker failed : > 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] > (Timer-1:null) System integrity check failed. Refuse to startup > com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm > template not found. Cannot upgrade system Vms > at > com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) > at > com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) > at > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- 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
[jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647498#comment-13647498 ] Nicolas Lamirault commented on CLOUDSTACK-2207: --- i try with system-wmware-3.0.5 it fails. I try with "system-wmware-3.0.0" it works. You could update the documentation. > Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present > > > Key: CLOUDSTACK-2207 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Chip Childers >Priority: Critical > Fix For: 4.1.0 > > > We're trying to upgrade from 2.2.14 to 4.1.0. > DatabaseUpgradeChecker failed : > 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] > (Timer-1:null) System integrity check failed. Refuse to startup > com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm > template not found. Cannot upgrade system Vms > at > com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) > at > com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) > at > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- 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
[jira] [Issue Comment Deleted] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2207: -- Comment: was deleted (was: I retry the upgrade with system template "system-vmware-3.0.5" : 2013-05-02 10:06:33,504 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Dropping public_ip_address keys from `cloud`.`secondary_storage_vm` and console_proxy tables... 2013-05-02 10:06:33,585 DEBUG [upgrade.dao.DbUpgradeUtils] (Timer-1:null) Key public_ip_address is dropped successfully from the table secondary_storage_vm 2013-05-02 10:06:33,640 DEBUG [upgrade.dao.DbUpgradeUtils] (Timer-1:null) Key public_ip_address is dropped successfully from the table console_proxy 2013-05-02 10:06:33,640 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Updating System Vm template IDs 2013-05-02 10:06:33,641 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Updating XenSever System Vms 2013-05-02 10:06:33,642 WARN [upgrade.dao.Upgrade2214to30] (Timer-1:null) 3.0.0 XenServer SystemVm template not found. XenServer hypervisor is not used, so not failing upgrade 2013-05-02 10:06:33,643 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Updating KVM System Vms 2013-05-02 10:06:33,643 WARN [upgrade.dao.Upgrade2214to30] (Timer-1:null) 3.0.0 KVM SystemVm template not found. KVM hypervisor is not used, so not failing upgrade 2013-05-02 10:06:33,644 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Updating VMware System Vms 2013-05-02 10:06:33,649 DEBUG [db.Transaction.Transaction] (Timer-1:null) Rolling back the transaction: Time = 30651 Name = Upgrade; called by -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.clos e:657-DatabaseUpgradeChecker.upgrade:284-DatabaseUpgradeChecker.check:379-ComponentContext.initComponentsLifeCycle:91-CloudStartupServlet$1.run:50-TimerThread.mainLoop:512-TimerThread.run:462 2013-05-02 10:06:33,653 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm template not found. Cannot upgrade system Vms at com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) at com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) So i restore database in 2.2.14 andi install new template "system-vmware-3.0.0". Now the error is : 2013-05-02 14:35:56,349 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Grabbing lock to check for database upgrade. 2013-05-02 14:35:56,367 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created 2013-05-02 14:35:56,374 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 2.2.14 Code Version = 4.1.0 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 2.2.14 to 4.1.0 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DBVersion upgrade from : 2.2.14 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 3.0.0 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 3.0.1 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 3.0.2 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 4.0.0 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 4.1.0 2013-05-02 14:35:56,376 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Running upgrade Upgrade2214to30 to upgrade from 2.2.14-3.0.0 to 3.0.0 2013-05-02 14:35:56,383 DEBUG [utils.script.Script] (Timer-1:null) Looking for db/schema-2214to30.sql in the classpath 2013-05-02 14:35:56,383 DEBUG [utils.script.Script] (Timer-1:null) System resource: null 2013-05-02 14:35:56,384 DEBUG [utils.script.Script] (Timer-1:null) Classpath resource: null 2013-05-02 14:35:56,384 DEBUG [utils.script.Script] (Timer-1:null) Looking for db/schema-2214to30.sql 2013-05-02 14:35:56,384 DEBUG [utils.script.Script] (Timer-1:null) Current binaries reside at /usr2/web/cloudstack-prp.bop.cloud.mbs/client/WEB-INF/lib 2013-05-02 14:35:56,385 DEBUG [utils.script.Script] (Timer-1:null) Looking for db/schema
[jira] [Reopened] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault reopened CLOUDSTACK-2207: --- I retry the upgrade with system template "system-vmware-3.0.5" : 2013-05-02 10:06:33,504 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Dropping public_ip_address keys from `cloud`.`secondary_storage_vm` and console_proxy tables... 2013-05-02 10:06:33,585 DEBUG [upgrade.dao.DbUpgradeUtils] (Timer-1:null) Key public_ip_address is dropped successfully from the table secondary_storage_vm 2013-05-02 10:06:33,640 DEBUG [upgrade.dao.DbUpgradeUtils] (Timer-1:null) Key public_ip_address is dropped successfully from the table console_proxy 2013-05-02 10:06:33,640 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Updating System Vm template IDs 2013-05-02 10:06:33,641 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Updating XenSever System Vms 2013-05-02 10:06:33,642 WARN [upgrade.dao.Upgrade2214to30] (Timer-1:null) 3.0.0 XenServer SystemVm template not found. XenServer hypervisor is not used, so not failing upgrade 2013-05-02 10:06:33,643 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Updating KVM System Vms 2013-05-02 10:06:33,643 WARN [upgrade.dao.Upgrade2214to30] (Timer-1:null) 3.0.0 KVM SystemVm template not found. KVM hypervisor is not used, so not failing upgrade 2013-05-02 10:06:33,644 DEBUG [upgrade.dao.Upgrade2214to30] (Timer-1:null) Updating VMware System Vms 2013-05-02 10:06:33,649 DEBUG [db.Transaction.Transaction] (Timer-1:null) Rolling back the transaction: Time = 30651 Name = Upgrade; called by -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.clos e:657-DatabaseUpgradeChecker.upgrade:284-DatabaseUpgradeChecker.check:379-ComponentContext.initComponentsLifeCycle:91-CloudStartupServlet$1.run:50-TimerThread.mainLoop:512-TimerThread.run:462 2013-05-02 10:06:33,653 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm template not found. Cannot upgrade system Vms at com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) at com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) So i restore database in 2.2.14 andi install new template "system-vmware-3.0.0". Now the error is : 2013-05-02 14:35:56,349 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Grabbing lock to check for database upgrade. 2013-05-02 14:35:56,367 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created 2013-05-02 14:35:56,374 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 2.2.14 Code Version = 4.1.0 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 2.2.14 to 4.1.0 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DBVersion upgrade from : 2.2.14 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 3.0.0 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 3.0.1 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 3.0.2 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 4.0.0 2013-05-02 14:35:56,375 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) --> Upgrade: 4.1.0 2013-05-02 14:35:56,376 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Running upgrade Upgrade2214to30 to upgrade from 2.2.14-3.0.0 to 3.0.0 2013-05-02 14:35:56,383 DEBUG [utils.script.Script] (Timer-1:null) Looking for db/schema-2214to30.sql in the classpath 2013-05-02 14:35:56,383 DEBUG [utils.script.Script] (Timer-1:null) System resource: null 2013-05-02 14:35:56,384 DEBUG [utils.script.Script] (Timer-1:null) Classpath resource: null 2013-05-02 14:35:56,384 DEBUG [utils.script.Script] (Timer-1:null) Looking for db/schema-2214to30.sql 2013-05-02 14:35:56,384 DEBUG [utils.script.Script] (Timer-1:null) Current binaries reside at /usr2/web/cloudstack-prp.bop.cloud.mbs/client/WEB-INF/lib 2013-05-02 14:35:56,385 DEBUG [utils.script.Script] (Timer-1:null) Looking for db/schema-2214to30.sql in /usr2/web/c
[jira] [Created] (CLOUDSTACK-2302) Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade
Nicolas Lamirault created CLOUDSTACK-2302: - Summary: Upgrade from 2.2.14 to 4.1.0 failed due to database upgrade Key: CLOUDSTACK-2302 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2302 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Nicolas Lamirault Priority: Blocker Fix For: 4.1.0 I try to upgrade from 2.2.14 to 4.1.0 INFO: Initializing log4j from [classpath:log4j-cloud.xml] May 2, 2013 10:05:45 AM org.apache.catalina.core.ApplicationContext log INFO: Initializing Spring root WebApplicationContext INFO [web.context.ContextLoader] (main:) Root WebApplicationContext: initialization started INFO [context.support.XmlWebApplicationContext] (main:) Refreshing Root WebApplicationContext: startup date [Thu May 02 10:05:45 CEST 2013]; root of context hierarchy INFO [factory.xml.XmlBeanDefinitionReader] (main:) Loading XML bean definitions from class path resource [applicationContext.xml] INFO [factory.xml.XmlBeanDefinitionReader] (main:) Loading XML bean definitions from class path resource [nonossComponentContext.xml] INFO [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:) JSR-330 'javax.inject.Inject' annotation found and supported for autowiring INFO [context.support.XmlWebApplicationContext] (main:) Bean 'transactionContextBuilder' of type [class com.cloud.utils.db.TransactionContextBuilder] is not eligible for getting processed by all BeanPostProcessor s (for example: not eligible for auto-proxying) INFO [context.support.XmlWebApplicationContext] (main:) Bean 'actionEventInterceptor' of type [class com.cloud.event.ActionEventInterceptor] is not eligible for getting processed by all BeanPostProcessors (for ex ample: not eligible for auto-proxying) |...] INFO [utils.component.ComponentContext] (main:) Setup Spring Application context INFO [db.Transaction.Transaction] (main:) Encryption set INFO [db.Transaction.Transaction] (main:) SQL :cloudstackprp cloudstackprp INFO [cloud.serializer.GsonHelper] (main:) Default Builder inited. INFO [hypervisor.vmware.VmwareServerDiscoverer] (main:) VmwareServerDiscoverer is constructed INFO [web.context.ContextLoader] (main:) Root WebApplicationContext: initialization completed in 12179 ms INFO [cloud.utils.LogUtils] (main:) log4j configuration found at /usr2/web/cloudstack-prp.bop.cloud.mbs/client/WEB-INF/classes/log4j-cloud.xml INFO [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:) JSR-330 'javax.inject.Inject' annotation found and supported for autowiring INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.service.dao.ServiceOfferingDaoImpl_EnhancerByCloudStack_af34365d@5e8dc627 May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor host-manager.xml INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.storage.dao.DiskOfferingDaoImpl_EnhancerByCloudStack_eb5bef65@5d9d277e May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor manager.xml May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig deployDescriptor WARNING: A docBase /usr/local/webapps/manager inside the host appBase has been specified, and will be ignored INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.dc.dao.DataCenterDaoImpl_EnhancerByCloudStack_64f15179@7f371a59 May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory examples INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.dc.dao.HostPodDaoImpl_EnhancerByCloudStack_8ac13ca5@351775bc INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.dc.dao.VlanDaoImpl_EnhancerByCloudStack_77d75d5@15b57dcb INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.user.dao.UserDaoImpl_EnhancerByCloudStack_f3e2d1d9@4e81d783 INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.storage.dao.VMTemplateDaoImpl_EnhancerByCloudStack_c338eac7@29086036 INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.hypervisor.dao.HypervisorCapabilitiesDaoImpl_EnhancerByCloudStack_45b65693@34139285 May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory ROOT INFO [utils.component.ComponentContext] (Timer-1:) Spring configure bean com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_15fe0949@1ddd40f3 May 2, 2013 10:05:57 AM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory docs INFO [utils.compone
[jira] [Commented] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647372#comment-13647372 ] Nicolas Lamirault commented on CLOUDSTACK-2194: --- This patch fix problem on encryption error. > Upgrade from 2.2.14 to 4.1.0 failed due to encryption error > --- > > Key: CLOUDSTACK-2194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Kelven Yang >Priority: Blocker > Fix For: 4.1.0 > > > i'm trying to upgrade from 2.2.14 to 4.1.0. > After setting encryption like that : > $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp > Preparing /etc/cloud/management/db.properties >[ OK ] > Processing encryption ... >[ OK ] > Finalizing setup ... > [ OK ] > CloudStack has successfully setup Encryption > I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D > db.properties content is : > $> grep -v "#" /etc/cloudstack/management/db.properties|sort > cluster.node.IP=127.0.0.1 > cluster.servlet.port=9090 > db.awsapi.host=cloud-sql01-prp.cloud > db.awsapi.name=cloudbridge > db.awsapi.password=cloudstackprp > db.awsapi.port=3306 > db.awsapi.username=cloudstackprp > db.cloud.autoReconnect=true > db.cloud.encryption.type=file > db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ) > db.cloud.host=cloud-sql01-prp.cloud > db.cloud.keyStore= > db.cloud.keyStorePassword= > db.cloud.maxActive=250 > db.cloud.maxIdle=30 > db.cloud.maxWait=1 > db.cloud.minEvictableIdleTimeMillis=24 > db.cloud.name=cloud > db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq) > db.cloud.poolPreparedStatements=false > db.cloud.port=3306 > db.cloud.testOnBorrow=true > db.cloud.testWhileIdle=true > db.cloud.timeBetweenEvictionRunsMillis=4 > db.cloud.trustStore= > db.cloud.trustStorePassword= > db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true > db.cloud.username=cloudstackprp > db.cloud.useSSL=false > db.cloud.validationQuery=SELECT 1 > db.simulator.autoReconnect=true > db.simulator.host=cloud-sql01-prp.cloud > db.simulator.maxActive=250 > db.simulator.maxIdle=30 > db.simulator.maxWait=1 > db.simulator.name=simulator > db.simulator.password=cloudstackprp > db.simulator.port=3306 > db.simulator.username=cloudstackprp > db.usage.autoReconnect=true > db.usage.host=cloud-sql01-prp.cloud > db.usage.maxActive=100 > db.usage.maxIdle=30 > db.usage.maxWait=1 > db.usage.name=cloud_usage > db.usage.password=ENC(K57vTmW5CYCKY5P0B4NoeUchMwBPb1Z3) > db.usage.port=3306 > db.usage.username=cloudstackprp > region.id=1 -- 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
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646628#comment-13646628 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- @Tamas: do you try to compile CS 4.0.2 from source ? To fix exception : com.cloud.utils.exception.CloudRuntimeException: The end upgrade version is actually at 4.0.0 but our management server code version is at 4.0.2.20130420145617 you need to change in each pom.xml file version number, and update DatabaseUpgradeChecker and PremiumDatabaseUpgradeChecker to add database migration I can help you if you want (my nick : l_a_m on cloudstack-dev channel) On May 2, i try to upgrade to 4.1.0 and verify this issue too. > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.0.2 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID matches but API throws exception while the IS is supplied in the > query.
[jira] [Commented] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646387#comment-13646387 ] Nicolas Lamirault commented on CLOUDSTACK-2194: --- Sure, i will test this fix tomorrow on thursday. Do you think database upgrade will be called first ? According to this patch, it seems only ApiServer is changed. > Upgrade from 2.2.14 to 4.1.0 failed due to encryption error > --- > > Key: CLOUDSTACK-2194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Kelven Yang >Priority: Blocker > Fix For: 4.1.0 > > > i'm trying to upgrade from 2.2.14 to 4.1.0. > After setting encryption like that : > $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp > Preparing /etc/cloud/management/db.properties >[ OK ] > Processing encryption ... >[ OK ] > Finalizing setup ... > [ OK ] > CloudStack has successfully setup Encryption > I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D > db.properties content is : > $> grep -v "#" /etc/cloudstack/management/db.properties|sort > cluster.node.IP=127.0.0.1 > cluster.servlet.port=9090 > db.awsapi.host=cloud-sql01-prp.cloud > db.awsapi.name=cloudbridge > db.awsapi.password=cloudstackprp > db.awsapi.port=3306 > db.awsapi.username=cloudstackprp > db.cloud.autoReconnect=true > db.cloud.encryption.type=file > db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ) > db.cloud.host=cloud-sql01-prp.cloud > db.cloud.keyStore= > db.cloud.keyStorePassword= > db.cloud.maxActive=250 > db.cloud.maxIdle=30 > db.cloud.maxWait=1 > db.cloud.minEvictableIdleTimeMillis=24 > db.cloud.name=cloud > db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq) > db.cloud.poolPreparedStatements=false > db.cloud.port=3306 > db.cloud.testOnBorrow=true > db.cloud.testWhileIdle=true > db.cloud.timeBetweenEvictionRunsMillis=4 > db.cloud.trustStore= > db.cloud.trustStorePassword= > db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true > db.cloud.username=cloudstackprp > db.cloud.useSSL=false > db.cloud.validationQuery=SELECT 1 > db.simulator.autoReconnect=true > db.simulator.host=cloud-sql01-prp.cloud > db.simulator.maxActive=250 > db.simulator.maxIdle=30 > db.simulator.maxWait=1 > db.simulator.name=simulator > db.simulator.password=cloudstackprp > db.simulator.port=3306 > db.simulator.username=cloudstackprp > db.usage.autoReconnect=true > db.usage.host=cloud-sql01-prp.cloud > db.usage.maxActive=100 > db.usage.maxIdle=30 > db.usage.maxWait=1 > db.usage.name=cloud_usage > db.usage.password=ENC(K57vTmW5CYCKY5P0B4NoeUchMwBPb1Z3) > db.usage.port=3306 > db.usage.username=cloudstackprp > region.id=1 -- 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
[jira] [Commented] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645529#comment-13645529 ] Nicolas Lamirault commented on CLOUDSTACK-2194: --- Same bug with another component. Before database upgrade process, CS try to read configuration for the ApiServer initialization. And all entries which have category=hidden aren't encrypted. It is possible to force DatabaseUpgrade process to be the first component to be called ? > Upgrade from 2.2.14 to 4.1.0 failed due to encryption error > --- > > Key: CLOUDSTACK-2194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: sebastien goasguen >Priority: Blocker > Fix For: 4.1.0 > > > i'm trying to upgrade from 2.2.14 to 4.1.0. > After setting encryption like that : > $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp > Preparing /etc/cloud/management/db.properties >[ OK ] > Processing encryption ... >[ OK ] > Finalizing setup ... > [ OK ] > CloudStack has successfully setup Encryption > I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D > db.properties content is : > $> grep -v "#" /etc/cloudstack/management/db.properties|sort > cluster.node.IP=127.0.0.1 > cluster.servlet.port=9090 > db.awsapi.host=cloud-sql01-prp.cloud > db.awsapi.name=cloudbridge > db.awsapi.password=cloudstackprp > db.awsapi.port=3306 > db.awsapi.username=cloudstackprp > db.cloud.autoReconnect=true > db.cloud.encryption.type=file > db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ) > db.cloud.host=cloud-sql01-prp.cloud > db.cloud.keyStore= > db.cloud.keyStorePassword= > db.cloud.maxActive=250 > db.cloud.maxIdle=30 > db.cloud.maxWait=1 > db.cloud.minEvictableIdleTimeMillis=24 > db.cloud.name=cloud > db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq) > db.cloud.poolPreparedStatements=false > db.cloud.port=3306 > db.cloud.testOnBorrow=true > db.cloud.testWhileIdle=true > db.cloud.timeBetweenEvictionRunsMillis=4 > db.cloud.trustStore= > db.cloud.trustStorePassword= > db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true > db.cloud.username=cloudstackprp > db.cloud.useSSL=false > db.cloud.validationQuery=SELECT 1 > db.simulator.autoReconnect=true > db.simulator.host=cloud-sql01-prp.cloud > db.simulator.maxActive=250 > db.simulator.maxIdle=30 > db.simulator.maxWait=1 > db.simulator.name=simulator > db.simulator.password=cloudstackprp > db.simulator.port=3306 > db.simulator.username=cloudstackprp > db.usage.autoReconnect=true > db.usage.host=cloud-sql01-prp.cloud > db.usage.maxActive=100 > db.usage.maxIdle=30 > db.usage.maxWait=1 > db.usage.name=cloud_usage > db.usage.password=ENC(K57vTmW5CYCKY5P0B4NoeUchMwBPb1Z3) > db.usage.port=3306 > db.usage.username=cloudstackprp > region.id=1 -- 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
[jira] [Reopened] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault reopened CLOUDSTACK-2194: --- BUG due to ApiServer > Upgrade from 2.2.14 to 4.1.0 failed due to encryption error > --- > > Key: CLOUDSTACK-2194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: sebastien goasguen >Priority: Blocker > Fix For: 4.1.0 > > > i'm trying to upgrade from 2.2.14 to 4.1.0. > After setting encryption like that : > $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp > Preparing /etc/cloud/management/db.properties >[ OK ] > Processing encryption ... >[ OK ] > Finalizing setup ... > [ OK ] > CloudStack has successfully setup Encryption > I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D > db.properties content is : > $> grep -v "#" /etc/cloudstack/management/db.properties|sort > cluster.node.IP=127.0.0.1 > cluster.servlet.port=9090 > db.awsapi.host=cloud-sql01-prp.cloud > db.awsapi.name=cloudbridge > db.awsapi.password=cloudstackprp > db.awsapi.port=3306 > db.awsapi.username=cloudstackprp > db.cloud.autoReconnect=true > db.cloud.encryption.type=file > db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ) > db.cloud.host=cloud-sql01-prp.cloud > db.cloud.keyStore= > db.cloud.keyStorePassword= > db.cloud.maxActive=250 > db.cloud.maxIdle=30 > db.cloud.maxWait=1 > db.cloud.minEvictableIdleTimeMillis=24 > db.cloud.name=cloud > db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq) > db.cloud.poolPreparedStatements=false > db.cloud.port=3306 > db.cloud.testOnBorrow=true > db.cloud.testWhileIdle=true > db.cloud.timeBetweenEvictionRunsMillis=4 > db.cloud.trustStore= > db.cloud.trustStorePassword= > db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true > db.cloud.username=cloudstackprp > db.cloud.useSSL=false > db.cloud.validationQuery=SELECT 1 > db.simulator.autoReconnect=true > db.simulator.host=cloud-sql01-prp.cloud > db.simulator.maxActive=250 > db.simulator.maxIdle=30 > db.simulator.maxWait=1 > db.simulator.name=simulator > db.simulator.password=cloudstackprp > db.simulator.port=3306 > db.simulator.username=cloudstackprp > db.usage.autoReconnect=true > db.usage.host=cloud-sql01-prp.cloud > db.usage.maxActive=100 > db.usage.maxIdle=30 > db.usage.maxWait=1 > db.usage.name=cloud_usage > db.usage.password=ENC(K57vTmW5CYCKY5P0B4NoeUchMwBPb1Z3) > db.usage.port=3306 > db.usage.username=cloudstackprp > region.id=1 -- 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
[jira] [Commented] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645407#comment-13645407 ] Nicolas Lamirault commented on CLOUDSTACK-2194: --- Now it seems bug comes from ApiServer : 2013-04-30 11:11:34,978 INFO [web.context.ContextLoader] (main:null) Root WebApplicationContext: initialization started 2013-04-30 11:11:35,104 INFO [context.support.XmlWebApplicationContext] (main:null) Refreshing Root WebApplicationContext: startup date [Tue Apr 30 11:11:35 CEST 2013]; root of context hierarchy 2013-04-30 11:11:35,185 INFO [factory.xml.XmlBeanDefinitionReader] (main:null) Loading XML bean definitions from class path resource [applicationContext.xml] 2013-04-30 11:11:35,715 INFO [factory.xml.XmlBeanDefinitionReader] (main:null) Loading XML bean definitions from class path resource [nonossComponentContext.xml] 2013-04-30 11:11:37,583 INFO [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:null) JSR-330 'javax.inject.Inject' annotation found and supported for autowiring 2013-04-30 11:11:37,628 INFO [context.support.XmlWebApplicationContext] (main:null) Bean 'transactionContextBuilder' of type [class com.cloud.utils.db.TransactionContextBuilder] is not eligible for getting proces sed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2013-04-30 11:11:37,633 INFO [context.support.XmlWebApplicationContext] (main:null) Bean 'actionEventInterceptor' of type [class com.cloud.event.ActionEventInterceptor] is not eligible for getting processed by al l BeanPostProcessors (for example: not eligible for auto-proxying) 2013-04-30 11:11:37,692 INFO [factory.support.DefaultListableBeanFactory] (main:null) Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@5c09624: defining beans [ org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAn notationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,componentContext,transactionContextBuilder,actionEventInterceptor,instantiatePostProcessor,onwireRegistry,messageSerialize r,transportProvider,rpcProvider,eventBus,serviceOfferingDaoImpl,diskOfferingDaoImpl,dataCenterDaoImpl,hostPodDaoImpl,vlanDaoImpl,userDaoImpl,VMTemplateDaoImpl,hypervisorCapabilitiesDaoImpl,accountDaoImpl,accountDe tailsDaoImpl,accountJoinDaoImpl,accountVlanMapDaoImpl,agentUpgradeDaoImpl,alertDaoImpl,asyncJobDaoImpl,asyncJobJoinDaoImpl,autoScalePolicyConditionMapDaoImpl,autoScalePolicyDaoImpl,autoScaleVmGroupDaoImpl,autoScal eVmGroupPolicyMapDaoImpl,autoScaleVmProfileDaoImpl,capacityDaoImpl,certificateDaoImpl,clusterDaoImpl,clusterDetailsDaoImpl,commandExecLogDaoImpl,conditionDaoImpl,consoleProxyDaoImpl,counterDaoImpl,dataCenterIpAddr essDaoImpl,dataCenterJoinDaoImpl,dataCenterLinkLocalIpAddressDaoImpl,dataCenterVnetDaoImpl,dataStoreProviderDaoImpl,dcDetailsDaoImpl,engineDcDetailsDaoImpl,diskOfferingJoinDaoImpl,domainDaoImpl,domainRouterDaoImpl ,domainRouterJoinDaoImpl,elasticLbVmMapDaoImpl,engineClusterDaoImpl,engineDataCenterDaoImpl,engineHostDaoImpl,engineHostPodDaoImpl,eventDaoImpl,eventJoinDaoImpl,externalFirewallDeviceDaoImpl,externalLoadBalancerDe viceDaoImpl,externalPublicIpStatisticsDaoImpl,firewallRulesCidrsDaoImpl,firewallRulesDaoImpl,guestOSCategoryDaoImpl,guestOSDaoImpl,highAvailabilityDaoImpl,hostDaoImpl,hostDetailsDaoImpl,engineHostDetailsDaoImpl,ho stJoinDaoImpl,engineHostTagsDaoImpl,hostTagsDaoImpl,hostTransferMapDaoImpl,iPAddressDaoImpl,identityDaoImpl,imageDaoStoreDaoImpl,imageDataDaoImpl,imageDataStoreProviderDaoImpl,inlineLoadBalancerNicMapDaoImpl,insta nceGroupDaoImpl,instanceGroupJoinDaoImpl,instanceGroupVMMapDaoImpl,itWorkDaoImpl,keystoreDaoImpl,lBStickinessPolicyDaoImpl,launchPermissionDaoImpl,loadBalancerDaoImpl,loadBalancerVMMapDaoImpl,managementServerHostD aoImpl,managementServerHostPeerDaoImpl,networkAccountDaoImpl,networkDaoImpl,networkDomainDaoImpl,networkExternalFirewallDaoImpl,networkExternalLoadBalancerDaoImpl,networkOfferingDaoImpl,networkOfferingServiceMapDa oImpl,networkOpDaoImpl,networkRuleConfigDaoImpl,networkServiceMapDaoImpl,nicDaoImpl,objectInDataStoreDaoImpl,ovsTunnelInterfaceDaoImpl,ovsTunnelNetworkDaoImpl,physicalNetworkDaoImpl,physicalNetworkIsolationMethodD aoImpl,physicalNetworkServiceProviderDaoImpl,physicalNetworkTagDaoImpl,physicalNetworkTrafficTypeDaoImpl,podVlanDaoImpl,podVlanMapDaoImpl,portForwardingRulesDaoImpl,primaryDataStoreDaoImpl,primaryDataStoreDetailsD aoImpl,privateIpDaoImpl,projectAccountDaoImpl,projectAccountJoinDaoImpl,projectDaoImpl,projectInvitationDaoImpl,projectInvitationJoinDaoImpl,projectJoinDaoImpl,regionDaoImpl,remoteAccessVpnDaoImpl,resourceCountDao Impl,resourceLimitDaoImpl,resourceTagJoinDaoImpl,resourceTagsDaoImpl
[jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644552#comment-13644552
]
Nicolas Lamirault commented on CLOUDSTACK-2207:
---
Hello,
This issue seems blocker ...
In file 'server/src/com/cloud/upgrade/dao/Upgrade2214to30.java',
DatabaseUpgrade depends on systemvm-vmware-3.0.0 :
//VMware
s_logger.debug("Updating VMware System Vms");
try {
//Get 3.0.0 VMware system Vm template Id
pstmt = conn.prepareStatement("select id from
`cloud`.`vm_template` where name = 'systemvm-vmware-3.0.0' and removed is
null");
rs = pstmt.executeQuery();
if(rs.next()){
long templateId = rs.getLong(1);
rs.close();
pstmt.close();
// change template type to SYSTEM
pstmt = conn.prepareStatement("update `cloud`.`vm_template`
set type='SYSTEM' where id = ?");
pstmt.setLong(1, templateId);
pstmt.executeUpdate();
pstmt.close();
// update templete ID of system Vms
pstmt = conn.prepareStatement("update `cloud`.`vm_instance`
set vm_template_id = ? where type <> 'User' and hypervisor_type = 'VMware'");
pstmt.setLong(1, templateId);
pstmt.executeUpdate();
pstmt.close();
} else {
if (VMware){
throw new CloudRuntimeException("3.0.0 VMware SystemVm
template not found. Cannot upgrade system Vms");
} else {
s_logger.warn("3.0.0 VMware SystemVm template not
found. VMware hypervisor is not used, so not failing upgrade");
}
}
} catch (SQLException e) {
throw new CloudRuntimeException("Error while updating VMware
systemVm template", e);
}
This upgrade (2.2.14 to 3.0) can't be done without this template.
> Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
>
>
> Key: CLOUDSTACK-2207
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0
>Reporter: Nicolas Lamirault
> Fix For: 4.1.0
>
>
> We're trying to upgrade from 2.2.14 to 4.1.0.
> DatabaseUpgradeChecker failed :
> 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext]
> (Timer-1:null) System integrity check failed. Refuse to startup
> com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm
> template not found. Cannot upgrade system Vms
> at
> com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713)
> at
> com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379)
> at
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91)
> at
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> According to the documentation, there is no VMware SystemVm 3.0.0 to install.
--
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
[jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644495#comment-13644495 ] Nicolas Lamirault commented on CLOUDSTACK-2207: --- I did as it says on page 50, installing a new system template : VMware Name: systemvm-vmware-4.1.0 Description: systemvm-vmware-4.1.0 URL: http://download.cloud.com/templates/burbank/burbank- systemvm-08012012.ova Zone: Choose the zone where this hypervisor is used Hypervisor: VMware Format: OVA OS Type: Debian GNU/Linux 5.0 (32-bit) Extractable: no Password Enabled: no Public: no Featured: no > Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present > > > Key: CLOUDSTACK-2207 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault > Fix For: 4.1.0 > > > We're trying to upgrade from 2.2.14 to 4.1.0. > DatabaseUpgradeChecker failed : > 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] > (Timer-1:null) System integrity check failed. Refuse to startup > com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm > template not found. Cannot upgrade system Vms > at > com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) > at > com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) > at > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- 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
[jira] [Updated] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2207: -- Fix Version/s: 4.1.0 Affects Version/s: 4.1.0 > Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present > > > Key: CLOUDSTACK-2207 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault > Fix For: 4.1.0 > > > We're trying to upgrade from 2.2.14 to 4.1.0. > DatabaseUpgradeChecker failed : > 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] > (Timer-1:null) System integrity check failed. Refuse to startup > com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm > template not found. Cannot upgrade system Vms > at > com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) > at > com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) > at > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- 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
[jira] [Comment Edited] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642765#comment-13642765 ] Nicolas Lamirault edited comment on CLOUDSTACK-2194 at 4/26/13 3:22 PM: Before the upgrade : mysql> select * from version ; ++-+-+--+ | id | version | updated | step | ++-+-+--+ | 1 | 2.2.13.2013-01-18T10:50:46Z | 2013-02-15 09:03:22 | Complete | | 2 | 2.2.14 | 2013-04-25 10:54:12 | Complete | ++-+-+--+ 2 rows in set (0.00 sec) mysql> select * from configuration where name ='cloud.identifier'; +--+--+---+--+--++ | category | instance | component | name | value | description| +--+--+---+--+--++ | Hidden | DEFAULT | management-server | cloud.identifier | f8af0421-a349-487f-9a25-8f25540a2d2d | A unique identifier for the cloud. | +--+--+---+--+--++ 1 row in set (0.00 sec) was (Author: nlamirault): mysql> select * from version ; ++-+-+--+ | id | version | updated | step | ++-+-+--+ | 1 | 2.2.13.2013-01-18T10:50:46Z | 2013-02-15 09:03:22 | Complete | | 2 | 2.2.14 | 2013-04-25 10:54:12 | Complete | ++-+-+--+ 2 rows in set (0.00 sec) mysql> select * from configuration where name ='cloud.identifier'; +--+--+---+--+--++ | category | instance | component | name | value | description| +--+--+---+--+--++ | Hidden | DEFAULT | management-server | cloud.identifier | f8af0421-a349-487f-9a25-8f25540a2d2d | A unique identifier for the cloud. | +--+--+---+--+--++ 1 row in set (0.00 sec) > Upgrade from 2.2.14 to 4.1.0 failed due to encryption error > --- > > Key: CLOUDSTACK-2194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Kishan Kavala >Priority: Blocker > Fix For: 4.1.0 > > > i'm trying to upgrade from 2.2.14 to 4.1.0. > After setting encryption like that : > $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp > Preparing /etc/cloud/management/db.properties >[ OK ] > Processing encryption ... >[ OK ] > Finalizing setup ... > [ OK ] > CloudStack has successfully setup Encryption > I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D > db.properties content is : > $> grep -v "#" /etc/cloudstack/management/db.properties|sort > cluster.node.IP=127.0.0.1 > cluster.servlet.port=9090 > db.awsapi.host=cloud-sql01-prp.cloud > db.awsapi.name=cloudbridge > db.awsapi.password=cloudstackprp > db.awsapi.port=3306 > db.awsapi.username=cloudstackprp > db.cloud.autoReconnect=true > db.cloud.encryption.type=file > db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ) > db.cloud.host=cloud-sql01-prp.cloud > db.cloud.keyStore= > db.cloud.keyStorePassword= > db.cloud.maxActive=250 > db.cloud.maxIdle=30 > db.cloud.maxWait=1 > db.cloud.minEvictableIdleTimeMillis=24 > db.cloud.name=cloud > db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq) > db.cloud.poolPreparedStatements=false > db.cloud.port=3306 > db.cloud.testOnBorrow=true > db.cloud.testWhileIdle=true > db.cloud.timeBetweenEvictionRunsMillis=4 > db.cloud.trustStore= >
[jira] [Commented] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642765#comment-13642765 ] Nicolas Lamirault commented on CLOUDSTACK-2194: --- mysql> select * from version ; ++-+-+--+ | id | version | updated | step | ++-+-+--+ | 1 | 2.2.13.2013-01-18T10:50:46Z | 2013-02-15 09:03:22 | Complete | | 2 | 2.2.14 | 2013-04-25 10:54:12 | Complete | ++-+-+--+ 2 rows in set (0.00 sec) mysql> select * from configuration where name ='cloud.identifier'; +--+--+---+--+--++ | category | instance | component | name | value | description| +--+--+---+--+--++ | Hidden | DEFAULT | management-server | cloud.identifier | f8af0421-a349-487f-9a25-8f25540a2d2d | A unique identifier for the cloud. | +--+--+---+--+--++ 1 row in set (0.00 sec) > Upgrade from 2.2.14 to 4.1.0 failed due to encryption error > --- > > Key: CLOUDSTACK-2194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Kishan Kavala >Priority: Blocker > Fix For: 4.1.0 > > > i'm trying to upgrade from 2.2.14 to 4.1.0. > After setting encryption like that : > $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp > Preparing /etc/cloud/management/db.properties >[ OK ] > Processing encryption ... >[ OK ] > Finalizing setup ... > [ OK ] > CloudStack has successfully setup Encryption > I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D > db.properties content is : > $> grep -v "#" /etc/cloudstack/management/db.properties|sort > cluster.node.IP=127.0.0.1 > cluster.servlet.port=9090 > db.awsapi.host=cloud-sql01-prp.cloud > db.awsapi.name=cloudbridge > db.awsapi.password=cloudstackprp > db.awsapi.port=3306 > db.awsapi.username=cloudstackprp > db.cloud.autoReconnect=true > db.cloud.encryption.type=file > db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ) > db.cloud.host=cloud-sql01-prp.cloud > db.cloud.keyStore= > db.cloud.keyStorePassword= > db.cloud.maxActive=250 > db.cloud.maxIdle=30 > db.cloud.maxWait=1 > db.cloud.minEvictableIdleTimeMillis=24 > db.cloud.name=cloud > db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq) > db.cloud.poolPreparedStatements=false > db.cloud.port=3306 > db.cloud.testOnBorrow=true > db.cloud.testWhileIdle=true > db.cloud.timeBetweenEvictionRunsMillis=4 > db.cloud.trustStore= > db.cloud.trustStorePassword= > db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true > db.cloud.username=cloudstackprp > db.cloud.useSSL=false > db.cloud.validationQuery=SELECT 1 > db.simulator.autoReconnect=true > db.simulator.host=cloud-sql01-prp.cloud > db.simulator.maxActive=250 > db.simulator.maxIdle=30 > db.simulator.maxWait=1 > db.simulator.name=simulator > db.simulator.password=cloudstackprp > db.simulator.port=3306 > db.simulator.username=cloudstackprp > db.usage.autoReconnect=true > db.usage.host=cloud-sql01-prp.cloud > db.usage.maxActive=100 > db.usage.maxIdle=30 > db.usage.maxWait=1 > db.usage.name=cloud_usage > db.usage.password=ENC(K57vTmW5CYCKY5P0B4NoeUchMwBPb1Z3) > db.usage.port=3306 > db.usage.username=cloudstackprp > region.id=1 -- 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
[jira] [Created] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
Nicolas Lamirault created CLOUDSTACK-2207: - Summary: Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present Key: CLOUDSTACK-2207 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nicolas Lamirault We're trying to upgrade from 2.2.14 to 4.1.0. DatabaseUpgradeChecker failed : 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm template not found. Cannot upgrade system Vms at com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) at com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- 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
[jira] [Commented] (CLOUDSTACK-2201) Failed to start MS after fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642698#comment-13642698 ] Nicolas Lamirault commented on CLOUDSTACK-2201: --- According to this file : https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=server/src/com/cloud/upgrade/PremiumDatabaseUpgradeChecker.java;h=bad32536955239d8bc7394e4d78e8184c5d4997b;hb=HEAD new Upgrade410to420() for each database migration are missing. > Failed to start MS after fresh installation > > > Key: CLOUDSTACK-2201 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2201 > 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 > Environment: CentOS 6.3 build > Branch master >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-2201.rar > > > Step 1 :Install MS from master branch build > Step 2 : execute > cloudstack-setup-databases cloud:password@localhost --deploy-as=root:password > cloudstack-setup-management > Actual result > Failed to management server, with below error in MS log > 2013-04-25 22:01:06,030 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) DB version = 4.0.0 Code Version = 4.2.0-SNAPSHOT > 2013-04-25 22:01:06,030 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) Database upgrade must be performed from 4.0.0 to 4.2.0-SNAPSHOT > 2013-04-25 22:01:06,030 ERROR [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) The end upgrade version is actually at 4.1.0 but our > management server code version is at 4.2.0-SNAPSHOT > 2013-04-25 22:01:06,036 ERROR [utils.component.ComponentContext] > (Timer-1:null) System integrity check failed. Refuse to startup > Is it happening due to below check-in ? > Commit 099677a1244cd55fb98d3c40ee7881223dd9ac7c by chip.childers > CLOUDSTACK-2172: adding database upgrade to 4.1.0 in > PremiumDatabaseUpgradeChecker > Add migration to 4.1.0 in the PremiumDatabaseUpgradeChecker, like in the > DatabaseUpgradeChecker. -- 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
[jira] [Commented] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641912#comment-13641912
]
Nicolas Lamirault commented on CLOUDSTACK-2194:
---
According to file "server/src/com/cloud/upgrade/dao/Upgrade2214to30.java",
there is a method which is responsible for data encryption :
private void encryptConfigValues(Connection conn) {
s_logger.debug("Encrypting Config values");
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
pstmt = conn.prepareStatement("select name, value from
`cloud`.`configuration` where category in ('Hidden', 'Secure')");
rs = pstmt.executeQuery();
while (rs.next()) {
String name = rs.getString(1);
String value = rs.getString(2);
if (value == null) {
continue;
}
String encryptedValue = DBEncryptionUtil.encrypt(value);
pstmt = conn.prepareStatement("update `cloud`.`configuration`
set value=? where name=?");
pstmt.setBytes(1, encryptedValue.getBytes("UTF-8"));
pstmt.setString(2, name);
pstmt.executeUpdate();
}
} catch (SQLException e) {
throw new CloudRuntimeException("Unable encrypt configuration
values ", e);
} catch (UnsupportedEncodingException e) {
throw new CloudRuntimeException("Unable encrypt configuration
values ", e);
} finally {
try {
if (rs != null) {
rs.close();
}
if (pstmt != null) {
pstmt.close();
}
} catch (SQLException e) {
}
}
s_logger.debug("Done encrypting Config values");
}
But before database upgrade process, CS try to read configuration. And all
entries which have category=hidden aren't encrypted.
> Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
> ---
>
> Key: CLOUDSTACK-2194
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0
>Reporter: Nicolas Lamirault
>Priority: Blocker
> Fix For: 4.1.0
>
>
> i'm trying to upgrade from 2.2.14 to 4.1.0.
> After setting encryption like that :
> $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp
> Preparing /etc/cloud/management/db.properties
>[ OK ]
> Processing encryption ...
>[ OK ]
> Finalizing setup ...
> [ OK ]
> CloudStack has successfully setup Encryption
> I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D
> db.properties content is :
> $> grep -v "#" /etc/cloudstack/management/db.properties|sort
> cluster.node.IP=127.0.0.1
> cluster.servlet.port=9090
> db.awsapi.host=cloud-sql01-prp.cloud
> db.awsapi.name=cloudbridge
> db.awsapi.password=cloudstackprp
> db.awsapi.port=3306
> db.awsapi.username=cloudstackprp
> db.cloud.autoReconnect=true
> db.cloud.encryption.type=file
> db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ)
> db.cloud.host=cloud-sql01-prp.cloud
> db.cloud.keyStore=
> db.cloud.keyStorePassword=
> db.cloud.maxActive=250
> db.cloud.maxIdle=30
> db.cloud.maxWait=1
> db.cloud.minEvictableIdleTimeMillis=24
> db.cloud.name=cloud
> db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq)
> db.cloud.poolPreparedStatements=false
> db.cloud.port=3306
> db.cloud.testOnBorrow=true
> db.cloud.testWhileIdle=true
> db.cloud.timeBetweenEvictionRunsMillis=4
> db.cloud.trustStore=
> db.cloud.trustStorePassword=
> db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true
> db.cloud.username=cloudstackprp
> db.cloud.useSSL=false
> db.cloud.validationQuery=SELECT 1
> db.simulator.autoReconnect=true
> db.simulator.host=cloud-sql01-prp.cloud
> db.simulator.maxActive=250
> db.simulator.maxIdle=30
> db.simulator.maxWait=1
> db.simulator.name=simulator
> db.simulator.password=cloudstackprp
> db.simulator.port=3306
> db.simulator.username=cloudstackprp
> db.usage.autoReconnect=true
> db.usage.host=cloud-sql01-prp.cloud
> db.usage.maxActive=100
> db.usage.maxIdle=30
> db.usage.maxWait=1
> db.usage.name=cloud_usage
> db.usage.password=ENC(K57vTmW5CYCKY5P0B4NoeUchMwBPb1Z3)
> db.usage.port=3306
> db.usage.username=cloudstackprp
> region.id=1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
F
[jira] [Comment Edited] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641895#comment-13641895
]
Nicolas Lamirault edited comment on CLOUDSTACK-2194 at 4/25/13 3:41 PM:
By adding a log here :
diff --git a/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
b/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
index fe5f5ae..69524dc 100644
--- a/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
+++ b/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
@@ -81,6 +81,7 @@ public class ConfigurationDaoImpl extends
GenericDaoBase configurations = listIncludingRemovedBy(sc);
for (ConfigurationVO config : configurations) {
+s_logger.info("Config " + config.getName());
if (config.getValue() != null)
_configs.put(config.getName(), config.getValue());
}
we can see in Cloudstack logs :
2013-04-25 17:37:08,802 INFO [cloudstack.discovery.ApiDiscoveryServiceImpl]
(main:null) Api Discovery Service: Annotation, docstrings, api relation graph
processed in 428.764924 ms
2013-04-25 17:37:09,216 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config account.cleanup.interval
2013-04-25 17:37:09,216 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config agent.lb.enabled
2013-04-25 17:37:09,216 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config agent.load.threshold
2013-04-25 17:37:09,216 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.email.addresses
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.email.sender
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.host
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.password
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.port
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.useAuth
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.username
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.wait
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config allow.public.user.templates
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config allow.subdomain.network.access
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config backup.snapshot.wait
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config capacity.check.period
2013-04-25 17:37:09,218 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config capacity.skipcounting.hours
2013-04-25 17:37:09,218 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config check.pod.cidrs
2013-04-25 17:37:09,218 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config cloud.identifier
2013-04-25 17:37:09,239 DEBUG [utils.crypt.DBEncryptionUtil] (main:null) Error
while decrypting: f8af0421-a349-487f-9a25-8f25540a2d2d
And we can find the entry into database :
mysql> select * from configuration where name = 'cloud.identifier';
+--+--+---+--+--++
| category | instance | component | name | value
| description|
+--+--+---+--+--++
| Hidden | DEFAULT | management-server | cloud.identifier |
f8af0421-a349-487f-9a25-8f25540a2d2d | A unique identifier for the cloud. |
+--+--+---+--+--++
was (Author: nlamirault):
By adding a log here :
diff --git a/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
b/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
index fe5f5ae..69524dc 100644
--- a/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
+++ b/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
@@ -81,6 +81,7 @@ public class ConfigurationDaoImpl extends
GenericDaoBase configurations = listIncludingRemovedBy(sc);
for (ConfigurationVO config : configurations) {
+s_logger.info("Config " + config.getName());
if (config.getValue() != null)
_configs.put(config.getName(), config.getValue());
[jira] [Commented] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641895#comment-13641895
]
Nicolas Lamirault commented on CLOUDSTACK-2194:
---
By adding a log here :
diff --git a/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
b/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
index fe5f5ae..69524dc 100644
--- a/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
+++ b/server/src/com/cloud/configuration/dao/ConfigurationDaoImpl.java
@@ -81,6 +81,7 @@ public class ConfigurationDaoImpl extends
GenericDaoBase configurations = listIncludingRemovedBy(sc);
for (ConfigurationVO config : configurations) {
+s_logger.info("Config " + config.getName());
if (config.getValue() != null)
_configs.put(config.getName(), config.getValue());
}
we can see in Cloudstack logs :
2013-04-25 17:37:08,802 INFO [cloudstack.discovery.ApiDiscoveryServiceImpl]
(main:null) Api Discovery Service: Annotation, docstrings, api relation graph
processed in 428.764924 ms
2013-04-25 17:37:09,216 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config account.cleanup.interval
2013-04-25 17:37:09,216 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config agent.lb.enabled
2013-04-25 17:37:09,216 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config agent.load.threshold
2013-04-25 17:37:09,216 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.email.addresses
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.email.sender
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.host
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.password
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.port
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.useAuth
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.smtp.username
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config alert.wait
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config allow.public.user.templates
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config allow.subdomain.network.access
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config backup.snapshot.wait
2013-04-25 17:37:09,217 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config capacity.check.period
2013-04-25 17:37:09,218 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config capacity.skipcounting.hours
2013-04-25 17:37:09,218 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config check.pod.cidrs
2013-04-25 17:37:09,218 INFO [configuration.dao.ConfigurationDaoImpl]
(main:null) Config cloud.identifier
2013-04-25 17:37:09,239 DEBUG [utils.crypt.DBEncryptionUtil] (main:null) Error
while decrypting: f8af0421-a349-487f-9a25-8f25540a2d2d
And we can find the entry into database :
mysql> select name, value from configuration where name = 'cloud.identifier';
+--+--+
| name | value|
+--+--+
| cloud.identifier | f8af0421-a349-487f-9a25-8f25540a2d2d |
+--+--+
> Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
> ---
>
> Key: CLOUDSTACK-2194
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0
>Reporter: Nicolas Lamirault
> Fix For: 4.1.0
>
>
> i'm trying to upgrade from 2.2.14 to 4.1.0.
> After setting encryption like that :
> $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp
> Preparing /etc/cloud/management/db.properties
>[ OK ]
> Processing encryption ...
>[ OK ]
> Finalizing setup ...
> [ OK ]
> CloudStack has successfully setup Encryption
> I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D
> db.properties content is :
> $> grep -v "#" /etc/cloudstack/management/db.properties|sort
> cluster.node.IP=127.0.0.1
> clust
[jira] [Updated] (CLOUDSTACK-2194) Upgrade from 2.2.14 to 4.1.0 failed due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2194: -- Fix Version/s: 4.1.0 Description: i'm trying to upgrade from 2.2.14 to 4.1.0. After setting encryption like that : $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp Preparing /etc/cloud/management/db.properties [ OK ] Processing encryption ... [ OK ] Finalizing setup ... [ OK ] CloudStack has successfully setup Encryption I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D db.properties content is : $> grep -v "#" /etc/cloudstack/management/db.properties|sort cluster.node.IP=127.0.0.1 cluster.servlet.port=9090 db.awsapi.host=cloud-sql01-prp.cloud db.awsapi.name=cloudbridge db.awsapi.password=cloudstackprp db.awsapi.port=3306 db.awsapi.username=cloudstackprp db.cloud.autoReconnect=true db.cloud.encryption.type=file db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ) db.cloud.host=cloud-sql01-prp.cloud db.cloud.keyStore= db.cloud.keyStorePassword= db.cloud.maxActive=250 db.cloud.maxIdle=30 db.cloud.maxWait=1 db.cloud.minEvictableIdleTimeMillis=24 db.cloud.name=cloud db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq) db.cloud.poolPreparedStatements=false db.cloud.port=3306 db.cloud.testOnBorrow=true db.cloud.testWhileIdle=true db.cloud.timeBetweenEvictionRunsMillis=4 db.cloud.trustStore= db.cloud.trustStorePassword= db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true db.cloud.username=cloudstackprp db.cloud.useSSL=false db.cloud.validationQuery=SELECT 1 db.simulator.autoReconnect=true db.simulator.host=cloud-sql01-prp.cloud db.simulator.maxActive=250 db.simulator.maxIdle=30 db.simulator.maxWait=1 db.simulator.name=simulator db.simulator.password=cloudstackprp db.simulator.port=3306 db.simulator.username=cloudstackprp db.usage.autoReconnect=true db.usage.host=cloud-sql01-prp.cloud db.usage.maxActive=100 db.usage.maxIdle=30 db.usage.maxWait=1 db.usage.name=cloud_usage db.usage.password=ENC(K57vTmW5CYCKY5P0B4NoeUchMwBPb1Z3) db.usage.port=3306 db.usage.username=cloudstackprp region.id=1 Affects Version/s: 4.1.0 Summary: Upgrade from 2.2.14 to 4.1.0 failed due to encryption error (was: U) > Upgrade from 2.2.14 to 4.1.0 failed due to encryption error > --- > > Key: CLOUDSTACK-2194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault > Fix For: 4.1.0 > > > i'm trying to upgrade from 2.2.14 to 4.1.0. > After setting encryption like that : > $> cloud-setup-encryption -m cloudstackprp -k cloudstackprp > Preparing /etc/cloud/management/db.properties >[ OK ] > Processing encryption ... >[ OK ] > Finalizing setup ... > [ OK ] > CloudStack has successfully setup Encryption > I start Cloudstack. Output logs are here : http://pastebin.com/ZE99v90D > db.properties content is : > $> grep -v "#" /etc/cloudstack/management/db.properties|sort > cluster.node.IP=127.0.0.1 > cluster.servlet.port=9090 > db.awsapi.host=cloud-sql01-prp.cloud > db.awsapi.name=cloudbridge > db.awsapi.password=cloudstackprp > db.awsapi.port=3306 > db.awsapi.username=cloudstackprp > db.cloud.autoReconnect=true > db.cloud.encryption.type=file > db.cloud.encrypt.secret=ENC(dKaV+o5+JqtVi2tfo9xVn6eyUatFXwfZ) > db.cloud.host=cloud-sql01-prp.cloud > db.cloud.keyStore= > db.cloud.keyStorePassword= > db.cloud.maxActive=250 > db.cloud.maxIdle=30 > db.cloud.maxWait=1 > db.cloud.minEvictableIdleTimeMillis=24 > db.cloud.name=cloud > db.cloud.password=ENC(IhnVBWyQT2ES/YNjPleAz6GXHoGrVsvq) > db.cloud.poolPreparedStatements=false > db.cloud.port=3306 > db.cloud.testOnBorrow=true > db.cloud.testWhileIdle=true > db.cloud.timeBetweenEvictionRunsMillis=4 > db.cloud.trustStore= > db.cloud.trustStorePassword= > db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true > db.cloud.username=cloudstackprp > db.cloud.useSSL=false > db.cloud.validationQuery=SELECT 1 > db.simulator.autoReconnect=true > db.simulator.host=cloud-sql01-prp.cloud > db.simulator.maxActive=250 > db.simulator.maxIdle=30 > db.simulator.maxWait=1 > db.simulator.name=simulator > db.simulator.password=cloudstackprp > db.simulator.port=3306 > db.simulator.username=cloudstack
[jira] [Created] (CLOUDSTACK-2194) U
Nicolas Lamirault created CLOUDSTACK-2194: - Summary: U Key: CLOUDSTACK-2194 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2194 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nicolas Lamirault -- 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
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641637#comment-13641637 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- We only use Ubutu and vmWare. > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0 > Environment: CentOS >Reporter: Tamas Monos >Priority: Blocker > Fix For: 4.0.2 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID matches but API throws exception while the IS is supplied in the > query. > Scenario: > I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not > update the systemVMs to the new template I've applied a workaround and > recreated the systemVMs with the new templates. After that I've enabled > storage clean-up and the cleanup script destroyed everything on my primary > storage including systemVMs. I wanted to re-create them but cannot add > secondary storage to the Zone. > The applied workarounds during upgrade: > 1. Add new vmware templat
[jira] [Updated] (CLOUDSTACK-2172) Upgrade from 2.2.14 to 4.1.0 failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2172: -- Fix Version/s: 4.1.0 > Upgrade from 2.2.14 to 4.1.0 failed > --- > > Key: CLOUDSTACK-2172 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2172 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Priority: Blocker > Fix For: 4.1.0 > > > due to BUG CS 528, we can't upgrade our production to 4.0.x. > So we try to upgrade to 4.1.0. > When we start CS, we 've read theses logs : > 2013-04-24 10:57:23,407 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) > Checking to see if the database is at a version before it was the version > table is created > 2013-04-24 10:57:23,420 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) DB version = 2.2.14 Code Version = 4.1.0 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) Database upgrade must be performed from 2.2.14 to 4.1.0 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.7 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 > 3.0.2 4.0.0 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.6 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 > 3.0.2 4.0.0 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.5 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 > 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.4 > 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.5 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 > 3.0.0 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.3 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.4 2.2.4 2.2.5 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 > 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.2 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.4 2.2.4 2.2.5 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 > 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.1 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.2 2.2.4 2.2.4 2.2.5 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 > 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 3.0.2 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 4.0.0 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 3.0.1 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 3.0.2 4.0.0 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.10 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.11 > 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.8 > 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 > 4.0.0 > 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.12 > 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) => Version 2.2.9 > 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] > (Timer-1:null) 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 > 2013-04-24 10:57:23,423 INFO [cloud.upgr
[jira] [Created] (CLOUDSTACK-2172) Upgrade from 2.2.14 to 4.1.0 failed
Nicolas Lamirault created CLOUDSTACK-2172: - Summary: Upgrade from 2.2.14 to 4.1.0 failed Key: CLOUDSTACK-2172 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2172 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Nicolas Lamirault due to BUG CS 528, we can't upgrade our production to 4.0.x. So we try to upgrade to 4.1.0. When we start CS, we 've read theses logs : 2013-04-24 10:57:23,407 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created 2013-04-24 10:57:23,420 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 2.2.14 Code Version = 4.1.0 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 2.2.14 to 4.1.0 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.7 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.6 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.5 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.4 2013-04-24 10:57:23,421 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.5 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.3 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.4 2.2.4 2.2.5 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.2 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.4 2.2.4 2.2.5 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.1 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.2 2.2.4 2.2.4 2.2.5 2.2.6 2.2.8 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 3.0.2 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 4.0.0 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 3.0.1 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 3.0.2 4.0.0 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.10 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,422 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.11 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.8 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.9 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.12 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.9 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.10 2.2.11 2.2.12 2.2.13 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.2.13 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.2.14 3.0.0 3.0.1 3.0.2 4.0.0 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) => Version 2.1.7 2013-04-24 10:57:23,423 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) 2.1.8 2.2.1 2.2.2 2.2.4 2.2.4 2.2.5
[jira] [Comment Edited] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616407#comment-13616407 ] Nicolas Lamirault edited comment on CLOUDSTACK-528 at 4/2/13 9:22 AM: -- According to this commit : https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=095f5523b9832488071579f347035037a9b9babf there is only documentation fixes. As Tamas said, this bug is not only a problem of documentation. Regards was (Author: nlamirault): According to this commit : https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=095f5523b9832488071579f347035037a9b9babf, there is only documentation fixes. As Tamas said, this bug is not only a problem of documentation. Regards > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0 > Environment: CentOS >Reporter: Tamas Monos >Assignee: Saksham Srivastava >Priority: Blocker > Fix For: 4.0.2 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +
[jira] [Comment Edited] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616407#comment-13616407 ] Nicolas Lamirault edited comment on CLOUDSTACK-528 at 3/28/13 4:44 PM: --- According to this commit : https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=095f5523b9832488071579f347035037a9b9babf, there is only documentation fixes. As Tamas said, this bug is not only a problem of documentation. Regards was (Author: nlamirault): According to this commit : https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=095f5523b9832488071579f347035037a9b9babf, there is only documentation fixes. As Tamas said, this bug is not only a problem of documentation > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0 > Environment: CentOS >Reporter: Tamas Monos >Assignee: Saksham Srivastava >Priority: Blocker > Fix For: 4.0.2 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616407#comment-13616407 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- According to this commit : https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=095f5523b9832488071579f347035037a9b9babf, there is only documentation fixes. As Tamas said, this bug is not only a problem of documentation > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0 > Environment: CentOS >Reporter: Tamas Monos >Assignee: Saksham Srivastava >Priority: Blocker > Fix For: 4.0.2 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID matches but API throws exception while the IS is supplied in the > query. > Scenario: > I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not > update the systemVMs to the new template I've applied a workaround and > recreated the systemVMs with the new templates. After that I've enabled > st
[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608768#comment-13608768 ] Nicolas Lamirault commented on CLOUDSTACK-528: -- hi, do you have any information regarding the resolution of this issue ? it is a date planned for version 4.0.2 ? Regards. > Failed to create secondary storage > -- > > Key: CLOUDSTACK-528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.0.0 > Environment: CentOS >Reporter: Tamas Monos >Assignee: Saksham Srivastava >Priority: Blocker > Fix For: 4.0.2 > > > Hi, > I cannot add secondary storage to my existing Zone. This prevents the > platform from operating. > API call via GUI captured by tcpdump: > http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114 > Result: > Unable to connect due to > java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data > center: null > at > com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501) > at > com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551) > at > com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2012-11-23 12:32:58,518 INFO [cloud.resource.ResourceManagerImpl] > (catalina-exec-23:null) server resources successfully discovered by > SecondaryStorage > 2012-11-23 12:32:58,518 WARN [cloud.api.ApiDispatcher] > (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to > add secondary storage > Debug: > mysql> select uuid from data_center where name='Watford'; > +--+ > | uuid | > +--+ > | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 | > +--+ > The Zone ID matches but API throws exception while the IS is supplied in the > query. > Scenario: > I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not > update the systemVMs to the new template I've applied a workaround and > recreated the systemVMs with the new templates. After that I've enabled > storage clean-up and the cleanup script destroyed everything on my primary > storage including systemVMs. I wanted t
