[
https://issues.apache.org/jira/browse/CLOUDSTACK-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-6061:
-------------------------------------------
Assignee: Alena Prokharchyk
> 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)
