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

(Datasource) NSX-T Edge gateway Plugin chrashes when reading Egde gateway with allocated IPv6 addresses. V2 #1270

Closed
Nagte502 opened this issue May 16, 2024 · 5 comments · Fixed by #1275
Assignees

Comments

@Nagte502
Copy link

Hi, We are unfortunately still experiencing an issue with the datasource 'vcd_edgegateway' when the edge has IPv6 addresses allocated.
When using this datasource on an edge gateway that has ipv6 IP allocations, we get the following error:

image

This is a different error now that we have updated to 3.12.1, but it still doesn't work...
(#1242)

When removing the IPv6 allocation from the edge, the plugin works fine again, as before.

Terraform vcd provider version v3.12.1
Terraform version v1.8.3

@Didainius
Copy link
Collaborator

@Nagte502 ,
Would you be able to validate the fix that I have done in #1275?

@Nagte502
Copy link
Author

Nagte502 commented Jun 7, 2024

Unfortunately I haven't been able to do so yet. I hope to get to it early next week

@Nagte502
Copy link
Author

I've quickly discussed with the team this morning about testing the branch. Since the tenant in question is a customer tenant, we can't quickly make changes to it. As a work around, IPv6 has been disabled for the customer. Testing the branch would only work with IPv6 enabled. However, I won't be able to do so without customer impact. Unfortunately I won't be able to test this branch because of this.

@Didainius
Copy link
Collaborator

Understood. Would you be able to tell the prefix of IPv6 subnet the customer had? I am suspecting this had to be something big e.g. /64 as it is the case when API starts to miss a few fields and we had this error

@Nagte502
Copy link
Author

Yes, it's the same /64 network

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

Successfully merging a pull request may close this issue.

3 participants