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

Failure when deploying new azure_kubernetes_cluster resource into centralus #1160

Closed
g0atcheez opened this issue Apr 24, 2018 · 7 comments
Closed

Comments

@g0atcheez
Copy link

Starting yesterday, our automation has broken with the following error.

  • azurerm_kubernetes_cluster.test: containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="LinkedInvalidPropertyId" Message="Property id '' at path 'properties.agentPoolProfiles[0].vnetSubnetID' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'."

As a test, I took the sample from the resource documentation and tried deploying it to multiple regions with the same result.

Terraform Version

Terraform v0.11.7

  • provider.azurerm v1.3.3

Affected Resource(s)

Please list the resources as a list, for example:

  • azure_kubernetes_cluster

Terraform Configuration Files

provider "azurerm" {}

resource "azurerm_resource_group" "test" {
  name     = "acctestRG1"
  location = "centralus"
}

resource "azurerm_kubernetes_cluster" "test" {
  name                = "acctestaks1"
  location            = "${azurerm_resource_group.test.location}"
  resource_group_name = "${azurerm_resource_group.test.name}"
  dns_prefix          = "acctestagent1"

  linux_profile {
    admin_username = "azureuser"

    ssh_key {
      key_data = "${file("modules/azure/terraform.pub")}"
    }
  }

  agent_pool_profile {
    name            = "default"
    count           = 1
    vm_size         = "Standard_A0"
    os_type         = "Linux"
    os_disk_size_gb = 30
  }

  service_principal {
    client_id     = "00000000-0000-0000-0000-000000000000"
    client_secret = "00000000000000000000000000000000"
  }
}

Debug Output

https://gist.github.com/g0atcheez/4cbdcb9b26b067239c5808eac9140dce

Expected Behavior

Terraform provisions the AKS cluster.

Actual Behavior

The apply errors out stating that the subnet ID is blank.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform init
  2. terraform apply
@tombuildsstuff
Copy link
Contributor

hi @g0atcheez

Thanks for opening this issue :)

We also detected this API change in our acceptance tests run this morning and have opened #1158 which includes a fix - which will be released as part of v1.4.0 in the near future.

Thanks!

@tombuildsstuff
Copy link
Contributor

@g0atcheez I'm going to close this issue since I've just merged the fix for this into master - as mentioned above we'll be shipping this fix as a part of v1.4.0 very soon.

Thanks!

@g0atcheez
Copy link
Author

g0atcheez commented Apr 24, 2018

Thanks for the quick response and fix!

@tombuildsstuff
Copy link
Contributor

tombuildsstuff commented Apr 26, 2018

hey @g0atcheez

Just to let you know that v1.4.0 of the Azure Provider has been released which includes the fix for this :)

Thanks!

@damian-robo
Copy link

damian-robo commented Jun 6, 2018

This issue is still present. We're using the following and we're still getting an error while trying to create the AKS:

Terraform v0.11.7
provider.azurerm v1.6.0

@katbyte
Copy link
Collaborator

katbyte commented Jun 13, 2018

Hello @damian-robo,

Could you please open a new issue and supply the terraform exhibiting the issue and the error you are getting?

Thanks!

@ghost
Copy link

ghost commented Mar 30, 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 Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants