We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Given the following ipv6 address definition:
/ipv6 address 4 G 2600:1700:a646:41d:4aa9:8aff:fe75:d2c5/64 user-vlan users yes
And the following resource:
resource "routeros_ipv6_address" "user_vlan" { address = "2600:1700:a646:41d:4aa9:8aff:fe75:d2c5/64" eui_64 = true from_pool = routeros_ipv6_dhcp_client.user_vlan.pool_name interface = routeros_interface_vlan.users.name } resource "routeros_ipv6_dhcp_client" "user_vlan" { add_default_route = true advertise = true interface = "vrrp1" pool_name = "user-vlan" request = ["address", "prefix"] use_interface_duid = true use_peer_dns = false pool_prefix_length = "64" }
When running Terraform plan and importing the existing resource, this is the plan:
# routeros_ipv6_dhcp_client.user_vlan will be imported resource "routeros_ipv6_dhcp_client" "user_vlan" { add_default_route = true address = "2600:1700:a646:410::40, 48m6s" default_route_distance = 1 dhcp_options = [] dhcp_server_v6 = "fe80::fa63:d9ff:fe49:3e50" disabled = false duid = "0x0003000100005e000201" id = "*3" interface = "vrrp1" invalid = false pool_name = "user-vlan" pool_prefix_length = 64 prefix = "2600:1700:a646:41d::/64, 48m6s" prefix_hint = "::/0" request = [ "address", "prefix", ] status = "bound" use_interface_duid = true use_peer_dns = false }
It is showing some sort of timestamp as part of both the prefix and address, which is not correct.
Note that the actual IPV6 address is correct:
# routeros_ipv6_address.user_vlan will be imported resource "routeros_ipv6_address" "user_vlan" { actual_interface = "users" address = "2600:1700:a646:41d:4aa9:8aff:fe75:d2c5/64" advertise = true disabled = false dynamic = false eui_64 = true from_pool = "user-vlan" global = true id = "*60" interface = "users" invalid = false no_dad = false }
Since the 'address' property is read-only on the routeros_ipv6_dhcp_client, this seems to be a problem when importing resources.
routeros_ipv6_dhcp_client
To Reproduce Given the TF section above, apply that on a imported routeros_ipv6_dhcp_client and routeros_ipv6_adress.
Expected behavior The correct IPV6 address should be displayed when running plan (for example: "2600:1700:a646:41d:4aa9:8aff:fe75:d2c5/64")
Additional context
tofu version OpenTofu v1.8.6 on darwin_arm64 + provider registry.opentofu.org/terraform-routeros/routeros v1.70.0
The text was updated successfully, but these errors were encountered:
Hi, I'll try to take a look at it soon. Very interesting error in the plan:
Sorry, something went wrong.
I on CHR 7.15.3 was unable to reproduce the problem. Could you please run
CHR 7.15.3
TF_LOG_PROVIDER=1 TF_LOG=debug ROS_LOG_COLOR=1 terraform import routeros_ipv6_dhcp_client.user_vlan *X
and post the green MT response lines?
@outworlder Please look at my previous post.
No branches or pull requests
Describe the bug
Given the following ipv6 address definition:
And the following resource:
When running Terraform plan and importing the existing resource, this is the plan:
It is showing some sort of timestamp as part of both the prefix and address, which is not correct.
Note that the actual IPV6 address is correct:
Since the 'address' property is read-only on the
routeros_ipv6_dhcp_client
, this seems to be a problem when importing resources.To Reproduce
Given the TF section above, apply that on a imported routeros_ipv6_dhcp_client and routeros_ipv6_adress.
Expected behavior
The correct IPV6 address should be displayed when running plan (for example: "2600:1700:a646:41d:4aa9:8aff:fe75:d2c5/64")
Additional context
The text was updated successfully, but these errors were encountered: