Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 11 Sep 2014 12:19:34 +0000 (UTC)
From: "Daan Hoogland (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12740139.1410271151000.8731.1410437974609@Atlassian.JIRA>
In-Reply-To: <JIRA.12740139.1410271151000@Atlassian.JIRA>
References: <JIRA.12740139.1410271151000@Atlassian.JIRA>
 <JIRA.12740139.1410271151535@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-7521) DB migration from 4.2.1 to 4.4.0
 fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daan Hoogland updated CLOUDSTACK-7521:
--------------------------------------
    Priority: Critical  (was: Blocker)

> DB migration from 4.2.1 to 4.4.0 fails
> --------------------------------------
>
>                 Key: CLOUDSTACK-7521
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7521
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.4.0
>            Reporter: Siavash Safi
>            Priority: Critical
>         Attachments: management-server.log
>
>
> I tried to upgrade the management server on ubuntu from 4.2.1 to 4.4.0 but it fails to start.
> After checking syslog I noticed an exception related to DB migration.
> Here is the mysql error output when trying to run migration schema manually:
> {noformat}
> root@server:/etc/cloudstack/management# mysql -f -u cloud -p cloud < /usr/share/cloudstack-management/setup/db/schema-421to430.sql
> Enter password:
> ERROR 1050 (42S01) at line 64: Table 'vm_work_job' already exists
> ERROR 1050 (42S01) at line 75: Table 'async_job_journal' already exists
> ERROR 1050 (42S01) at line 86: Table 'async_job_join_map' already exists
> ERROR 1046 (3D000) at line 483: No database selected
> ERROR 1046 (3D000) at line 498: No database selected
> ERROR 1050 (42S01) at line 583: Table 'firewall_rule_details' already exists
> ERROR 1050 (42S01) at line 615: Table 'ldap_configuration' already exists
> ERROR 1050 (42S01) at line 624: Table 'monitoring_services' already exists
> ERROR 1062 (23000) at line 634: Duplicate entry '1' for key 'PRIMARY'
> ERROR 1062 (23000) at line 635: Duplicate entry '2' for key 'PRIMARY'
> ERROR 1062 (23000) at line 636: Duplicate entry '3' for key 'PRIMARY'
> ERROR 1062 (23000) at line 637: Duplicate entry '4' for key 'PRIMARY'
> ERROR 1050 (42S01) at line 641: Table 'usage_event_details' already exists
> ERROR 1050 (42S01) at line 650: Table 'usage_event_details' already exists
> ERROR 1050 (42S01) at line 659: Table 'user_ip_address_details' already exists
> ERROR 1050 (42S01) at line 669: Table 'remote_access_vpn_details' already exists
> ERROR 1060 (42S21) at line 787: Duplicate column name 'cpu_speed'
> ERROR 1050 (42S01) at line 791: Table 'vpc_details' already exists
> ERROR 1050 (42S01) at line 802: Table 'vpc_gateway_details' already exists
> ERROR 1050 (42S01) at line 812: Table 'network_acl_details' already exists
> ERROR 1050 (42S01) at line 822: Table 'network_acl_item_details' already exists
> ERROR 1050 (42S01) at line 847: Table 's2s_vpn_gateway_details' already exists
> ERROR 1050 (42S01) at line 876: Table 's2s_customer_gateway_details' already exists
> ERROR 1050 (42S01) at line 887: Table 's2s_vpn_connection_details' already exists{noformat}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)