Error when deploying normal VM through terraform [RESOLVED]

#1

Trying to deploy a VM on the TF grid, but fail to get a ygg_network running. I followed the example code in the terraform section of the manual, but that failed. This is the example code

The output is as follows:

 /m/h/j/c/g/w/mytrunk   *…  terraform/TF-Test  terraform init                             Thu May  9 15:00:40 2024

Initializing the backend...

Initializing provider plugins...
- Finding latest version of threefoldtech/grid...
- Installing threefoldtech/grid v1.10.0...
- Installed threefoldtech/grid v1.10.0 (self-signed, key ID 77AB02E5CA9698A3)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
 /m/h/j/c/g/w/mytrunk   *…  terraform/TF-Test  terraform plan                      9.4s  Thu May  9 15:00:54 2024
╷
│ Error: Unsupported attribute
│ 
│   on main.tf line 84, in output "ygg_ip1":
│   84:    value = grid_deployment.d1.vms[0].ygg_ip
│ 
│ This object has no argument, nested block, or exported attribute named "ygg_ip".
╵
1 Like
#2

Thanks Weynand.

I know we are going with Mycelium for the Planetary Network. I started an issue on the manual to make sure we have proper docs on planetary network (mycelium) instead of yggdrasil.

It seems the yggdrasil address does not work for some reason. You can just remove the output section

output "ygg_ip1" {
  value = grid_deployment.d1.vms[0].ygg_ip
}

and set false to planetary

    planetary = true
  }
}

You can still access with SSH and IPv4. You can also set Mycelium: https://manual.grid.tf/documentation/system_administrators/mycelium/mycelium_toc.html

There might be a fix for yggdrasil or it’s perhaps not supported anymore. I can have a look soon.

As always @scott may have some insights too.

#3

Actually all that’s needed is to replace ygg_ip with planetary_ip. It’s all indeed a bit confusing with the introduction of Mycelium as well, but for now “Planetary Network” is still Yggdrasil and the name of the field in our Terraform provider was changed not too long ago.

1 Like
#4

Well that is something. Thanks Scott.

We’ll make sure we have something clear if this is not optimal for users. Thanks @weynandkuijpers for the feedback.

1 Like