cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sateesh Chodapuneedi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-4408) [Upgrade 3.0.7 to 4.2] Zone with clusters of multiple hypervisors including VMware should be processed for legacy zone.
Date Tue, 20 Aug 2013 10:33:52 GMT

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

Sateesh Chodapuneedi resolved CLOUDSTACK-4408.
----------------------------------------------

    Resolution: Fixed
    
> [Upgrade 3.0.7 to 4.2] Zone with clusters of multiple hypervisors including VMware should
be processed for legacy zone.
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4408
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4408
>             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: Sateesh Chodapuneedi
>            Assignee: Sateesh Chodapuneedi
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Currently zones with multiple clusters from more than 1 hypervisor including VMware,
are being ignored while processing them during upgrade.
> If a zone has all non-VMware clusters then ignoring the zone is correct.
> But if a zone has atleast 1 VMware cluster then make sure the zone processed further
to mark it as legacy or associate the zone with appropriate VMware DC.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message