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

softlayer_file_storage requires a different IOPS value than what is stored in state #135

Closed
lgfa29 opened this issue Mar 29, 2017 · 1 comment

Comments

@lgfa29
Copy link

lgfa29 commented Mar 29, 2017

When ordering a softlayer_file_storage resource you need to specify a value for iops which can be 0.25, 2, 4 or 10.

But after the resource is created, the value stored in the Terraform state has more decimals, so, for example,4 is stored as 4.096 and 10 is stored as 10.24.

This causes a subsequent terraform plan to incorrect flag the resource as needing to be recreated.

Steps to reproduce

  1. Order a softlayer_file_storage:
resource "softlayer_file_storage" "nfs" {
    type = "Endurance"
    datacenter = "tor01"
    capacity = 500
    iops = 4
}
  1. terraform apply
  2. terraform plan gives wrong result:
/+ softlayer_file_storage.nfs
    capacity:                           "500" => "500"
    datacenter:                         "tor01" => "tor01"
    hostname:                           "[OMITTED]" => "<computed>"
    iops:                               "4.096" => "4" (forces new resource)
    snapshot_capacity:                  "500" => "500"
    type:                               "Endurance" => "Endurance"
    volumename:                         "[OMITTED]" => "<computed>"

Expected result

No changes required

Environment

Terraform v0.8.8
terraform-provider-softlayer v1.4.0
@renier
Copy link
Contributor

renier commented Mar 30, 2017

@ivan-n16

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

No branches or pull requests

2 participants