Unable to find management port group Management Network while migrating instances

[top-secrett]

ISSUE TYPE

• Bug Report

COMPONENT NAME

UI, API

CLOUDSTACK VERSION

4.18.0.0

CONFIGURATION

Advanced networking
VMware cluster
vSphere Client version 6.7.0.54000

OS / ENVIRONMENT

OracleLinux 8

SUMMARY

After reboot vSphere Client and whole VMware infrastructure we got an error while migration instances. Before reboot all worked fine.
Error:
MigrateCommand failed due to [Exception: java.lang.Exception Message: Unable to find management port group Management Network ].
Management port group "Management Network" present in VMware:

Full log:
ManagementNetworkError.txt

EXPECTED RESULTS

Migration successful

ACTUAL RESULTS

Migration failed

[kiranchavala]

@top-secrett

Could you please try to unmanage /Manage the cluster and then try to migrate a vm

[rohityadavcloud]

@top-secrett did you restart cloudstack management server as well after the VMware infra was rebooted?

[top-secrett]

@kiranchavala @rohityadavcloud I restarted CS management server and tryed to unmanage/manage clusters, but i get the same error

[top-secrett]

@rohityadavcloud @kiranchavala hello guys. Any suggestions how to resolve problem?

[rohityadavcloud]

Sorry I missed your message @top-secrett - you can simply try to create the port-group manually on the destination host. Ideally you can create a distributed vswitch and migrate all your guest network/port groups to the dvswitch.

[top-secrett]

@rohityadavcloud We are already using distributed vswitch with port group "Management Network"

[rohityadavcloud]

@top-secrett if this is an env where all the old svs were migrated to dvs, then you'll need to create the management network portgroup in the migrated DVS and in CloudStack enable the global setting vmware.use.dvswitch. You may also read https://www.shapeblue.com/cloudstack-vmware-environment-migration-from-vswitch-to-dvswitch/

I'm not sure if the docs website suggests these, this could be a docs issue - cc @DaanHoogland @weizhouapache

[top-secrett]

@rohityadavcloud should we use VLAN in "vmwarenetworklabel" zone parameter with dvs?

[DaanHoogland]

@top-secrett did you get any new information on this? is it still a problem?

[top-secrett]

@DaanHoogland It is still a problem. In 2 old clusters we can't migrate VMs. We added a new pod in existing zone and there is no problem

[harikrishna-patnala]

@top-secrett can you check the following details for your particular host from the managed object browser. You will need to first find the host in the path. (https:///mob then click on "Service Content" then "rootFolder" then "chilldEntity" then "hostFolder" then "childEntity" then "host" here you can moid of the host)

Management server is trying to query https:///mob/?moid=host-1009&doPath=config.virtualNicManagerInfo.netConfig and in that it is searching for value of nicType with "management"

The corresponding entry from vCenter I can see it here

Can you check if can list the similar details for your host.

[top-secrett]

@harikrishna-patnala

[JoaoJandre]

This issue seems like a environmental issue, not a bug; thus, I'll be removing it from the 4.18.2.0 milestone.
@SadiJr you have some experience with VMware, could you take a look at this?

[SadiJr]

@top-secrett could you please provide a little more information:

1. The migration fails between some specific hosts, or between any hosts? Also, are you only experiencing errors in the migration process?
2. Could you please review if your global configuration vmware.management.portgroup has the correct value? Please also check if there is a typo, or maybe a blank space at the start or the end of the configuration.
3. Could you please check, in every ESXi host, in Networking -> VMkernel NICs if the name of the Management Network is correct?

[top-secrett]

@SadiJr Hello. Sorry for delay.

1. I have 3 clusters in a one vSphereClient. Migration fails among all hosts in cluster-183_185-1 and cluster-183_185-2, but works in cluster-185. I found migrations errors only, everyting works fine except that.
   
   
2. There is no any additional spaces or symbols
   
3. All hosts from 3 clusters connected to the same network
   

[top-secrett]

I don't know what happened, but migration is working now.