-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nsx_edge_transport_node deploy failures (crash on syslog port + root object absent) #1186
Labels
bug
Bug
Comments
Ah, I always forget: we're testing against NSX-T 4.1.2.3 |
ksamoray
added a commit
to ksamoray/terraform-provider-nsxt
that referenced
this issue
Apr 18, 2024
validateSinglePort() validates a string value and therefore unsuitable for use in this case. NSX will validate the port in any case. Fixes: vmware#1186
ksamoray
added a commit
to ksamoray/terraform-provider-nsxt
that referenced
this issue
Apr 18, 2024
validateSinglePort() validates a string value and therefore unsuitable for use in this case. NSX will validate the port in any case. Fixes: vmware#1186 Signed-off-by: Kobi Samoray <kobi.samoray@broadcom.com>
ksamoray
added a commit
to ksamoray/terraform-provider-nsxt
that referenced
this issue
Apr 18, 2024
validateSinglePort() validates a string value and therefore unsuitable for use in this case. NSX will validate the port in any case. Fixes: vmware#1186 Signed-off-by: Kobi Samoray <kobi.samoray@broadcom.com>
ksamoray
added a commit
to ksamoray/terraform-provider-nsxt
that referenced
this issue
Apr 18, 2024
validateSinglePort() validates a string value and therefore unsuitable for use in this case. NSX will validate the port in any case. Fixes: vmware#1186 Signed-off-by: Kobi Samoray <kobi.samoray@broadcom.com>
annakhm
pushed a commit
that referenced
this issue
May 15, 2024
validateSinglePort() validates a string value and therefore unsuitable for use in this case. NSX will validate the port in any case. Fixes: #1186 Signed-off-by: Kobi Samoray <kobi.samoray@broadcom.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Since #1146 and #1153 have now been fixed (thanks!) and the new provider has been released, we have resumed testing.
We still have problems creating new edges with our desired configuration. Given the following resource:
We have two problems.
Reproduction steps
Expected behavior
No errors on deploy.
Additional context
No response
The text was updated successfully, but these errors were encountered: