NSX-T Load Balancer application profile parameters are not persistent on NCP restart

Products

• VMware NSX

Issue/Introduction

Symptoms:

• This issue can affect all K8S based NCP integrations, including TKGi.
• The Load Balancer application profile parameters are set via K8s.

For example, the request header size is set to 65536:

GET /api/v1/loadbalancer/application-profiles/<App-profile-id>
{ "http_redirect_to_https" : false, "ntlm" : false, "idle_timeout" : 15, "request_header_size" : 65536, "response_timeout" : 900, "response_header_size" : 65536, "resource_type" : "LbHttpProfile", "id" : "e0339cf8-ed08-4d77-ad7f-d965dd280a61", "display_name" : "ncp-pks-b4825b10-d116-462a-90d8-a1c8e51a2977-LbHttpProfile", "tags" : [ { "scope" : "ncp/version", "tag" : "1.2.0" }, { "scope" : "ncp/cluster", "tag" : "pks-b4825b10-d116-462a-90d8-a1c8e51a2977" } ], "_system_owned" : false, "_create_user" : "pks-b4825b10-d116-462a-90d8-a1c8e51a2977", "_create_time" : 1617024296892, "_last_modified_user" : "pks-b4825b10-d116-462a-90d8-a1c8e51a2977", "_last_modified_time" : 1617024296892, "_protection" : "REQUIRE_OVERRIDE", "_revision" : 0 }

• After a restart of NCP, these values are back to default.

The request header is now set to 1024:

GET /api/v1/loadbalancer/application-profiles/<App-profile-id>
{ "http_redirect_to_https" : false, "ntlm" : false, "idle_timeout" : 15, "request_header_size" : 1024, "response_timeout" : 900, "response_header_size" : 4096, "resource_type" : "LbHttpProfile", "id" : "e0339cf8-ed08-4d77-ad7f-d965dd280a61", "display_name" : "ncp-pks-b4825b10-d116-462a-90d8-a1c8e51a2977-LbHttpProfile", "tags" : [ { "scope" : "ncp/version", "tag" : "1.2.0" }, { "scope" : "ncp/cluster", "tag" : "pks-b4825b10-d116-462a-90d8-a1c8e51a2977" } ], "_system_owned" : false, "_create_user" : "pks-b4825b10-d116-462a-90d8-a1c8e51a2977", "_create_time" : 1617024296892, "_last_modified_user" : "pks-b4825b10-d116-462a-90d8-a1c8e51a2977", "_last_modified_time" : 1617025089030, "_protection" : "REQUIRE_OVERRIDE", "_revision" : 1 }

Environment

VMware NSX-T Data Center

Resolution

This issue is resolved in NSX-T NCP version 3.2.0 available at VMware downloads.

Workaround:

Re-apply the configuration via NSX-T REST API:

PUT /api/v1/loadbalancer/application-profiles/<application-profile-id>

Example Request:

PUT https://<nsx-mgr>/api/v1/loadbalancer/application-profiles/1cab1491-a058-48fd-ac55-ea412adb3283
{
  "resource_type" : "LbHttpProfile",
  "description" : "LB_HTTP_Application_Profile",
  "id" : "1cab1491-a058-48fd-ac55-ea412adb3283",
  "display_name" : "LB_HTTP_Application_Profile",
  "ntlm" : false,
  "request_header_size" : 65536,
  "http_redirect_to_https" : false,
  "idle_timeout" : 30,
  "_create_time" : 1515741466296,
  "_last_modified_user" : "admin",
  "_last_modified_time" : 1515741466296,
  "_system_owned" : false,
  "_create_user" : "admin",
  "_protection" : "NOT_PROTECTED",
  "_revision" : 0
}