Skip to content
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

Terraform resource limitation for NSXT LB #1353

Open
ravishankar1jan opened this issue Sep 4, 2024 · 5 comments
Open

Terraform resource limitation for NSXT LB #1353

ravishankar1jan opened this issue Sep 4, 2024 · 5 comments
Assignees
Labels
bug Bug duplicate Duplicate
Milestone

Comments

@ravishankar1jan
Copy link

Describe the bug

I have try to automate NSXT resource provisioning however i am only able to create some of resources in policy mode (Highlighted in green colour).

GitHub

Could you please let me know if anyone has solution to provision resources which are greyed out.
Please also let me know if additional explanation is required.

Reproduction steps

Expected behavior

Additional context

@ravishankar1jan ravishankar1jan added the bug Bug label Sep 4, 2024
@salv-orlando
Copy link
Member

salv-orlando commented Sep 4, 2024

Hello @ravishankar1jan If I try to open the image you attached I get a 404. Can you please comment on which resources are still missing? We have some gaps for NSX LB resources, and planning to close them in 3.7.0 or 3.8.0 if time does not allows us to.

@ravishankar1jan
Copy link
Author

@salv-orlando
Following is status of resources. Where ever there is "X", i am not able to create that resource in policy mode.

Profile-> APPLICATION

Fast TCP - X
Fast UDP - X
HTTP - nsxt_policy_lb_http_application_profile

Profile-> Persistence

Source IP - X
Cookie - X
Generic - X

Profile-> SSL

Client SSL - nsxt_policy_lb_client_ssl_profile
Server SSL - X

=================================
Monitor-> All working as expected
Active ->
http - nsxt_policy_lb_http_monitor_profile
https - nsxt_policy_lb_https_monitor_profile
icmp - nsxt_policy_lb_icmp_monitor_profile
tcp - nsxt_policy_lb_tcp_monitor_profile
udp - nsxt_policy_lb_udp_monitor_profile
Passive ->
passive - nsxt_policy_lb_passive_monitor_profile

Virutal Server

HTTP -> nsxt_policy_lb_virtual_server
TCP -> X
UDP -> X

ServerPool

LB Pool - nsxt_policy_lb_pool

GitHub

Please let me know if you need any further details.

Thanks

@annakhm annakhm added the duplicate Duplicate label Sep 9, 2024
@ravishankar1jan
Copy link
Author

Hello Team,
I have tried to create virtual server with rule set using terraform with nsxt provider version 3.6.2 as well as 3.7.0
However, when i am trying to create with rules it's throwing following error:


│ Error: Plugin did not respond

│ with module.my_module_name.nsxt_policy_lb_virtual_server.test,
│ on .terraform/modules/my_module_name/virtual-server.tf line 12, in resource "nsxt_policy_lb_virtual_server" "test":
│ 12: resource "nsxt_policy_lb_virtual_server" "test" {

│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.

Stack trace from the terraform-provider-nsxt_v3.7.0 plugin:
panic: interface conversion: interface {} is nil, not map[string]interface {}
goroutine 76 [running]:
github.com/vmware/terraform-provider-nsxt/nsxt.getPolicyLbRulesFromSchema(0xc000778600?)
github.com/vmware/terraform-provider-nsxt/nsxt/resource_nsxt_policy_lb_virtual_server.go:1416 +0x4997
github.com/vmware/terraform-provider-nsxt/nsxt.resourceNsxtPolicyLBVirtualServerCreate(0xc000778600, {0x1bf5480, 0xc0003f9380})
github.com/vmware/terraform-provider-nsxt/nsxt/resource_nsxt_policy_lb_virtual_server.go:1619 +0x605
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).create(0x1f4a590?, {0x1f4a590?, 0xc000a8f260?}, 0xd?, {0x1bf5480?, 0xc0003f9380?})
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:766 +0x15f
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc0000195e0, {0x1f4a590, 0xc000a8f260}, 0xc0004bea90, 0xc000778480, {0x1bf5480, 0xc0003f9380})
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:909 +0xa89
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc000481d40, {0x1f4a590?, 0xc000a8f1a0?}, 0xc000a0bcc0)
github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/grpc_provider.go:1060 +0xd5c
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ApplyResourceChange(0xc00035cdc0, {0x1f4a590?, 0xc000a8e9c0?}, 0xc0002de380)
github.com/hashicorp/[email protected]/tfprotov5/tf5server/server.go:859 +0x56f
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ApplyResourceChange_Handler({0x1c18120, 0xc00035cdc0}, {0x1f4a590, 0xc000a8e9c0}, 0xc0002de310, 0x0)
github.com/hashicorp/[email protected]/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:467 +0x1a6
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0001d0000, {0x1f4f580, 0xc0004bc000}, 0xc000a918c0, 0xc0002f60c0, 0x28888d8, 0x0)
google.golang.org/[email protected]/server.go:1358 +0xde3
google.golang.org/grpc.(*Server).handleStream(0xc0001d0000, {0x1f4f580, 0xc0004bc000}, 0xc000a918c0, 0x0)
google.golang.org/[email protected]/server.go:1735 +0x9da
google.golang.org/grpc.(*Server).serveStreams.func1.1()
google.golang.org/[email protected]/server.go:970 +0xbb
created by google.golang.org/grpc.(*Server).serveStreams.func1 in goroutine 20
google.golang.org/[email protected]/server.go:981 +0x136
Error: The terraform-provider-nsxt_v3.7.0 plugin crashed!
This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Please let me know if you need any additional details.

Regards,
Ravi Shankar

@ksamoray
Copy link
Collaborator

Hi @ravishankar1jan, can you include the nsxt_policy_lb_virtual_server resource which triggered the failure?

@salv-orlando salv-orlando added this to the v3.9.0 milestone Dec 13, 2024
@salv-orlando
Copy link
Member

@ksamoray this request completes and overlaps with issue #1240 - perhaps they should be both addressed with the same PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug duplicate Duplicate
Projects
None yet
Development

No branches or pull requests

4 participants