VMs which have been vMotioned may have their NIC linked to the wrong network in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Symptoms:

• Provisioning process is intermittently linking a machine's network interface card to the wrong fabric network
• Machines' NICs assigned to NSX networks get re-assigned to the vSphere representation of the NSX network after vMotion
• When DRS is enabled on vSphere, it may not be known that the virtual machine has moved to another ESXi host
• Load balancer component provisioning fails because VM NIC network assignment has changed

Environment

• VMware Aria Automation 8.x

Cause

• This is due to an issue with the reconciliation logic when VMs with NSX networks are vMotioned

Resolution

• This issue will be fixed in Aria Automation 8.18.1-Patch 2 once it is made available.

 

Workaround:

It is possible to disable to logic that updates the machine NIC during vMotion.
The side effect is that if machine NIC subnet assignment actually does change during vMotion, it will not be updated.

1. Please snapshot all Aria Automation nodes before applying this change
2. Edit the provisioning service:
   • kubectl -n prelude edit deployment provisioning-service-app
3. Add the following option in the JAVA_OPTS section, taking care to use identical whitespace to the other options:
   • "-DUPDATE_SUBNET_LINK_ON_NIC=false"
4. The provisioning pods will take about 5 minutes to be recreated with the new option

Notes:

• The change above will need to be re-applied after rebooting or executing deploy.sh
• This will not fix existing deployments with wrong NIC assigned:
  • To fix these, please contact Global Support, referencing this article.