cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saksham Srivastava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3837) 3.0.6 to ASF 4.2 Upgrade: "cloud_usage" Database Schema Inconsistencies on the Upgraded Setup
Date Fri, 26 Jul 2013 12:01:52 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720709#comment-13720709
] 

Saksham Srivastava commented on CLOUDSTACK-3837:
------------------------------------------------

I have added my changes to 4.2 and master in schema-410to420.sql
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=743d35c;hp=d89115b5cff9013c917c8d2e984c596698389cfe

Can you confirm does the problem still persists.
                
> 3.0.6 to ASF 4.2 Upgrade: "cloud_usage" Database Schema Inconsistencies on the Upgraded
Setup
> ---------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3837
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3837
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.2.0
>            Reporter: Chandan Purushothama
>            Assignee: Saksham Srivastava
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Cloud_usage database
> Table 9: cloud_usage
> On ASF 4.2 Setup:
> no virtual_size column
> On the 4.2 Upgraded Setup:
>  `virtual_size` bigint(20) UNSIGNED DEFAULT NULL,
> Table 10: usage_event
> On ASF 4.2 Setup:
> no virtual_size column
> On the 4.2 Upgraded Setup:
>  `virtual_size` bigint(20) UNSIGNED DEFAULT NULL,
> Table 11: usage_storage
> On ASF 4.2 Setup:
> no virtual_size column
> On the 4.2 Upgraded Setup:
>  `virtual_size` bigint(20) UNSIGNED DEFAULT NULL, 

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