HCX not taking current name of destination T1 after renaming, unextend-extend and-or recreate Service Mesh fail.

Products

• VMware HCX

Issue/Introduction

• The error occurs when extending the network and refers to an incorrect path containing an invalid character (name "T1-Nóme").
• An NSX T1 was created that included a special character in it name.
• The extension of a network that needed to use this T1 as the next hop will fail.
• To correct the issue the NSX T1 was renamed without any special characters used in its name.
  
  
• The T1 rename was perform in the NSX manager by clicking edit for the T1 with the special character in its name.
• The special character was removed.  From "T1-Nóme" to "T1-Name" in our example.
• The network extension still fails with the same error.
  
  

Environment

VMware NSX
VMware HCX

Cause

• This occurs more often when a keyboard language other than English is used.
• The edit modifies the display name, but not the object path. 
• The original name is used to create the objects path.
  •  /infra/tier-1s/T1-Nóme  ⇐This does not get modified when the display name is changed.
  • Display Name = T1-Name       ⇐Valid Name used in path = T1-Nóme 
• Invalid Name containing special character remains.
• The API calls used by HCX to request tasks of NSX will now fail due to the special character present in the T1's name in the object path.

Resolution

1. Create a new T1 with no special characters used.
2. Migrate segments to the new T1.