Load balancer application profiles created using API with id of edge_load_balancer_application_profiles-x" rather than "applicationProfile-x".

Products

• VMware NSX

Issue/Introduction

• The applicationProfileId parameter is not specified while configuring the NSX Edge Load Balancer with the REST API “PUT /api/4.0/edges/{edgeId}/loadbalancer/config”.  An application profile is created with an incorrect “applicationProfileId”.
• The following error message is displayed in the vSphere Client UI when you associate this application profile with the virtual server:
  
  "errorMessage": "[LoadBalancer] Invalid LoadBalancer objectId edge_load_balancer_application_profiles1, the valid objectId should start with the objectId prefix applicationProfile-

Cause

When the "applicationProfileId" parameter is omitted while configuring an NSX Edge Load Balancer with the PUT REST API, a default "applicationProfileId" is created. This default “applicationProfileId” is created in an incorrect format (i.e. edge_load_balancer_application_profilesX instead of applicationProfile-X).

Resolution

Resolved in VMware NSX for vSphere 6.4.5.

Workaround:
To overcome this issue, specify the "applicationProfileId" with pattern “applicationProfile-<number>” while configuring the NSX Edge Load Balancer with the REST API “PUT /api/4.0/edges/{edgeId}/loadbalancer/config”.