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

nutanix_subnet SIGSEGV on network rename #118

Closed
rafaldutko-ig opened this issue Apr 30, 2020 · 2 comments · Fixed by #122
Closed

nutanix_subnet SIGSEGV on network rename #118

rafaldutko-ig opened this issue Apr 30, 2020 · 2 comments · Fixed by #122

Comments

@rafaldutko-ig
Copy link

Nutanix Cluster Information

Version 5.11 - Starter License
NCC Version: 3.8.0.1
LCM Version: 2.2.9803

Terraform Version

Terraform v0.12.24

  • provider.nutanix v1.0.2
    also checked on
    Terraform v0.11.14
  • provider.nutanix v1.0.2

Affected Resource(s)

  • nutanix_subnet

Terraform Configuration Files

data "nutanix_clusters" "clusters" {
}

output "cluster" {
  value = data.nutanix_clusters.clusters.entities.0.metadata.uuid
}

resource "nutanix_subnet" "next-iac-managed" {
  # What cluster will this VLAN live on?
  cluster_uuid = data.nutanix_clusters.clusters.entities.0.metadata.uuid

  # General Information
  name        = "next-iac-managed-kotki"
  vlan_id     = 101
  subnet_type = "VLAN"

}

Debug Output

https://gist.github.com/rafaldutko-ig/2465e7f1c382a772a05a94b7f2889cec

Panic Output

https://gist.github.com/rafaldutko-ig/b664c3a7cd396e6055ae7beed1a35a6e

Expected Behavior

Network renamed from next-iac-managed-example to next-iac-managed-kotki

Actual Behavior

Terraform crashed with SIGSEGV

Steps to Reproduce

  1. terraform apply

Important Factors

Using a Prism Element cluster

References

  • #0000 <!---Github Issue number --->
@PacoDw
Copy link
Contributor

PacoDw commented May 11, 2020

Hello @rafaldutko-ig thank you so much for your review, I'm working on it, I'll let you know when I have news

@PacoDw
Copy link
Contributor

PacoDw commented May 11, 2020

The issue is fixed you can test it on the fix-#118 branch

Let me know if you have another comment or concern, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants