cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Whitehead (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CLOUDSTACK-6185) Upgrade from 4.1.1 -> 4.2.1 fails with database alter error
Date Fri, 28 Feb 2014 19:04:22 GMT

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

Bryan Whitehead edited comment on CLOUDSTACK-6185 at 2/28/14 7:04 PM:
----------------------------------------------------------------------

mysql> select * from router_network_ref where router_network_ref.router_id not in (select
id from domain_router)\G
*************************** 1. row ***************************
        id: 1
 router_id: 7
network_id: 204
guest_type: Shared
1 row in set (0.00 sec)




was (Author: jiqiren):
Yea I do have a record.

mysql> select * from router_network_ref where router_network_ref.router_id not in (select
id from domain_router);
+----+-----------+------------+------------+
| id | router_id | network_id | guest_type |
+----+-----------+------------+------------+
|  1 |         7 |        204 | Shared     |
+----+-----------+------------+------------+
1 row in set (0.00 sec)



> Upgrade from 4.1.1 -> 4.2.1 fails with database alter error
> -----------------------------------------------------------
>
>                 Key: CLOUDSTACK-6185
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6185
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Upgrade
>    Affects Versions: 4.2.1
>            Reporter: Bryan Whitehead
>         Attachments: upgrade.log
>
>
> Following the release notes for 4.2.1, cloudstack-management is unable to alter the tables
correctly - this causes the upgrade to fail.
> It was suggested on IRC that I try from 4.1.1 -> 4.2.0 before going to 4.2.1. I get
a entirely different DB alter error.
> I'll attach logs.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message