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

Network ordering should be ordered as defined in TF file #99

Closed
itakouna opened this issue Nov 3, 2020 · 1 comment
Closed

Network ordering should be ordered as defined in TF file #99

itakouna opened this issue Nov 3, 2020 · 1 comment
Assignees
Labels

Comments

@itakouna
Copy link
Contributor

itakouna commented Nov 3, 2020

Terraform Version

all versiions

Affected Resource(s)

  • server_networks

Terraform Configuration Files

resource "gridscale_server" "node" {
  name  = "network-ordering"
  cores  = 1
  memory = 2
  network {
    object_uuid = data.gridscale_public_network.public.id
  }
  network {
    object_uuid = gridscale_network.private.id
  }

}

resource "gridscale_network" "private" {
  name = "network-ordering-private"
}

data "gridscale_public_network" "public" {
}

Expected Behavior

The network ordering should be consistent and match network resource order as defined in the TF file

Actual Behavior

The network order is assigned randomly

Steps to Reproduce

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

      + network {
          + bootdevice   = (known after apply)
          + create_time  = (known after apply)
          + mac          = (known after apply)
          + network_type = (known after apply)
          + object_name  = (known after apply)
          + object_uuid  = "e196b077-8286-4164-84d7-662af768745c"
          + ordering     = 0
        }
      + network {
          + bootdevice   = (known after apply)
          + create_time  = (known after apply)
          + mac          = (known after apply)
          + network_type = (known after apply)
          + object_name  = (known after apply)
          + object_uuid  = (known after apply)
          + ordering     = 0
        }

after running terraform apply, I run terraform plan again

terraform plan

     + network {
          + bootdevice   = (known after apply)
          + create_time  = (known after apply)
          + mac          = (known after apply)
          + network_type = (known after apply)
          + object_name  = (known after apply)
          + object_uuid  = "e196b077-8286-4164-84d7-662af768745c"
          **+ ordering     = 0**
        }
      - network {
          - bootdevice   = false -> null
          - create_time  = "2020-11-03 14:05:34 +0000 UTC" -> null
          - mac          = "16:63:39:97:97:01" -> null
          - network_type = "network" -> null
          - object_name  = "network-ordering-private" -> null
          - object_uuid  = "1d5d7e68-d3b1-4506-8773-4b1e48be1e06" -> null
          **- ordering     = 0 -> null**
        }
      + network {
          + bootdevice   = false
          + create_time  = "2020-11-03 14:05:34 +0000 UTC"
          + mac          = "16:63:39:97:97:01"
          + network_type = "network"
          + object_name  = "network-ordering-private"
          + object_uuid  = "1d5d7e68-d3b1-4506-8773-4b1e48be1e06"
          **+ ordering     = 0**
        }
      - network {
          - bootdevice   = false -> null
          - create_time  = "2020-11-03 14:05:37 +0000 UTC" -> null
          - mac          = "16:63:39:97:97:02" -> null
          - network_type = "network" -> null
          - object_name  = "Public Network" -> null
          - object_uuid  = "e196b077-8286-4164-84d7-662af768745c" -> null
          **- ordering     = 1 -> null**
        }
The network order has changed
@itakouna
Copy link
Contributor Author

itakouna commented Nov 4, 2020

solved in v1.7.4

@itakouna itakouna closed this as completed Nov 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants