-
Notifications
You must be signed in to change notification settings - Fork 85
MP Resource import runs into endless loop #1481
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
Comments
The only PR that could have caused this behaviour is #1384 Let's target this to 3.8.0 to try and unblock as soon as possible. |
salv-orlando
added a commit
to salv-orlando/terraform-provider-nsxt
that referenced
this issue
Dec 17, 2024
The wrapper function was updating the existing importer, but the replaced function ended up having the same pointer as the wrapper function, meaning that import would enter an infinite recursion loop. Tested by doing import, read, update, and delete for 1) nsxt_logical_tier1_router 2) nsxt_ip_pool Signed-off-by: Salvatore Orlando <[email protected]>
salv-orlando
added a commit
that referenced
this issue
Dec 18, 2024
ImporterWrapper: Allocate a new Importer object (#1481)
Resolved with PR #1486. |
salv-orlando
added a commit
to salv-orlando/terraform-provider-nsxt
that referenced
this issue
Dec 18, 2024
The wrapper function was updating the existing importer, but the replaced function ended up having the same pointer as the wrapper function, meaning that import would enter an infinite recursion loop. Tested by doing import, read, update, and delete for 1) nsxt_logical_tier1_router 2) nsxt_ip_pool Signed-off-by: Salvatore Orlando <[email protected]>
annakhm
added a commit
that referenced
this issue
Dec 19, 2024
ImporterWrapper: Allocate a new Importer object (#1481)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We're trying to specifically import a nsxt_logical_tier1_router resource with
NSX-T: 4.1.2.5
Provider: 3.7.1
But the import runs into an endless loop and never comes back. Note that the import works with provider version 3.7.0 so it must be a recent change.
I can see the resource just fine using this code here so communication and authentication works fine and the resource exists:
But when I try to import the resource, the plan never comes back:
With TF_LOG=TRACE, we get the following:
... after that the cycle repeats endlessly.
Reproduction steps
Expected behavior
Import should work with provider versions >= 3.7.1
Additional context
No response
The text was updated successfully, but these errors were encountered: