[VMC] Unable to change the Connected Gateway of Segment to None
search cancel

[VMC] Unable to change the Connected Gateway of Segment to None

book

Article ID: 432902

calendar_today

Updated On:

Products

VMware Cloud on AWS

Issue/Introduction

  • For the NSX segments which were created via HCX L2E workflow and later cutover in VMC, the following error is thrown when attempting to change "Connected Gateway" to "None":-
    • Error: Could not resolve type id 'Segment' as a subtype of `ChildPolicyConfigResource`: known type ids = [ChildAntreaTraceflowConfig, ChildBfdProfile, ..., ChildSegment, ..., ChildVpcSubnetPort] (for POJO property 'children')
  • Creation of native NSX segments with "Connected Gateway" set to "None" continues to work. 
  • For existing native NSX segments, changing "Connected Gateway" to "None" also works.

Environment

VMware Cloud on AWS

Cause

This is caused by VMC-specific NSX UI bug where the payload does not contain: "resource_type": "ChildSegment"

Resolution

  • This is a known bug in VMC-specific NSX UI which is a part of NSX product bundle. Formal bug fix would come in as a bundle update in a future release (no ETA).
  • Workaround: Create a native NSX segment with "Connected Gateway" set to "None".

Additional Information

Create an Segment