cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7071) Upgrade to 4.2 fails in case a VMware setup has multiple zones managing the same VMware datacenter
Date Mon, 07 Jul 2014 11:33:33 GMT

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

ASF subversion and git services commented on CLOUDSTACK-7071:
-------------------------------------------------------------

Commit 8e112858d35a77943e154e69736caaf2e5b94e7d in cloudstack's branch refs/heads/master from
[~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8e11285 ]

CLOUDSTACK-7071. Upgrade to CCP 4.2 fails in case a VMware setup has multiple zones mapping
to the same VMware datacenter.
If 2 or more CloudStack zones map to the same VMware datacenter, mark the zones as legacy
zones.


> Upgrade to 4.2 fails in case a VMware setup has multiple zones managing the same VMware
datacenter
> --------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7071
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7071
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade, VMware
>    Affects Versions: 4.2.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.5.0
>
>
> In a pre-upgrade setup if clusters that belong to one single VMware Datacenter are spread
across 3 different CloudStack zones, upgrade to 4.2 will fail.
> As part of the new mapping model for CloudStack zone and Vmware datacenter [https://issues.apache.org/jira/browse/CLOUDSTACK-1963],
during CS upgrade to 4.2 we populate each of the VMware datacenter into either cloud.vmware_datacenter
or cloud.legacy_zones table. But our upgrade script doesn't handle a VMware Datacenter that
is managed by two different CloudStack zones and hence the it will fail with the following
error -
> {noformat}
> 2014-06-19 03:19:27,565 ERROR [c.c.u.d.Upgrade410to420] (main:null) Unable to discover
legacy zones.Duplicate entry 'xxx' for key 'guid'
> 2014-06-19 03:19:27,568 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade
the database
> com.cloud.utils.exception.CloudRuntimeException: Unable to discover legacy zones.Duplicate
entry 'xxx' for key 'guid'
> at com.cloud.upgrade.dao.Upgrade410to420.persistLegacyZones(Upgrade410to420.java:979)
> at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:80)
> at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:292)
> at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:414)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message