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
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:
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
The text was updated successfully, but these errors were encountered:
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.
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
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:
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
The text was updated successfully, but these errors were encountered: