Github user serg38 commented on the pull request:
https://github.com/apache/cloudstack/pull/1094#issuecomment-162532791
This index comes from schema-40to410.sql:
CREATE TABLE `cloud`.`nicira_nvp_router_map` (
`id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
`logicalrouter_uuid` varchar(255) NOT NULL UNIQUE COMMENT 'nicira uuid of
logical router',
`network_id` bigint unsigned NOT NULL UNIQUE COMMENT 'cloudstack id of
the network',
PRIMARY KEY (`id`),
CONSTRAINT `fk_nicira_nvp_router_map__network_id` FOREIGN KEY
(`network_id`) REFERENCES `networks`(`id`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
There might be variation how UNIQUE attribute is enforced in different
versions of MySQL.
In 5.5 it generate unique index `logicalrouter_uuid`
To take it out the correct statement is
ALTER TABLE `cloud`.`nicira_nvp_router_map`
DROP INDEX `logicalrouter_uuid` ;
Can you check if schema-40to410.sql got applied in your environment? What
version of MySQL do you use?
The drop index logicalrouter_uuid should come from schema-470to471.sql (or
later upgrade script)but not from schema-410to420-cleanup.sql.
From: Remi Bergsma <[email protected]>
Reply-To: apache/cloudstack <[email protected]>
Date: Sunday, December 6, 2015 at 11:59 AM
To: apache/cloudstack <[email protected]>
Cc: Sergey Levitskiy <[email protected]>
Subject: Re: [cloudstack] CLOUDSTACK-9074: Support shared networking in
NiciraNVP Plugin (#1094)
Guys, I cannot build a cloud from this branch any more. The build itself
works, but the database deployment gives an SQL error: Can't DROP
'logicalrouter_uuid'; check that column/key exists
Details:
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer
---
log4j:WARN No appenders could be found for logger
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
========> WARNING: Provided file does not exist:
/data/git/cs1/cloudstack/developer/../utils/conf/db.properties.override
========> WARNING: Provided file does not exist:
/data/git/cs1/cloudstack/developer/developer-prefill.sql.override
========> Initializing database=cloud with host=localhost port=3306
username=cloud password=cloud
============> Running query: drop database if exists `cloud`
============> Running query: create database `cloud`
============> Running query: GRANT ALL ON cloud.* to 'cloud'@`localhost`
identified by 'cloud'
============> Running query: GRANT ALL ON cloud.* to 'cloud'@`%` identified
by 'cloud'
========> Initializing database=cloud_usage with host=localhost port=3306
username=cloud password=cloud
============> Running query: drop database if exists `cloud_usage`
============> Running query: create database `cloud_usage`
============> Running query: GRANT ALL ON cloud_usage.* to
'cloud'@`localhost` identified by 'cloud'
============> Running query: GRANT ALL ON cloud_usage.* to 'cloud'@`%`
identified by 'cloud'
========> Processing SQL file at
/data/git/cs1/cloudstack/developer/target/db/create-schema.sql
========> Processing SQL file at
/data/git/cs1/cloudstack/developer/target/db/create-schema-premium.sql
========> Processing SQL file at
/data/git/cs1/cloudstack/developer/target/db/templates.sql
========> Processing SQL file at
/data/git/cs1/cloudstack/developer/developer-prefill.sql
========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[WARNING]
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
execute upgrade script:
/data/git/cs1/cloudstack/developer/target/db/db/schema-410to420-cleanup.sql
at
com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:290)
at
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:425)
at
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:474)
at com.cloud.upgrade.DatabaseCreator.main(DatabaseCreator.java:217)
... 6 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't
DROP 'logicalrouter_uuid'; check that column/key exists
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:185)
at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
at
com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:281)
... 9 more
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 19.639s (Wall Clock)
[INFO] Finished at: Sun Dec 06 09:07:53 GMT 2015
[INFO] Final Memory: 43M/259M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:java (create-schema) on project
cloud-developer: An exception occured while executing the Java class. null:
InvocationTargetException: Unable to execute upgrade script:
/data/git/cs1/cloudstack/developer/target/db/db/schema-410to420-cleanup.sql:
Can't DROP 'logicalrouter_uuid'; check that column/key exists -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Not sure if it is related. Tried cleaning everything (VMs, git repo,
storage) but same result.
â
Reply to this email directly or view it on GitHub.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
