key:value vxlan_subnet is being populated when skip_creating_vxlan = true

[TP-87]

When I have no value for vxlan_subnet due to skipping the creation, I can see that it appears that a vxlan subnet has been created anyway with vxlan_subnet = "192.168.1.0/24"

I can see that the segment has not been created so seems to just be a value populated on the backend that is now being pulled in the code the issue is that because we don’t have that value in our code the resetting this value to “null” is forcing a replacement of the sddc - vxlan_subnet = "192.168.1.0/24" -> null # forces replacement

This same config worked without issues when using version 1.3

[saloneerege]

Thanks for reporting this issue. I will look into it.

[shylasrinivas]

@TP-87 fix for this issue is now available in the latest release v1.5.0

[github-actions]

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.