[
https://issues.apache.org/jira/browse/CLOUDSTACK-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-9911:
-------------------------------------------
Description:
The Upgrade looks for legacy zones and updates vmware_data_center and
vmware_data_center_zone_map tables. The way it does is that, that it only looks
for the first cluster, for zone 1 that is KVM so the update is skipped.
Messages from logs confirming above:
2017-04-28 19:21:35,424 DEBUG [c.c.u.d.Upgrade410to420] (main:null) (logid
Ignoring zone 1 with hypervisor type KVM
2017-04-28 19:21:35,426 DEBUG [c.c.u.d.Upgrade410to420] (main:null) (logid
Discovered non-legacy zone 3. Processing the zone to associate with VMware
datacenter.
Link to the Update code is below. This code looks at the first cluster and
since it is KVM skips it
https://github.com/shapeblue/cloudstack/blob/4.9/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java#L713
While adding a new VMWare DC the mapping is used to make sure that the new
VMWare DC is not already in use. So this check will fail and the same VMWare DC
could be added again.
was:
n short, the Upgrade looks for legacy zones and updates vmware_data_center and
vmware_data_center_zone_map tables. The way it does is that it only looks for
the first cluster, for zone 1 that is KVM so update is skipped.
Messages from logs confirming above:
2017-04-28 19:21:35,424 DEBUG [c.c.u.d.Upgrade410to420] (main:null) (logid
Ignoring zone 1 with hypervisor type KVM
2017-04-28 19:21:35,426 DEBUG [c.c.u.d.Upgrade410to420] (main:null) (logid
Discovered non-legacy zone 3. Processing the zone to associate with VMware
datacenter.
Link to the Update code:
This code looks at the first cluster and since it is KVM skips it
https://github.com/shapeblue/cloudstack/blob/4.9/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java#L713
While adding a new VMWare DC the mapping is used to make sure that the new
VMWare DC is not already in use. So this check will fail and the same VMWare DC
could be added again.
> VMware VC details not visible after upgrade 3.0.7 to 4.9.1
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-9911
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9911
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.9.0.1
> Environment: VMWARE
> Reporter: Abhinandan Prateek
> Fix For: Future
>
>
> The Upgrade looks for legacy zones and updates vmware_data_center and
> vmware_data_center_zone_map tables. The way it does is that, that it only
> looks for the first cluster, for zone 1 that is KVM so the update is skipped.
> Messages from logs confirming above:
> 2017-04-28 19:21:35,424 DEBUG [c.c.u.d.Upgrade410to420] (main:null) (logid
> Ignoring zone 1 with hypervisor type KVM
> 2017-04-28 19:21:35,426 DEBUG [c.c.u.d.Upgrade410to420] (main:null) (logid
> Discovered non-legacy zone 3. Processing the zone to associate with VMware
> datacenter.
> Link to the Update code is below. This code looks at the first cluster and
> since it is KVM skips it
> https://github.com/shapeblue/cloudstack/blob/4.9/engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java#L713
> While adding a new VMWare DC the mapping is used to make sure that the new
> VMWare DC is not already in use. So this check will fail and the same VMWare
> DC could be added again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
