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

Bug: It is not possible to create Static (standard SKU) IPv6 addresses #6090

Closed
TVH7 opened this issue Mar 12, 2020 · 3 comments · Fixed by #6140
Closed

Bug: It is not possible to create Static (standard SKU) IPv6 addresses #6090

TVH7 opened this issue Mar 12, 2020 · 3 comments · Fixed by #6140

Comments

@TVH7
Copy link

TVH7 commented Mar 12, 2020

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform version: 0.12.21

Affected Resource(s)

  • azurerm_2.0.0
  • azurerm_public_ip

Terraform Configuration Files

 resource "azurerm_public_ip" "ipv6" {
   depends_on = [azurerm_kubernetes_cluster.k8s]
   name                = "${var.aks_cluster_name}-lb01-ipv6"
   resource_group_name = azurerm_kubernetes_cluster.k8s.node_resource_group
   location            = azurerm_resource_group.k8s.location
   sku                 = "Standard"
   allocation_method   = "Static"
   ip_version          = "IPv6"
 }

Debug Output

https://gist.github.com/TVH7/c74c7c4df438795994fd50fa8b8e0cc0

Panic Output

https://gist.github.com/TVH7/c74c7c4df438795994fd50fa8b8e0cc0

Expected Behavior

When creating IPv6 Addresses with specific SKU's you have the following options:

Standard SKU: Only static IPv6 IP addresses are allowed.
Basic SKU: Only dynamic IPv6 IP Addresses are allowed.

However, at the moment terraform only allows to create Dynamic IP addresses for IPv6 which is not working with the Standard SKU type, thus the creation of the object fails.

Actual Behavior

We get an error saying: Cannot specify publicIpAllocationMethod as Static for IPv6 PublicIp, this is also described in the manual of the Azurerm IP address terraform object but this is only correct when working with the Basic type of IP addresses, it is not valid for the Standard SKU type.

Thus we can conclude that terraform's support for Standard SKU type IPv6 is broken at the moment.

Steps to Reproduce

  1. Create a IPv6 address with SKU=Standard and allocation_type="static"
  2. You will receive an error message stating that it is not possible to do so.
  3. Now try the same with SKU=Standard and allocation_type="Dynamic" and you will also receive an error message as you can only create dynamic SKU type IPv6 addresses.

Important Factoids

None.

References

https://www.terraform.io/docs/providers/azurerm/r/public_ip.html

  • #0000
@fabianofranz
Copy link
Contributor

PR to fix this issue: #6140

katbyte pushed a commit that referenced this issue Mar 20, 2020
This limitation has been relaxed for standard load balancers.

Fixes #6090.
@katbyte katbyte added this to the v2.3.0 milestone Mar 20, 2020
@ghost
Copy link

ghost commented Mar 27, 2020

This has been released in version 2.3.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.3.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Apr 20, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants