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

Crash refreshing VM scaleset #537

Closed
cehoffman opened this issue Nov 8, 2017 · 4 comments
Closed

Crash refreshing VM scaleset #537

cehoffman opened this issue Nov 8, 2017 · 4 comments

Comments

@cehoffman
Copy link

cehoffman commented Nov 8, 2017

Terraform Version

Terraform v0.10.8 with AzureRM 0.3.2. This same config works fine with 0.1.7 version of AzureRM.

Affected Resource(s)

azurerm_virtual_machine_scale_set

Terraform Configuration Files

resource "azurerm_virtual_machine_scale_set" "docker" {
  count               = "${var.test ? 0 : 1}"
  name                = "${var.prefix}-quay-builder"
  location            = "${var.region}"
  resource_group_name = "${var.resource_group_name}"
  upgrade_policy_mode = "Manual"

  sku {
    name     = "${var.vm_size}"
    tier     = "${element(split("_", var.vm_size),0)}"
    capacity = "${var.builder_count}"
  }

  os_profile {
    computer_name_prefix = "${var.prefix}-quay-builder-"
    admin_username       = "core"
    admin_password       = ""
    custom_data          = "${base64encode(data.ignition_config.builder.rendered)}"
  }

  os_profile_linux_config {
    disable_password_authentication = true

    ssh_keys {
      path     = "/home/core/.ssh/authorized_keys"
      key_data = "${file(var.public_key)}"
    }
  }

  network_profile {
    name    = "quay-builder-profile"
    primary = true

    ip_configuration {
      name                                   = "quay-builder-ip-configuration"
      subnet_id                              = "${azurerm_subnet.docker.id}"
      load_balancer_backend_address_pool_ids = ["${azurerm_lb_backend_address_pool.lb-pool.id}"]
    }
  }

  storage_profile_os_disk {
    name              = ""
    caching           = "ReadWrite"
    create_option     = "FromImage"
    managed_disk_type = "Standard_LRS"
  }

  storage_profile_image_reference {
    publisher = "CoreOS"
    offer     = "CoreOS"
    sku       = "Stable"
    version   = "latest"
  }
}

Debug Output

https://gist.github.com/cehoffman/724aa034741019012a3805058d188d2a

Panic Output

https://gist.github.com/cehoffman/724aa034741019012a3805058d188d2a

Expected Behavior

A change requiring a new resource should have been planned.

Actual Behavior

Terraform crashed with SIGSEGV

Steps to Reproduce

  1. terraform plan
@ctrlalttaco
Copy link

ctrlalttaco commented Nov 9, 2017

I too am experiencing this issue with azurerm provider v0.3.2 and Terraform v0.10.8. However, I have additional resources that are impacted.

azurerm_network_security_group
azurerm_subnet
azurerm_virtual_network_peering
provider

@ctrlalttaco
Copy link

I believe this is related to #491

@tombuildsstuff
Copy link
Contributor

Hey @cehoffman @Steven-Burns

Thanks for opening this issue :)

This is a duplicate of #481 which has been fixed in #480 - the fix has been merged into master and will be released in the near future; as such I'm going to close this issue for the moment.

Thanks!

@ghost
Copy link

ghost commented Apr 1, 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 1, 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

3 participants