You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Bharat Kumar (JIRA)" <ji...@apache.org> on 2013/07/29 19:17:49 UTC
[jira] [Updated] (CLOUDSTACK-3910) Upgrade from 3.0.6 to 4.2 is
failing with DB exceptions.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Kumar updated CLOUDSTACK-3910:
-------------------------------------
Status: Ready To Review (was: In Progress)
> Upgrade from 3.0.6 to 4.2 is failing with DB exceptions.
> --------------------------------------------------------
>
> Key: CLOUDSTACK-3910
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3910
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Upgrade
> Affects Versions: 4.2.0
> Environment: upgrade from 3.0.6 to 4.2
> Reporter: manasaveloori
> Assignee: Bharat Kumar
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Steps:
>
> 1. Install 3.0.6 patch E build.
> 2. Added 2 hosts with different zones(KVM and xen6.1)
> 3. Added SRX,Netscaler,F5 devices to the setup.
> 4. Configured the static nat using SRX,LB using Netscaler and F5.
> 5. Upgarde the build to 4.2
> Observing the following exceptions:
> -07-29 23:02:23,185 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-07-29 23:02:23,195 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 3.0.6.20130524112703 Code Version = 4.2.0-SNAPSHOT
> 2013-07-29 23:02:23,202 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 3.0.6.20130524112703 to 4.2.0-SNAPSHOT
> 2013-07-29 23:02:23,202 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Running upgrade Upgrade306to307 to upgrade from 3.0.6-3.0.7 to 3.0.7
> 2013-07-29 23:02:23,226 DEBUG [utils.script.Script] (Timer-1:null) Looking for db/schema-306to307.sql in the classpath
> 2013-07-29 23:02:23,227 DEBUG [utils.script.Script] (Timer-1:null) System resource: file:/usr/share/cloudstack-management/setup/db/schema-306to307.sql
> 2013-07-29 23:02:23,227 DEBUG [utils.script.Script] (Timer-1:null) Absolute path = /usr/share/cloudstack-management/setup/db/schema-306to307.sql
> 2013-07-29 23:02:23,231 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- Licensed to the Apache Software Foundation (ASF) under one
> 2013-07-29 23:02:23,234 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- or more contributor license agreements. See the NOTICE file
> 2013-07-29 23:02:23,234 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- distributed with this work for additional information
> 2013-07-29 23:02:23,234 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- regarding copyright ownership. The ASF licenses this file
> 2013-07-29 23:02:23,234 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- to you under the Apache License, Version 2.0 (the
> 2013-07-29 23:02:23,234 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- "License"); you may not use this file except in compliance
> 2013-07-29 23:02:23,234 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- with the License. You may obtain a copy of the License at
> 2013-07-29 23:02:23,235 DEBUG [utils.db.ScriptRunner] (Timer-1:null) --
> 2013-07-29 23:02:23,235 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- http://www.apache.org/licenses/LICENSE-2.0
> 2013-07-29 23:02:23,237 DEBUG [utils.db.ScriptRunner] (Timer-1:null) --
> 2013-07-29 23:02:23,237 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- Unless required by applicable law or agreed to in writing,
> 2013-07-29 23:02:23,237 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- software distributed under the License is distributed on an
> 2013-07-29 23:02:23,237 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> 2013-07-29 23:02:23,237 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- KIND, either express or implied. See the License for the
> 2013-07-29 23:02:23,237 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- specific language governing permissions and limitations
> 2013-07-29 23:02:23,237 DEBUG [utils.db.ScriptRunner] (Timer-1:null) -- under the License.
> 2013-07-29 23:02:23,237 DEBUG [utils.db.ScriptRunner] (Timer-1:null) INSERT IGNORE INTO `cloud`.`configuration` VALUES ('Network', 'DEFAULT', 'management-server', 'network.loadbalancer.haproxy.max.conn', '4096', 'Load Balancer(haproxy) maximum number of concurrent connections(global max)')
> 2013-07-29 23:02:23,243 DEBUG [utils.db.ScriptRunner] (Timer-1:null) ALTER TABLE `cloud`.`network_offerings` ADD COLUMN `concurrent_connections` int(10) unsigned COMMENT 'concurrent connections supported on this network'
> 2013-07-29 23:02:23,245 ERROR [utils.db.ScriptRunner] (Timer-1:null) Error executing: ALTER TABLE `cloud`.`network_offerings` ADD COLUMN `concurrent_connections` int(10) unsigned COMMENT 'concurrent connections supported on this network'
> 2013-07-29 23:02:23,248 ERROR [utils.db.ScriptRunner] (Timer-1:null) com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'concurrent_connections'
> 2013-07-29 23:02:23,250 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-306to307.sql
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'concurrent_connections'
> at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
> at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
> at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:215)
> at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:276)
> at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:405)
> at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
> at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> at java.util.TimerThread.mainLoop(Timer.java:534)
> at java.util.TimerThread.run(Timer.java:484)
> 2013-07-29 23:02:23,257 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Unable to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-306to307.sql
> at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:224)
> at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:276)
> at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:405)
> at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
> at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
> at java.util.TimerThread.mainLoop(Timer.java:534)
> at java.util.TimerThread.run(Timer.java:484)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column name 'concurrent_connections'
> at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:193)
> at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
> at com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:215)
> ... 6 more
> 2013-07-29 23:02:23,262 DEBUG [db.Transaction.Transaction] (Timer-1:null) Rolling back the transaction: Time = 59 Name = null; called by -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-DatabaseUpgradeChecker.upgrade:309-DatabaseUpgradeChecker.check:405-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:50-TimerThread.mainLoop:534-TimerThread.run:484
> 2013-07-29 23:02:23,267 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup
> Note:
> I have upgraded from 3.0.6 patchE to 4.2 (CloudPlatform-4.2-dbupgrade-35-rhel6.2.tar.gz ) without any rules and external devices. It went fine. I did not face any issue.
> Attaching the Ms logs and db dumps.
--
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