This issue is resolved in NSX-T 3.2.2.1, available from VMware Broadcom Support Portal .
Workaround:
Impacted environments should upgrade to 3.2.2.1 or higher.
If an attempt was made to install 3.2.2 and a host is already stuck in 0% state, it may be necessary to clean this up.
Remove NSX from the host, if restrictions apply this can be performed from API using
DELETE http://<NSX mgmt IP>/api/v1/transport-nodes/<TN ID>?force=true&unprepare_host=false