incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kishan Kavala (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-560) Usage server doesn't work in 4.0.0 due to missing db changes
Date Mon, 10 Dec 2012 14:13:20 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kishan Kavala resolved CLOUDSTACK-560.
--------------------------------------

    Resolution: Fixed

Added fix to master and 4.o branches
                
> Usage server doesn't work in 4.0.0 due to missing db changes
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-560
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-560
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.0.0
>            Reporter: David Nalley
>            Assignee: Kishan Kavala
>            Priority: Blocker
>              Labels: database, upgrade
>             Fix For: 4.0.1, 4.1.0
>
>
> [Alerts]
> Usage job failed. Job id: 1 25 Nov 2012 03:13:00
> [usage.log]
> 2012-11-25 03:13:00,154 ERROR [cloud.usage.UsageManagerImpl]
> (Usage-Job-1:null) Exception in usage manager
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on:
> org.apache.commons.dbcp.DelegatingPreparedStatement@5b5a5cf
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
> Unknown column 'account.default_zone_id' in 'field list'
> The usage server tried to get "account.default_zone_id" from "cloud_usage"
> database, but the "account" table doesn't have "default_zone_id" column.
> Kishan: This is the same bug as http://bugs.cloudstack.org/browse/CS-15170 - which apparently
didn't make it into master or 4.0 branch. 

--
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

Mime
View raw message