ManagementConfigModel table migration failure post NSX-T Upgrade from any 3.1x version to 3.2.x/4.x versions

Products

• VMware NSX Networking

Issue/Introduction

Symptoms:

• Customers will observe that the publish_fqdns field (located in the ManagementConfigModel table, accessible via API GET api/v1/configs/management) consistently remains set to false following the upgrade from 3.1.x to 3.2.x/4.x 

Please note that version 3.2.0 doesn't have this issue. The issue exists, when customer is trying to upgrade a 3.1.x setup to 3.2.1, 3.2.2, 3.2.3, 4.0.0,1, 4.0.1,1. (For fixed versions, refer to Resolution section).

Note - VMware support maximum 2 releases upgrade. For instance,  VMware supports, customer to upgrade from 3.1.x -> 3.2.x and 3.1.x -> 4.0.x , but we don’t support 3.1.x -> 4.1.x and 3.1.x -> 4.2.x,  
And the issue only happens if customer is planning to upgrade from 3.1.x

• Relevant log locations - 

/var/log/proton/nsxapi.log
/var/log/proton/data-migration.log

Keywords for Log Search: ManagementConfigModel

Environment

VMware NSX-T Data Center 3.x
VMware NSX-T Data Center

Resolution

The issue is resolved in version 3.2.4. No fix required for versions 4.1 and above.

Workaround:
User must execute PUT /api/v1/configs/management with the following payload:
{
  "publish_fqdns": true,
  "_revision": 0
}

This resets the publish_fqdns field to true.

Additional Information

Impact/Risks:

Manual intervention required. Customers must manually set publish_fqdns to true using the PUT /api/v1/configs/management with the following payload, post upgrade

{
  "publish_fqdns": true,
  "_revision": 0
}