You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2017/12/17 20:43:00 UTC

[jira] [Closed] (CLOUDSTACK-8591) Upgrade410to420: upgrading legacy VMware environments to non-legacy

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

Rohit Yadav closed CLOUDSTACK-8591.
-----------------------------------
    Resolution: Not A Problem

> Upgrade410to420: upgrading legacy VMware environments to non-legacy
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8591
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8591
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.2.1
>            Reporter: Abhinandan Prateek
>            Assignee: Abhinandan Prateek
>            Priority: Critical
>             Fix For: 4.2.1
>
>
>  In engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java. The method persistLegacyZones(). It intends (per the spec and notes in code) to compare the cluster vcenter urls in a given zone to ensure they're all pointing to the same vcenter before upgrading to non-legacy. It loops through each zone, but it fails to filter the clusters by zone, so in environments where we have multiple zones but still a 1:1 mapping between vCenter and CS zone, they're wrongly marked as legacy because they method compares all clusters.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)