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

Products

• VMware NSX

Issue/Introduction

• You may 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
  Note: Version 3.2.0 doesn't have this issue. The issue exists, when you are trying to upgrade a 3.1.x installation 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).

• Relevant log locations - 

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

Keywords for Log Search: ManagementConfigModel

Environment

VMware NSX

Resolution

The issue is resolved in VMware NSX 3.2.4. 
This issue is resolved in VMware NSX 4.2.0

Workaround:
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