@olivierlambert oh ok, I saw that and thought your comment was specific to the ESXi 7 version.

Thanks for the speedy response. I'd love to know how you clone yourself to be so responsive 24/7. Or am I talking to a Vates instance of ChatGPT?

@olivierlambert

I'm happy to help test if that kind of help is needed.

Mike

@olivierlambert yes, I think that would do it. I can't see any other difference at this point.

@gsrfan01 I don't know what to say. I have just tried to use 2 different TF files I was using to deploy Windows templates in XOA - I was not experiencing any of these errors before.

Now I am, and I am not having a good time of figuring out what is causing this.

Not sure what Windows could have to do with it - I'm running these commands on a RHEL Linux host - the errors occurs almost immediately after the command runs.

Very frustrating.

@gsrfan01

Here is my current vm.tf file

data "xenorchestra_pool" "pool" {
  name_label = "b500-2555 Server Room"
}

data "xenorchestra_template" "vm_template" {
  name_label = "rbbmswsoe2019s_2023-02-28"
}

data "xenorchestra_sr" "sr" {
  name_label = "nfs-isilon-xcpng-b500-2555"
   pool_id = "d27d1ac8-696a-78c6-e44f-444d1d10b5aa"
#  pool_id = data.xenorchestra_pool.pool.id
}

data "xenorchestra_network" "network" {
  name_label = "VLAN113"
   pool_id = "d27d1ac8-696a-78c6-e44f-444d1d10b5aa"
#  pool_id = data.xenorchestra_pool.pool.id
}

resource "xenorchestra_vm" "rbbmspcs2" {
  memory_max = 8589934594
  cpus = 2
  name_label = "XO terraform tutorial"
  affinity_host = data.xenorchestra_pool.pool.master
  template = data.xenorchestra_template.vm_template.id

  network {
    network_id = data.xenorchestra_network.network.id
}

  disk {
    sr_id = data.xenorchestra_sr.sr.id
    name_label = "VM boot drive"
    size = 50212254720
  }
}

I'm still getting this error

│ Error: jsonrpc2: code 10 message: invalid parameters: {"errors":[{"instancePath":"/VIFs/0/mac","schemaPath":"#/properties/VIFs/items/properties/mac/minLength","keyword":"minLength","params":{"limit":1},"message":"must NOT have fewer than 1 characters"}]}
│
│   with xenorchestra_vm.rbbmspcs2,
│   on vm.tf line 22, in resource "xenorchestra_vm" "rbbmspcs2":
│   22: resource "xenorchestra_vm" "rbbmspcs2" {
│
╵

I am not understanding this. Lin 22 is in the resource section for the VM.

@gsrfan01

so you're saying paste in the literal UUID

pool_id = "d27d1ac8-696a-78c6-e44e-444d1d10b5bb"

instead of referencing it like this?

pool_id = data.xenorchestra_pool.pool.id

This referenced version worked just fine in March... do I now have to change every instance of this pool_id definition thoughout my TF file?

@gsrfan01

I updated that stanza as follows

data "xenorchestra_network" "network" {
  name_label = "VLAN113"
  pool_id = var.pool_uuid
}

Now I can't get past "terraform plan" because "pool_uuid" hasn't been declared.

╷
│ Error: Reference to undeclared input variable
│
│   on vm.tf line 16, in data "xenorchestra_network" "network":
│   16:   pool_id = var.pool_uuid
│
│ An input variable with the name "pool_uuid" has not been declared. This variable can be declared with a variable "pool_uuid" {} block.
╵

No amount of googling is helping me to figure out how to declare "var.pool_uuid"

@gsrfan01 I'm up-to-date as far as I can tell.

Current version: 5.84.0

I just want to build a VM to test another feature - what can I do to get past this message? I can't find a way to define VIFs in Terraform for XO.

@florent hello, I'm sorry for the delay.

Yes, and I'm getting errors.

right after "terraform apply" and answering "yes" to the prompt, I got this:

xenorchestra_vm.rbbmspcs2: Creating...
╷
│ Error: jsonrpc2: code 10 message: invalid parameters: {"errors":[{"instancePath":"/affinityHost","schemaPath":"#/properties/affinityHost/minLength","keyword":"minLength","params":{"limit":1},"message":"must NOT have fewer than 1 characters"},{"instancePath":"/VIFs/0/mac","schemaPath":"#/properties/VIFs/items/properties/mac/minLength","keyword":"minLength","params":{"limit":1},"message":"must NOT have fewer than 1 characters"}]}
│
│   with xenorchestra_vm.rbbmspcs2,
│   on vm.tf line 19, in resource "xenorchestra_vm" "rbbmspcs2":
│   19: resource "xenorchestra_vm" "rbbmspcs2" {
│
╵

So... I did some Googling and found that another person was experiencing a similar issue recently, so I added the following line to my tf file:

affinity_host = data.xenorchestra_pool.pool.master

Now, I'm getting this error - and I can't figure out a solution on my own. Any ideas? I haven't toyed with my TF files in months, ever since I reported this, and wasn't getting these errors back then.

xenorchestra_vm.rbbmspcs2: Creating...
╷
│ Error: jsonrpc2: code 10 message: invalid parameters: {"errors":[{"instancePath":"/VIFs/0/mac","schemaPath":"#/properties/VIFs/items/properties/mac/minLength","keyword":"minLength","params":{"limit":1},"message":"must NOT have fewer than 1 characters"}]}
│
│   with xenorchestra_vm.rbbmspcs2,
│   on vm-windows.tf line 19, in resource "xenorchestra_vm" "rbbmspcs2":
│   19: resource "xenorchestra_vm" "rbbmspcs2" {
│
╵

Here follows the simplified TF file I've been using, with the new "affinity_host" line:

data "xenorchestra_pool" "pool" {
  name_label = "b500-2555 Server Room"
}

data "xenorchestra_template" "vm_template" {
  name_label = "rbbmswsoe2019s_2023-02-28"
}

data "xenorchestra_sr" "sr" {
  name_label = "nfs-isilon-xcpng-b500-2555"
  pool_id = data.xenorchestra_pool.pool.id
}

data "xenorchestra_network" "network" {
  name_label = "VLAN113"
  pool_id = data.xenorchestra_pool.pool.id
}

resource "xenorchestra_vm" "rbbmspcs2" {
  memory_max = 8589934594
  cpus = 2
  name_label = "XO terraform tutorial"
  affinity_host = data.xenorchestra_pool.pool.master
  template = data.xenorchestra_template.vm_template.id

  network {
    network_id = data.xenorchestra_network.network.id
  }

  disk {
    sr_id = data.xenorchestra_sr.sr.id
    name_label = "VM boot drive"
    size = 50212254720
  }
}

@florent ticket opened!

@florent XOA

@florent I confess I'm still new to things like "branches" I understand the concepts but am unsure how to go forward. Should I just wait until after the changes go live, or is there some way to test them before then?

@florent Great news! I'm eager to test, but tied up. I hope to get to it within the next 1-2 weeks.

Is there anything special I need to do from my end, or is the patch live?

Mike