[
https://issues.apache.org/jira/browse/CLOUDSTACK-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307340#comment-14307340
]
Andreas Stenius commented on CLOUDSTACK-8212:
---------------------------------------------
MariaDB 5.5.36 on a RedHat 6 machine.
If you can't reproduce it, feel free to close it as a one off inconsistency
unless you get others with this issue. I can try it again, but I'm a little
pressed for time right now; and since I got past this step with a manual patch,
that's good enough for me right now.
> database upgrade failed for fresh install of 4.5.0-SNAPSHOT
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-8212
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8212
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.5.0
> Environment: RedHat 7, external MariaDB on custom port.
> Reporter: Andreas Stenius
> Attachments: cloudstack-4.5.0-SNAPSHOT-logs.tar.gz
>
>
> During installation of a new system, when first starting the MS, it logs that
> the db needs upgrading from 4.0.0, but fails to do so (see attached logs).
> The culprit would seem to be due to these error messages (my guess from
> screening the logs...):
> ERROR [c.c.u.d.ScriptRunner] (localhost-startStop-1:null) Error executing:
> UPDATE `cloud`.`configuration` SET value = CONCAT("*.",(SELECT
> `temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE
> `name`="consoleproxy.url.domain") AS `temptable` WHERE
> `temptable`.`name`="consoleproxy.url.domain")) WHERE
> `name`="consoleproxy.url.domain"
> ERROR [c.c.u.d.ScriptRunner] (localhost-startStop-1:null)
> java.sql.SQLException: You can't specify target table 'configuration' for
> update in FROM clause
> ERROR [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) Unable to
> execute upgrade script:
> /usr/share/cloudstack-management/setup/db/schema-421to430.sql
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
