You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to #1146 we found another problem with the nsx_edge_transport_node resource. When using a ip_assignment of static_ip for the standard_host_switch like so:
We get the following error when applying this to NSX-T:
│ Error: failed to create Transport Node: error parsing HostSwitchSpec schema no valid IP assignment found
│
│ with nsxt_edge_transport_node.test2,
│ on [edges.tf](http://edges.tf/) line 1, in resource "nsxt_edge_transport_node" "test2":
│ 1: resource "nsxt_edge_transport_node" "test2" {
We're not sure what happens there as we cannot see the API call that the provider send to the backend, but somehow the info in the schema is not correctly translated?
Reproduction steps
Create a nsxt_edge_transport_node with a static ip assignment
Expected behavior
Edge node is created with static ip assignment and no error.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
In addition to #1146 we found another problem with the nsx_edge_transport_node resource. When using a ip_assignment of static_ip for the standard_host_switch like so:
We get the following error when applying this to NSX-T:
We're not sure what happens there as we cannot see the API call that the provider send to the backend, but somehow the info in the schema is not correctly translated?
Reproduction steps
Expected behavior
Edge node is created with static ip assignment and no error.
Additional context
No response
The text was updated successfully, but these errors were encountered: