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 modifying volume_name in ibm_is_instance_volume_attachment #3089

Closed
jjordana27 opened this issue Sep 10, 2021 · 0 comments · Fixed by #3117
Closed

Failure modifying volume_name in ibm_is_instance_volume_attachment #3089

jjordana27 opened this issue Sep 10, 2021 · 0 comments · Fixed by #3117
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure

Comments

@jjordana27
Copy link

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 other comments that do not add relevant new information or questions, 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 CLI and Terraform IBM Provider Version

Terraform v1.0.3 on windows_amd64
provider registry.terraform.io/ibm-cloud/ibm v1.31.0

Affected Resource(s)

  • ibm_is_instance_volume_attachment

Terraform Configuration Files

config file:

terraform {
  required_providers {
    ibm = {
      source = "IBM-Cloud/ibm"
      version = ">= 1.12.0"
    }
  }
}

# Configure the IBM Provider
provider "ibm" {
  region = "eu-de"
}

resource "ibm_is_instance" "testacc_instance" {
  resource_group = var.instance.resource_group
  name    = var.instance.name
  image   = var.instance.image
  profile = var.instance.profile
  primary_network_interface {
    subnet = var.instance.primary_network_interface.subnet
    primary_ipv4_address = var.instance.primary_network_interface.primary_ipv4_address
    allow_ip_spoofing = false
  }
  vpc  = var.instance.vpc
  zone = var.instance.zone
  keys = var.instance.keys
}

resource "ibm_is_instance_volume_attachment" "testacc_att1" {
  count = length(var.data_volumes)
  instance = ibm_is_instance.testacc_instance.id
  name = var.data_volumes[count.index].name
  profile = "custom"
  capacity = var.data_volumes[count.index].capacity
  volume_name = var.data_volumes[count.index].volume_name

}

old var:

"data_volumes" : [
        {
            "name" : "test-vol-att-1-45564",
            "capacity" : 50,
            "iops" : 100,
            "volume_name" : "testvol1-45564"
        }
    ]

new var:

"data_volumes" : [
        {
            "name" : "test-vol-att-1-45564",
            "capacity" : 50,
            "iops" : 100,
            "volume_name" : "newname"
        }
    ]

Expected Behavior

The volume_name should have changed

Actual Behavior

The volume_name did not change

Debug Output

This file contains the cmd output and the terraform/provider logs of the issue:

https://gist.github.com/jjordana27/f472a482e607041e8aa819561baa6238

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants