cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6061) Unable to execute upgrade script: schema-421to430.sql, Duplicate column name 'related'
Date Fri, 07 Feb 2014 21:49:23 GMT

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

Alena Prokharchyk commented on CLOUDSTACK-6061:
-----------------------------------------------

:) how did you rollback? You probably didn't drop cloud/cloud_usage db entirely. If you just
applied the DB dump from 4.2.1, all the new tables inserted as a part of 4.2-4.3 upgrade (in
your case vm_work_job), are not gonna be cleaned up. And it will lead to further exception.
So you have to do this when you rollback:

1) drop database cloud; dropdatabase cloud_usage; create database cloud; create database cloud_usage
2) Apply 4.2.1 db dump
3) install template
4) run the upgrade

> Unable to execute upgrade script: schema-421to430.sql, Duplicate column name 'related'
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6061
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6061
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.1, 4.3.0
>         Environment: CentOS 6.5 x86_64 management server
> Using http://tmp.nux.ro/cloudsnap430_4308/ built from revision 4308
>            Reporter: Nux
>            Assignee: Alena Prokharchyk
>            Priority: Critical
>              Labels: db, upgrade
>
> Running an advanced zone with SG on 4.2.1, NFS primary and secondary storage, one instance
and one extra volume. One management server, 2 HVs.
> Upgraded to 4.3.0 as follows:
> 1. service cloudstack-management stop
> 2. yum -y update (to update cloudstack-* rpms)
> 3. Add new SystemVM tmplate
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary
-u http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-2014-02-06-master-kvm.qcow2.bz2
 -h kvm -F
> 4. service cloudstack-management start
> The following shows up in the management log:
> http://fpaste.org/75337/
> This is how my cloud DB looked like BEFORE the upgrade; this is the working 4.2.1 DB:
> http://tmp.nux.ro/ifu82kcloud.sql
> One Note:
> If I install 4.2.1 and run cloudstack-setup-databases and right after this upgrade to
4.3.0 then there is no problem.
> If I start using 4.2.1, add zones, HVs etc to it and THEN try to upgrade to 4.3.0 then
the problem appears.



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

Mime
View raw message