Nicolas, in order to upgrade to 4.0, you need to have systemvm-vmware-4.0
template pre-installed. Apache CS release notes mention it (section 3.2):

http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.2/html/Releas
e_Notes/upgrade-instructions.html#upgrade-from-2.2.x-to-4.0


What pdf you are referring to?

-Alena.

On 6/3/13 4:28 AM, "nicolas.lamira...@orange.com"
<nicolas.lamira...@orange.com> wrote:

>Hi,
>we try to upgrade from 2.2.14 to 4.1
>And we failed on this logs :
>
>2013-06-03 13:15:24,367 DEBUG [utils.db.ScriptRunner] (Timer-1:null)
>UPDATE `cloud`.`user` SET PASSWORD=RAND() WHERE id=1
>2013-06-03 13:15:24,367 DEBUG [utils.db.ScriptRunner] (Timer-1:null)
>ALTER TABLE `cloud_usage`.`account` ADD COLUMN `default_zone_id` bigint
>unsigned
>2013-06-03 13:15:24,552 DEBUG [upgrade.dao.Upgrade302to40]
>(Timer-1:null) Updating VMware System Vms
>2013-06-03 13:15:24,556 DEBUG [db.Transaction.Transaction]
>(Timer-1:null) Rolling back the transaction: Time = 9675 Name =
>Upgrade; called by
>-Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close
>:657-DatabaseUpgradeChecker.upgrade:263-DatabaseUpgradeChecker.check:358-C
>omponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:50-Ti
>merThread.mainLoop:512-TimerThread.run:462
>2013-06-03 13:15:24,558 ERROR [utils.component.ComponentContext]
>(Timer-1:null) System integrity check failed. Refuse to startup
>
>According to the code :
>
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=server/s
>rc/com/cloud/upgrade/dao/Upgrade302to40.java;h=6f31fdd2b8eda8e15c223adceed
>52c70a6457349;hb=a5214bee99f6c5582d755c9499f7d99fd7b5b701
>
>// Just update the VMware system template. Other hypervisor templates
>are unchanged from previous 3.0.x versions.
>  105         s_logger.debug("Updating VMware System Vms");
>  106         try {
>  107             //Get 4.0 VMware system Vm template Id
>  108             pstmt = conn.prepareStatement("select id from
>`cloud`.`vm_template` where name = 'systemvm-vmware-4.0' and removed is
>null");
>  109             rs = pstmt.executeQuery();
>  110             if(rs.next()){
>  111                 long templateId = rs.getLong(1);
>  112                 rs.close();
>  113                 pstmt.close();
>  114                 // change template type to SYSTEM
>  115                 pstmt = conn.prepareStatement("update
>`cloud`.`vm_template` set type='SYSTEM' where id = ?");
>  116                 pstmt.setLong(1, templateId);
>  117                 pstmt.executeUpdate();
>  118                 pstmt.close();
>  119                 // update templete ID of system Vms
>  120                 pstmt = conn.prepareStatement("update
>`cloud`.`vm_instance` set vm_template_id = ? where type <> 'User' and
>hypervisor_type = 'VMware'");
>  121                 pstmt.setLong(1, templateId);
>  122                 pstmt.executeUpdate();
>  123                 pstmt.close();
>  124             } else {
>  125                 if (VMware){
>  126                     throw new CloudRuntimeException("4.0 VMware
>SystemVm template not found. Cannot upgrade system Vms");
>  127                 } else {
>  128                     s_logger.warn("4.0 VMware SystemVm template
>not found. VMware hypervisor is not used, so not failing upgrade");
>  129                 }
>  130             }
>  131         } catch (SQLException e) {
>  132             throw new CloudRuntimeException("Error while updating
>VMware systemVm template", e);
>  133         }
>
>but in release PDF, it is written :
>
>VMware
>Name: systemvm-vmware-3.0.5
>Description: systemvm-vmware-3.0.5
>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
>
>
>So ? it is a documentation bug ?
>Regards.
>
>-- 
>Nicolas Lamirault
>
>__________________________________________________________________________
>_______________________________________________
>
>Ce message et ses pieces jointes peuvent contenir des informations
>confidentielles ou privilegiees et ne doivent donc
>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>recu ce message par erreur, veuillez le signaler
>a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>electroniques etant susceptibles d'alteration,
>France Telecom - Orange decline toute responsabilite si ce message a ete
>altere, deforme ou falsifie. Merci.
>
>This message and its attachments may contain confidential or privileged
>information that may be protected by law;
>they should not be distributed, used or copied without authorisation.
>If you have received this email in error, please notify the sender and
>delete this message and its attachments.
>As emails may be altered, France Telecom - Orange is not liable for
>messages that have been modified, changed or falsified.
>Thank you.
>
>


Reply via email to