NSX-T tagging to virtual machine of onboarding is skipped.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• This issue occur add an NSX-T port group to a virtual machine on vSphere side before onboarding, and then immediately onboard virtual machine.
  
  
• NSX-T tagging to that virtual machine will be skipped.
  
  
• The following message will be output to provisioning-service-app.log:

  Skipping NSX-T tagging since the compute: [VM_NAME] is not connected to any NSX network

• You check the network resource type in Assembler -> Resources -> Deployments -> Onboarded Deployment, the virtual machine network is Cloud.vSphere.Network.
  
  Note: For NSX networks, expected value is Cloud.NSX.Network.

Environment

VMware Aria Automation 8.18.x

Cause

• Change the virtual machine configuration on vSphere side and then perform onboarding before Aria Automation data collection is complete, deployment will be created with old port group information.
  
  
• Aria Automation does not have information about the NSX-T port group that was added to the virtual machine before onboarding, so the virtual machine is network type is recognized as Cloud.vSphere.Network instead of Cloud.NSX.Network.
  
  
• As a result, it determines that the virtual machine is not connected NSX network and skips adding NSX-T tagging to the virtual machine.

Resolution

After adding NSX-T port group to VM in vSphere, wait for over 10 minutes before onboarding.

Note: Data collection of Aria Automation occurs every 10 minutes. For more information, see How does data collection work in VMware Aria Automation.