[
https://issues.apache.org/jira/browse/CLOUDSTACK-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744837#comment-13744837
]
ASF subversion and git services commented on CLOUDSTACK-4408:
-------------------------------------------------------------
Commit 319a7bf05caca175d67b910be79a7c9ead21a198 in branch refs/heads/4.2 from
[~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=319a7bf ]
CLOUDSTACK-4408 [Upgrade 3.0.7 to 4.2] Zone with clusters of multiple
hypervisors including VMware should be processed for legacy zone.
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.
Signed-off-by: Sateesh Chodapuneedi <[email protected]>
> [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
