Was this fixed in the 4.1 branch as well?

On Tue, Jul 09, 2013 at 07:09:52PM +0000, Alena Prokharchyk (JIRA) wrote:
> 
>     [ 
> https://issues.apache.org/jira/browse/CLOUDSTACK-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703664#comment-13703664
>  ] 
> 
> Alena Prokharchyk commented on CLOUDSTACK-3417:
> -----------------------------------------------
> 
> Fixed the missing table problem. Add it as a part of 306-41 upgrade. Now 
> reassigning the bug to Sheng as he needs to fix the foreign key insertion 
> portion for those tables. Currently the keys are being inserted in .sql file; 
> it should be moved to java part of the code and be inserted only when they 
> don't exist. Because some setups might have those keys, and some might miss 
> them. if the setup has the keys, you run into this exception during the 
> upgrade:
> 
> INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must 
> be performed from 3.0.6.2013-07-09T18:58:51Z to 4.2.0-SNAPSHOT
> ERROR [utils.db.ScriptRunner] (Timer-2:) Error executing: ALTER TABLE 
> `cloud`.`baremetal_dhcp_devices` ADD CONSTRAINT 
> `fk_external_dhcp_devices_nsp_id` FOREIGN KEY (`nsp_id`) REFERENCES 
> `physical_network_service_providers` (`id`) ON DELETE CASCADE
> ERROR [utils.db.ScriptRunner] (Timer-2:) java.sql.SQLException: Can't create 
> table 'cloud.#sql-c2_bc' (errno: 121)
> ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Unable to execute 
> upgrade script: 
> /Users/alena/campo/client/target/utilities/scripts/db/db/schema-410to420.sql
> java.sql.SQLException: Can't create table 'cloud.#sql-c2_bc' (errno: 121)
>       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
>                 
> > [Upgrade to 4.2.0] Upgrade to 4.2.0 fails with 
> > om.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 
> > 'cloud.baremetal_dhcp_devices' doesn't exist 
> > ------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> >                 Key: CLOUDSTACK-3417
> >                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3417
> >             Project: CloudStack
> >          Issue Type: Bug
> >      Security Level: Public(Anyone can view this level - this is the 
> > default.) 
> >          Components: Install and Setup
> >    Affects Versions: 4.2.0
> >            Reporter: Abhinav Roy
> >            Assignee: Alena Prokharchyk
> >            Priority: Blocker
> >             Fix For: 4.2.0
> >
> >         Attachments: management-server.log
> >
> >
> > Upgrade from CS 3.0.6 to 4.2.0 fails with the following error :
> > 2013-07-09 16:08:56,133 ERROR [utils.db.ScriptRunner] (Timer-1:null) 
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 
> > 'cloud.baremetal_dhcp_devices' doesn't exist
> > 2013-07-09 16:08:56,135 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
> > (Timer-1:null) Unable to execute upgrade script: 
> > /usr/share/cloudstack-management/setup/db/schema-410to420.sql
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 
> > 'cloud.baremetal_dhcp_devices' doesn't exist
> >         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:211)
> >         at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:272)
> >         at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:401)
> >         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-09 16:08:56,139 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-410to420.sql
> >         at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:220)
> >         at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:272)
> >         at 
> > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:401)
> >         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: Table 
> > 'cloud.baremetal_dhcp_devices' doesn't exist
> >         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:211)
> >         ... 6 more
> > 2013-07-09 16:08:56,144 DEBUG [db.Transaction.Transaction] (Timer-1:null) 
> > Rolling back the transaction: Time = 1467 Name =  null; called by 
> > -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-DatabaseUpgradeChecker.upgrade:305-DatabaseUpgradeChecker.check:401-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:50-TimerThread.mainLoop:534-TimerThread.run:484
> > 2013-07-09 16:08:56,144 ERROR [utils.component.ComponentContext] 
> > (Timer-1:null) System integrity check failed. Refuse to startup
> 
> --
> 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
> 

Reply via email to