[
https://issues.apache.org/jira/browse/CLOUDSTACK-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146070#comment-14146070
]
Alex Brett commented on CLOUDSTACK-7621:
----------------------------------------
Looking at the history, I see the following two schema changes between a
working build and a broken one:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=872b48b0c34d85d934344c8ccf33fa328d2748ed
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=b3c117a11eda3373a5a7187547a441be908f4453
[~pdion] could this be a side effect of these?
> Database schema not getting upgraded
> ------------------------------------
>
> Key: CLOUDSTACK-7621
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7621
> 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
> Reporter: Pavan Kumar Bandarupally
> Priority: Blocker
> Fix For: 4.5.0
>
> Attachments: management-server.log
>
>
> After installing management server , the process is stuck at database schema
> update. The update doesn't progress ahead from 4.0.0
> mysql> select * from version;
> +----+---------+---------------------+----------+
> | id | version | updated | step |
> +----+---------+---------------------+----------+
> | 1 | 4.0.0 | 2014-09-24 12:14:11 | Complete |
> +----+---------+---------------------+----------+
> 1 row in set (0.00 sec)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
