cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Lamirault (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
Date Mon, 29 Apr 2013 14:58:15 GMT

    [ 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

Mime
View raw message